Any plan to update to the latest version of Underscores

Hey guys @connorjburton @jarednova
First of all thanks a lot for creating Timber and this starter theme.
I just wanted to know, is there any plan to update this starter theme to the latest version of underscores? I am afraid the base html and the functions in this starter theme have got way too old 😭
Please let me know guys, Thanks in advance!

Which functions do you think are out of date @utsavdevsharma? I think I could find some time this weekend to open a PR updating some of that if it makes sense. A lot of template tags aren't needed though since you should be adding most of that data to your Timber context :)

PR's are very welcome if this is necessary for anyone. I will add an issue to change to namespaces too.

Underscores is deprecated and will be archived, no longer updated. Has anyone used https://blockbasetheme.com/ at https://github.com/Automattic/themes/tree/trunk/blockbase from Automattic? Because of the major changes in WordPress, we have to consider the 2 approaches now. I've been struggling with trying to figure this out myself, so did some research and the reasons for this are compelling:

WordPress is still in a transition phase – block themes are in a nascent stage and don’t offer the full gamut of features that will be available in the future. This puts theme developers in a bind; do we:

Continue building classic themes and ignore the Full Site Editor.

This is easier in the short term, but it ties our users in to the classic WordPress way of doing things.

Build block themes and give users a “beta” experience in the Full Site Editor

The Site Editor is still rough around the edges and for users who are familiar with the classic dashboard it can be confusing and frustrating.

Neither of these options is ideal. Enter universal themes.
Universal themes are an attempt to use the benefits of both approaches.


Fix dex merge issue

The issue was coming probably because the app was using different versions of build tool version and support library.
This no longer fails.
./gradlew :app:transformDexArchiveWithExternalLibsDexMergerForBetaDebugAndroidTest --stacktrace

@neslihanturan Can you test and confirm if the dex merge issue gets fixed by this PR. :)

@maskaravivek it seems like it didn't affect the issue. However, I think we should still include these changes into our code base.


German in english version

On the title page when using main-english.tex it says "Masterarbeit" instead of "Masterthesis" which I would say is the common translation for english.

Please see the discussion at https://github.com/latextemplates/scientific-thesis-cover/pull/10.
Please check with the Prüfungsausschuss Informatik whether there were changes in the last years. If yes, please file a pull request against https://github.com/latextemplates/scientific-thesis-cover
In case you are not from University of Stuttgart, I would advise you to check the documentation at https://github.com/latextemplates/scientific-thesis-cover#supported-options (type) and use type={master thesis}.

Ah okay I missed that, my bad. Thanks for the clarification.

You can add that to the FAQ (https://github.com/latextemplates/scientific-thesis-template/blob/master/docs/index.md#faq).
Enjoy #hacktoberfest


Dictionary and Enumerable Mappings: Call EnsureCapacity if source count is known and target has a EnsureCapacity(int) method

If Mapperly generates a foreach / Add mapping the capacity of the target is increased as needed.
If the source type does have a Count/ Length property and the target type does have a Method EnsureCapacity(int), EnsureCapacity(source.Count + target.Count) can be called to ensure the target collection has a big enough capacity for all source objects plus the existing target objects and does not need to resize as mapped objects are added.

This is already done via constructor arguments for dictionaries and lists I think. Calling EnsureCapacity there would be redundant

You are correct, if the target is created by Mapperly via new and the target type is a List or Dictionary. But if the target instance already exists, it is created via an object factory or is any type implementig IDictionary<,> or IList<> but is not Dictionary/List (eg. a custom List implementation), the capacity is not ensured.


Game Level Plan 9- Aditya,Aaryav,Aneesh

Game Plan
Level being changed: Skibidi
Aneesh: theme and background (sprites too)
Aditya:     Adjusting hitboxes of sprite and background so the character doesn't appear as floating.

Aaryav: Block placing is random and can be adjusted so the player can be more mobile.

Looking at this image the block placement is really random and doesn't help the player move around. If the block placement could be farther spread out it could give the player a better interaction. I plan to move the blocks towards the end of the level  instead of having them all stacked up at the start of the map.

Updated Hitbox for the main sprite:

Block placement has changed signicficantly throughout the stage

Clearer background with similar desert theme


Changlog

Should forks be encouraged (to be written in Contributing) to keep a running file that they do  not send in for the pull request of their own changes?

Do you meen like a log?

Yes, based off the concepts here.
But closing the issue as this is for sure not the responsibility of contributors, although they can be encouraged.


https://github.com/MicrosoftDocs/azure-docs/files/7186122/Re.Potential.issue.with.Managed.Scanning.PowerShe_438746692.eml

Re Potential issue with Managed Scanning PowerShe_438746692.eml.zip
As per attached email thread, there seems to be a bug in the powershell in this tutorial, rename the attachment and remove zip extension to open it.

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

ID: f2058d99-ebe7-6d5d-1337-43de20df8116
Version Independent ID: 643c4310-00e2-3dac-c0db-7e4f9c588d22
Content: Register and scan a Power BI tenant (preview) - Azure Purview
Content Source: articles/purview/register-scan-power-bi-tenant.md
Service: purview
Sub-service: purview-data-catalog
GitHub Login: @chanuengg
Microsoft Alias: csugunan

@zeinab-mk can you review this issue

@chanuengg Could you please check email conversion which is attached in issue title and update  doc as appropriate.

We are looking into this now.

@zeinab-mk for viz.

The team is still working on this issue.

We are still working on this issue, thank you for your patience. We are updating the PowerShell modules, and have been working on this since the issue was reported. As soon as it is complete I will update you here and we will update the documentation.

Just following up to let you know we are still working on these PowerShell revisions. As soon as they're ready, I'll update you here and revise the documentation.

Thank you so much for your patience!
We have been working on updating this process, and now have a new portal process that should allow you to connect cross tenant to Power BI.
The documentation has now been updated with the latest process in the portal: https://docs.microsoft.com/en-us/azure/purview/register-scan-power-bi-tenant
Please give these new features a try and reach out again if you have any issue.

#please-close


Error modifing TableRelation: Token StartAttribute in state Element Content would result in an invalid XML document

Describe the bug
If you modify a field of a table, and in that modify you modify TableRelation and also you include a trigger, then you will get the following error:
The request for path /NAV/dev/apps?SchemaUpdateMode=synchronize failed with code 422. Reason: Token StartAttribute in state Element Content would result in an invalid XML document.
Screenshots

Versions:

AL Language: 3.0.126610

Business Central: 14.0.29530.31705

Hi,
Could you provide us with a code sample that reproduces the issue? Having a clear repro will help us in processing this issue faster.
Thanks,
Thaddeus

        modify("Creditor No.")
        {
            TableRelation = "SomeTAble";

            trigger OnAfterValidate()
            var
                something: Codeunit "something";
            begin
            end;
        }

This should reproduce it.

I think you dont need more input, Verndroid show you the case.
Kind regards.

Just wondering, as far as I know the TableRelation property is not available for tableextension. See also this overview: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-table-properties

@ajkauffmann that looks like a documentation bug. Thank you for pointing it out!


[Feature Request] Ignore single line by using comment

Hi, I really like the library so far!
I would like to suggest a feature for ignoring mutation of a single line in a file by using something like a comment.
This feature would be useful in cases where modifying a line may change a filesystem during a test. I would like to present to you my specific use case:
def initialize_database(name: str) -> TinyDB:
  return TinyDB(name) if name != ':memory:' else TinyDB(storage=MemoryStorage)

In this case, I don't want a file named :memory: to be created when running tests, so I would like to ignore this line for the purpose of mutations.
I have seen some other libraries implement a solution that requires a comment such as
def initialize_database(name: str) -> TinyDB:
  return TinyDB(name) if name != ':memory:' else TinyDB(storage=MemoryStorage) # pragma : no mutation

Would this be possible to do for metatest?
Cheers.

Thanks for testing out mutatest and for your suggestion. For large codebases, mutation targets are a random sample out of a large population of potential targets, it's not clear that line-level annotations are pragmatic. I'd suggest test sub-selection  in a way that skips parts of your code where you don't want mutations. By default, mutatest only considers "covered" code from the test suite for the random sample.


i at the airport rn

whatup brocim at the airport. i should board in like 30 mins?

Hey are you still there? I fell asleep.

no i had a water bottle and tsa took me out back and shot me in the head

i am in the hairport agane rn. going to chi cago. do you know aryaj Kumar(https://www.linkedin.com/in/aryaj-kumar). he is a studence there. i will see him, ijn his bed looool. 😄


Tracer based on RVFI

This PR changes how RVFI signals are generated (https://github.com/lowRISC/ibex/issues/151, fixes https://github.com/lowRISC/ibex/issues/147).
It also forwards the uncompressed instruction to the tracer (https://github.com/lowRISC/ibex/issues/154).
As those commits are all closely coupled I think it is easier to do it in one PR.
@taoliug could you please test this before it is merged?

Looks like it has some issue with multi-cycles instruction. The RD value of mulh instruction is shown as X.

ibex trace:
              1729000<PHONE_NUMBER>6 00868693 addi             x13, x13, 8         x13=0x9b25d84a x13:0x9b25d842
              1739000<PHONE_NUMBER>8 4097d793 srai             x15, x15, 0x409     x15=0x0010fc50 x15:0x21f8a000
              1807000<PHONE_NUMBER>a 039597b3 mulh             x15, x11, x25       x15=0xxxxxxxxx x11:0x80000000 x25:0x00000003

spike trace:
core   0: 0xffffffff80000178 (0x000087a5) srai    a5, a5, 9
3 0x80000178 (0x87a5) x15 0x0010fc50
core   0: 0xffffffff8000017a (0x039597b3) mulh    a5, a1, s9
3 0x8000017a (0x039597b3) x15 0xfffffffe
core   0: 0xffffffff8000017e (0x0000199d) addi    s3, s3, -25
3 0x8000017e (0x199d) x19 0x7ffffff0

Thanks a lot @taoliug.
I pushed a fix for that. By the way, is there any commercial tool required to run the simulation with spike? I do not want to waste your time with testing my stuff if I can test it  myself.

Yes, commercial simulator is needed to run UVM TB. I can think about supporting load my test binary in a non-UVM TB which can be run with verilator. It will take some time to setup the flow though. It can be done by enhancing the tracer TB you have right now.

Thanks again for testing @taoliug.
@imphil @vogelpi please wait if you want to review, just found something which does not look right.

Thanks for the review @vogelpi.
I did not see that illegal_insn_id usage was changed in this PR, so I think it would be cleaner to do it in another PR. If you would do it I will be happy to rebase this PR. Thanks.

Thanks for the review @vogelpi.
I did not see that illegal_insn_id usage was changed in this PR, so I think it would be cleaner to do it in another PR. If you would do it I will be happy to rebase this PR. Thanks.
As if_id_pipe_reg_we was removed in the rework of RVFI I will update to remove it.

Okay, sounds good.

The fix for illegal_insn_id is in PR #161 .

Seeing your PR I saw that id_out_valid is also not used anymore. Should I remove id_out_valid_o from ID and controller as well @vogelpi?

Seeing your PR I saw that id_out_valid is also not used anymore. Should I remove id_out_valid_o from ID and controller as well @vogelpi?

Oh yes, good catch. I think this can also be removed entirely.


❔ Settings Hotkey Update

All users need the ability to summon the VIM Visualization settings within a Power BI report within any desktop web browser so that they can turn various tools on and off to complete their various tasks.
Issue: At the moment, our hotkeys are tied to Function keys, and most browsers have these reserved.
Solution: We need to reassign keyboard commands, starting with settings. We will review our existing list and see if there are any other low-hanging opportunities while we're at it.
Edge: https://support.microsoft.com/en-us/microsoft-edge/keyboard-shortcuts-in-microsoft-edge-50d3edab-30d9-c7e4-21ce-37fe2713cfad

Ctrl+/ is reserved by several web apps to summon a command bar, since we can't do that within the overall context of PowerBI, I suggest we use this keyboard combo to summon the user settings panel.

I suspected adding this feature would mean we must republish each report. This could also be a chance to update:

Backgrounds with new title bar visual
Add video buttons (if we use a shortcut url we can always direct to videos when they're done later)
Clean up formatting with some recent updates
Each report will get the latest data set?
Any improvements we've been holding off on

Or do we want to wait until the new publishing process is complete?


add doc for AIDA code gen

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65de88d4fa8df46a37da4505--harness-developer.netlify.app

Per @rustd , we need a live URL for this feature's documentation today. I am going to edit this topic to minimum viable docs and publish it. I will comment out any incomplete work to preserve it for future updates.
You will need to create a new PR after I merge.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65df93474234455b8347e561--harness-developer.netlify.app

thank you @aimurphy. We have some more content in-progress that we want to get deployed before we publish: https://docs.google.com/document/d/1eXAvuAnsFjVh8oH_HnbYAkdNBPMFEyApaTHxCmy5akI/edit

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65df965828fe6765b4b2ef95--harness-developer.netlify.app

thank you @aimurphy. We have some more content in-progress that we want to get included before we publish: https://docs.google.com/document/d/1eXAvuAnsFjVh8oH_HnbYAkdNBPMFEyApaTHxCmy5akI/edit

We need the initial page today as a priority. You are welcome to update again & create a new PR from your feature branch when you have the additional content ready. I apologize that I had to stick another page in this PR, it was a rush request.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65df97ee0c7658670523292f--harness-developer.netlify.app


Default IP address is retrieved with nix instead of pnet

Fixes #67

I fixed #103 on upstream and this one on origin. I had to rebase this branch.


Added danish JSON translation

Once more I have updated the pull request with changes.

Please, delete your updates on README and I will merge

Reverted readme changes. Ready for merge. @caouecs

Tak


Added code analyzers and fixed locale issues.

Fixes #154.
All program parsing and output should now use InvariantCulture or StringComparison.Invariant.
Currently, the output for logging etc. uses CurrentCulture instead of InvariantCulture.
This is the same behaviour as before, but now explicit to mark those places as not processed. However, it may be better to set these to English or Invariant too, since the error messages aren't localised.

I added the FxCop Analyzers to the project to find the locale problems, so warnings for certain issues should now show up when building with the Roslyn infrastructure. This happens with Visual Studio for example, but please check that I didn't break anything for your workflow.
I did some tiny fixes where suppressing the warning would have been more effort, but there are many warnings I just suppressed for now. I'll mark them in the commit via comment where appropriate, if that's supported here.

Almost forgot to update CONTRIBUTORS.md since it's not mentioned in CONTRIBUTING.md.
Sorry about that force-push. I forgot to pull the typo fix first and had a merge commit in there. Now it's nice and linear.

This is an excellent pull request. Thank you very much!


added A-Z alphabet learning extension for kids

Description
An extension for every toddler that reads aloud the english alphabet as well the word that starts by it. It is going to be like that keyboard that kids backs in the day had that would read aloud the alphabet and words as they were pressed.
Fixes:  #1650

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK
https://github.com/Sulagna-Dutta-Roy/GGExtensions/assets/142666229/541ff578-acc1-45d1-9ab8-af972ec3901b

Please review my pull request @Sulagna-Dutta-Roy


Fix/flakey integration tests

Fixed

Fixes #292 failing integration tests

Can no longer reproduce issue. Will leave branch open in-case this happens again and will investigate further.

Already merged into #291 which is now merged to master. Closing PR.


Help me please

Hi there
Can I ask you please help me how to add Arduino_stm32 board at below link to the "compilersettings.py" file like this one:
'ESP8266 Huzzah': 'esp8266:esp8266:generic',
I'm using stm32f103c8t6
https://github.com/rogerclarkmelbourne/Arduino_STM32
Many thanks.

Hello,  thanks for email, but at moment I can not answer you because I am
ill,,maybe next week I will be fit again....
next week I will get in contact again...
Thanks
2018-06-13 16:05 GMT+02:00 Ehsan Moradi<EMAIL_ADDRESS>
Hi there
Can I ask you please help me how to add Arduino_stm32 board at below link
to the "compilersettings.py" file like this one:
'ESP8266 Huzzah': 'esp8266:esp8266:generic',
I'm using stm32f103c8t6
https://github.com/rogerclarkmelbourne/Arduino_STM32
Many thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/carlosperate/ardublockly/issues/211, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AOMCoDmduT6xRD2-7TS_foOgqT4UrxGNks5t8RxGgaJpZM4UmRDG
.

Thanks a lot, I'm waiting for your help


make sure changes from PR #779 are reflected in sheets_and_friends Google sheet

#779

I don't see any of those typos in any of the sheets-for-nmdc-submission-schema variants I'm aware of, either in the Google Drive or in sheets_and_friends
Although we don't ahve any strategy for making sure these documents stay in sync with one another
or


Multi-arch docker image with M1 support

Currently the Docker image doesn't run on Macs with Apple silicon (arm64).

@jkarneges, can you try this?
https://hub.docker.com/r/zimbres/pushpin

@zimbres do you have the sourcecode for that?

@julianpoy
pushpin-docker


Add openssl-dev pkg as dependencies in Dockerfile

Since Actix or Sentry the Docker image can not be built.
Should I add in the GitHub actions a test wether we can build or not the Docker image when anyone makes a pull request?

Should I add in the GitHub actions a test wether we can build or not the Docker image when anyone makes a pull request?

I am not, sure, it takes many time to build, we didn't released anything with actix for now and we would have found ot that the Docker image couldn't be built when we were trying to release, so. It seems ok.
Could you add a line about actix in the Changelog file please?
Something in the line of:
- Change the HTTP framework, moving from tide to actix-web #601

I have a fix to remove openssl from all the package by tuning sentry features

Yeah, absolutelly but what is the downside of this sentry tuning? If all sentry requests becomes unsafe: non-ssl secured, I don't think that this is good. Or is it a feature that makes sentry use rustls?

Yes, in fact, it already uses rustls but we haven't removed the feature that includes also openssl on request

Yep, I dont mind adding openssl dependency, I was afraid because the image was getting bigger but apparently it's because of the whole sentry feature, not just openssl ^^
On a different subject @Kerollmops, I can see that the test that are launched on each pull request take up to 18 minutes, while building the docker image is maximum 14min.
I think the different GitHub actions are launched in parallel so that won't slow down the time needed for each PR.

@qdequele, for go on and remove this openssl dependency :)
@thomas, ok for adding a new test to the CI, waiting for your PR :)

I will update the changelog on #705


Adds rake tasks to audit the Fedora 3 to Fedora 4 migration

This pull request adds a few rake tasks to audit the migration of objects from Fedora 3 to Fedora 4. The idea is that these tasks will be run after deploying the Fedora 4 code base to production and immediately after the migration of data has been performed.
The code to perform the audit issues straight HTTP requests to Fedora 3 and Fedora 4 and bypasses Rubydora and ActiveFedora to make sure we query the Fedora repo as close to the metal as possible.
The following Wiki page provides some information on how these rake tasks will be run in production: https://github.com/psu-stewardship/scholarsphere/wiki/Fedora-3-to-Fedora-4-Migration

@awead @cam156 @mjgiarlo This is the latest on the code to audit the Fedora 3 to Fedora 4 migration.
This code includes the suggestions that Adam made earlier this week (on a PR that I deleted.) Notice that I only added unit tests to test the code from the Fedora 4 point of view since I didn't want to be running tests against both Fedora 3 and Fedora 4 in the same code base.
The unit tests stub the results that the Fedora 3 repo will have and then creates them in Fedora 4 and compares the two.

@cam156 @mjgiarlo so I went :banana: :banana: :banana: with the comments. I want to say that overall, I'm :100: :+1: with this as is. I was just exercising a bit here, in case @hectorcorrea wanted some deeper level comments. Feel free to provide additional suggestions.
The only thing I'm not sure of are all the changes to schema.rb but that's just me. If we want to pull this code out eventually, that might make the schema a little weird to deal with later, but I'm not too familiar with this on the Rails side.

:+1: to @awead's comments! These are useful pointers. Thanks for whipping this up and working through the PR process, @hectorcorrea

@awead @mjgiarlo I've implemented most of the suggestions that @awead provided. Thanks a lot for the comprehensive feedback. I also removed a few hash rockets that you guys missed ;)
The suggestions that I didn't implement are the ones that were along the lines of "reduce these the 3 lines to a single line" when I thought the assignment of the variables line by line made the code clearer (and easier to debug) than the suggested single line approach.
I also left a few string concatenations in place (instead of replacing them with string interpolation) when I I thought the concatenation made the operation easier to read.

:clap:


test(coverage): improve coverage config

Description
I've noticed that the test coverage is collecting data from dist and src.
Motivation and Context
Improve the collaboration experience and maintenance.
It will also enable a better yarn test --watch usability, cause the test-kit will look for the source code.
Previous coverage result
---------------------------|---------|----------|---------|---------|------------------------------------------
File                       | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
---------------------------|---------|----------|---------|---------|------------------------------------------
All files                  |   84.66 |    72.65 |   82.07 |   84.95 |
 dist                      |    90.8 |    74.63 |   92.86 |   90.94 |
  _handlers.js             |   91.18 |       68 |     100 |   91.18 | 48,54,65
  config-factory.js        |   96.88 |    82.61 |     100 |   96.88 | 38
  context-matcher.js       |   94.44 |       90 |     100 |   94.44 | 25,32
  errors.js                |     100 |      100 |     100 |     100 |
  http-proxy-middleware.js |    96.2 |    83.67 |     100 |    96.2 | 101-102,125
  index.js                 |   84.21 |    68.75 |      80 |   85.71 | 6-7
  logger.js                |   70.69 |       50 |   81.25 |   70.18 | 38,42,51-52,73,81,118-133
  path-rewriter.js         |   97.06 |    81.25 |     100 |   97.06 | 51
  router.js                |     100 |       90 |     100 |     100 | 13
 dist/handlers             |   43.21 |    52.63 |   33.33 |   42.25 |
  fix-request-body.js      |   92.86 |       90 |     100 |   92.86 | 10
  index.js                 |   78.57 |    68.75 |      75 |   77.78 | 6-7
  public.js                |    87.5 |      100 |      50 |     100 |
  response-interceptor.js  |    8.89 |        0 |       0 |    9.52 | 13-31,41-84
 src                       |   89.53 |    77.84 |   90.38 |   89.49 |
  _handlers.ts             |   96.88 |       96 |      75 |   96.88 | 87
  config-factory.ts        |   93.33 |    82.61 |     100 |   93.33 | 84,88
  context-matcher.ts       |     100 |      100 |     100 |     100 |
  errors.ts                |     100 |      100 |     100 |     100 |
  http-proxy-middleware.ts |   63.64 |    32.65 |   63.64 |   63.64 | ...96-99,141-147,164-168,176-181,187-194
  index.ts                 |     100 |      100 |     100 |     100 |
  logger.ts                |     100 |       95 |     100 |     100 | 72-78
  path-rewriter.ts         |     100 |    93.75 |     100 |     100 | 57
  router.ts                |     100 |      100 |     100 |     100 |
 src/handlers              |      80 |    45.45 |   71.43 |   78.18 |
  fix-request-body.ts      |   16.67 |        0 |       0 |   16.67 | 9-25
  index.ts                 |     100 |      100 |     100 |     100 |
  public.ts                |     100 |      100 |      50 |     100 |
  response-interceptor.ts  |   95.35 |    83.33 |      90 |      95 | 48,109
 test/e2e                  |     100 |      100 |      80 |     100 |
  test-kit.ts              |     100 |      100 |      80 |     100 |
---------------------------|---------|----------|---------|---------|------------------------------------------

Coverage result after config changes
---------------------------|---------|----------|---------|---------|-------------------
File                       | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
---------------------------|---------|----------|---------|---------|-------------------
All files                  |   98.31 |    91.79 |   98.48 |   98.29 |
 src                       |   98.99 |    92.43 |     100 |   98.98 |
  _handlers.ts             |     100 |       96 |     100 |     100 | 70
  config-factory.ts        |     100 |     91.3 |     100 |     100 | 29,79
  context-matcher.ts       |     100 |      100 |     100 |     100 |
  errors.ts                |     100 |      100 |     100 |     100 |
  http-proxy-middleware.ts |    96.1 |    83.67 |     100 |    96.1 | 141-147,181
  index.ts                 |     100 |      100 |     100 |     100 |
  logger.ts                |     100 |       95 |     100 |     100 | 72-78
  path-rewriter.ts         |     100 |    93.75 |     100 |     100 | 57
  router.ts                |     100 |      100 |     100 |     100 |
 src/handlers              |      95 |    86.36 |   92.86 |   94.55 |
  fix-request-body.ts      |   91.67 |       90 |     100 |   91.67 | 10
  index.ts                 |     100 |      100 |     100 |     100 |
  public.ts                |     100 |      100 |     100 |     100 |
  response-interceptor.ts  |   95.35 |    83.33 |      90 |      95 | 48,109
---------------------------|---------|----------|---------|---------|-------------------

How has this been tested?
Not need
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Coverage increased (+13.3%) to 98.286% when pulling 3cda05ad8ae0ebeaee84d4b803b9371576dfe3e2 on leonardobazico:coverage into c935888ea7135365bea3c4c81e4ffe48f359a670 on chimurai:master.

Thanks, this was on my TODO list.
This reason for testing dist was due this little annoying TypeScript behaviour:
https://github.com/chimurai/http-proxy-middleware/blob/c935888ea7135365bea3c4c81e4ffe48f359a670/src/http-proxy-middleware.ts#L45-L46
Testing it purely in typescript src didn't caught this issue.
Think it makes sense to create a separate dist test, so it doesn't affect the developer experience.


Great Work! Ask for the Demo

Hi @Yangsenqiao ,
I’m Denny, a PhD student with a strong interest in Vision-Language Models. I found your demo particularly fascinating, especially its ability to interactively select visual tokens. I believe this feature could be incredibly useful for assessing the importance of different tokens.
Would you be able to share the code for the demo or provide guidance on how to develop a similar implementation?
Thank you in advance for your time and assistance!
Best regards,
Denny

Hi Denny,
Thank you for your interest in our work! Since this demo involves some modifications to the LLaVA code itself, it may not be as straightforward or concise to release as VisionZip. Please kindly allow me some time to consider an appropriate release method.
Best,
Senqiao

Hi Denny,
We have uploaded the demo code to the new branch, 'demo-chat'. :wave:
And the code is based on the LLaVA framework with modifications. To help with analysis, we've provided the original unmodified LLaVA code in the commit 49b53a00dfd3a2d62ab79b8fdf5bc20d41b17ab9. You can compare this with the latest version to see the changes made.
I will close this issue. If you have any further questions, feel free to open a new issue or re-open this one. :blush:
Best,
Senqiao


 ECONNRESET : EFAULT, -1, "failed to send request");
/overlaybd/build/_deps/photon-src/include/photon/common/alog.h:552:14: note: in definition of macro ‘LOG_ERRNO_RETURN’
552 |     errno = (new_errno) ? (new_errno) : eno.no;
|              ^~~~~~~~~
/overlaybd/build/_deps/photon-src/rpc/rpc.cpp:174:57: warning: ?: using integer constants in boolean context, the expression will always evaluate to true’ [-Wint-in-bool-context]
174 |                 LOG_ERRNO_RETURN((err.no == ECONNRESET) ? ECONNRESET : EFAULT, -1, "failed to receive response ");
/overlaybd/build/_deps/photon-src/include/photon/common/alog.h:552:14: note: in definition of macro ‘LOG_ERRNO_RETURN’
552 |     errno = (new_errno) ? (new_errno) : eno.no;
|              ^~~~~~~~~
/overlaybd/build/_deps/photon-src/net/utils.cpp: In function ‘void photon::net::base64_translate_3to4(const char*, char*)’:
/overlaybd/build/_deps/photon-src/net/utils.cpp:97:12: note: offset of packed bit-field ‘photon::net::base64_translate_3to4(const char*, char*)::xlator::b’ has changed in GCC 4.4
97 |     struct xlator {
|            ^~~~~~
/overlaybd/build/_deps/photon-src/net/utils.cpp:97:12: note: offset of packed bit-field ‘photon::net::base64_translate_3to4(const char*, char*)::xlator::c’ has changed in GCC 4.4
/overlaybd/build/_deps/photon-src/net/utils.cpp:108:15: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasin]
108 |     auto x = (xlator )(&v);
|               ^~~~~~~~~~~~~~
/overlaybd/build/_deps/photon-src/net/utils.cpp:108:15: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasin]
/overlaybd/build/_deps/photon-src/net/utils.cpp: In function ‘bool photon::net::base64_translate_4to3(const char, char)’:
/overlaybd/build/_deps/photon-src/net/utils.cpp:188:12: note: offset of packed bit-field ‘photon::net::base64_translate_4to3(const char*, char*)::xlator::b’ has changed in GCC 4.4
188 |     struct xlator {
|            ^~~~~~
/overlaybd/build/_deps/photon-src/net/utils.cpp:188:12: note: offset of packed bit-field ‘photon::net::base64_translate_4to3(const char*, char*)::xlator::c’ has changed in GCC 4.4
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [_deps/photon-build/CMakeFiles/photon_obj.dir/build.make:622: _deps/photon-build/CMakeFiles/photon_obj.dir/rpc/rpc.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [src/overlaybd/cache/frontend/CMakeFiles/cache_frontend_lib.dir/build.make:63: src/overlaybd/cache/frontend/CMakeFiles/cache_frontend_lib.dir/cached_file.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [src/overlaybd/cache/full_file_cache/CMakeFiles/full_file_cache_lib.dir/build.make:63: src/overlaybd/cache/full_file_cache/CMakeFiles/full_file_cache_lib.dir/cache_pool.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....

itseems gcc  4.4 is used from the error info. it is too low, 7+ is preferred

itseems gcc 4.4 is used from the error info. it is too low, 7+ is preferred

$gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
I have no idea why gcc is changed to 4.4 version!

‘photon::net::base64_translate_4to3(const char*, char*)::xlator::c’ has changed in GCC 4.4

@liulanzheng I think it means something has already changed since GCC 4.4

$cmake ..
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Populating photon
-- Configuring done
-- Generating done
-- Build files have been written to: /users/Zhihao/cpp/overlaybd/build/_deps/photon-subbuild
Scanning dependencies of target photon-populate
[ 11%] Creating directories for 'photon-populate'
[ 22%] Performing download step (git clone) for 'photon-populate'
Cloning into 'photon-src'...
Note: switching to 'v0.5.6'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 5cf4719 Update alog.cpp
[ 33%] No patch step for 'photon-populate'
[ 44%] Performing update step for 'photon-populate'
[ 55%] No configure step for 'photon-populate'
[ 66%] No build step for 'photon-populate'
[ 77%] No install step for 'photon-populate'
[ 88%] No test step for 'photon-populate'
[100%] Completed 'photon-populate'
[100%] Built target photon-populate
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Performing Test COMPILER_HAS_MCRC32_FLAG
-- Performing Test COMPILER_HAS_MCRC32_FLAG - Success
-- Found aio: /usr/lib/x86_64-linux-gnu/libaio.so
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1.1.1f")
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
-- Found CURL: /usr/lib/x86_64-linux-gnu/libcurl.so (found version "7.68.0")
-- Populating tcmu
-- Configuring done
-- Generating done
-- Build files have been written to: /users/Zhihao/cpp/overlaybd/build/_deps/tcmu-subbuild
Scanning dependencies of target tcmu-populate
[ 11%] Creating directories for 'tcmu-populate'
[ 22%] Performing download step (git clone) for 'tcmu-populate'
Cloning into 'tcmu-src'...
Already on 'main'
Your branch is up to date with 'origin/main'.
[ 33%] No patch step for 'tcmu-populate'
[ 44%] Performing update step for 'tcmu-populate'
Current branch main is up to date.
[ 55%] No configure step for 'tcmu-populate'
[ 66%] No build step for 'tcmu-populate'
[ 77%] No install step for 'tcmu-populate'
[ 88%] No test step for 'tcmu-populate'
[100%] Completed 'tcmu-populate'
[100%] Built target tcmu-populate
-- Found nl: /usr/lib/x86_64-linux-gnu/libnl-3.so;/usr/lib/x86_64-linux-gnu/libnl-genl-3.so
-- Populating rapidjson
-- Configuring done
-- Generating done
-- Build files have been written to: /users/Zhihao/cpp/overlaybd/build/_deps/rapidjson-subbuild
Scanning dependencies of target rapidjson-populate
[ 11%] Creating directories for 'rapidjson-populate'
[ 22%] Performing download step (git clone) for 'rapidjson-populate'
Cloning into 'rapidjson-src'...
Note: switching to '80b6d1c83402a5785c486603c5611923159d0894'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 80b6d1c8 small corrections for schema.h
Submodule 'thirdparty/gtest' (https://github.com/google/googletest.git) registered for path 'thirdparty/gtest'
Cloning into '/users/Zhihao/cpp/overlaybd/build/_deps/rapidjson-src/thirdparty/gtest'...
Submodule path 'thirdparty/gtest': checked out 'ba96d0b1161f540656efdaed035b3c062b60e006'
[ 33%] No patch step for 'rapidjson-populate'
[ 44%] Performing update step for 'rapidjson-populate'
[ 55%] No configure step for 'rapidjson-populate'
[ 66%] No build step for 'rapidjson-populate'
[ 77%] No install step for 'rapidjson-populate'
[ 88%] No test step for 'rapidjson-populate'
[100%] Completed 'rapidjson-populate'
[100%] Built target rapidjson-populate
-- Populating ext2fs
-- Configuring done
-- Generating done
-- Build files have been written to: /users/Zhihao/cpp/overlaybd/build/_deps/ext2fs-subbuild
Scanning dependencies of target ext2fs-populate
[ 11%] Creating directories for 'ext2fs-populate'
[ 22%] Performing download step (download, verify and extract) for 'ext2fs-populate'
-- Downloading...
dst='/users/Zhihao/cpp/overlaybd/build/_deps/ext2fs-subbuild/ext2fs-populate-prefix/src/libext2fs.tar.gz'
timeout='none'
-- Using src='https://github.com/data-accelerator/e2fsprogs/releases/download/latest/libext2fs.tar.gz'
-- [download 2% complete]
-- [download 4% complete]
-- [download 5% complete]
-- [download 11% complete]
-- [download 17% complete]
-- [download 23% complete]
-- [download 28% complete]
-- [download 34% complete]
-- [download 40% complete]
-- [download 46% complete]
-- [download 51% complete]
-- [download 57% complete]
-- [download 63% complete]
-- [download 69% complete]
-- [download 74% complete]
-- [download 80% complete]
-- [download 86% complete]
-- [download 91% complete]
-- [download 97% complete]
-- [download 100% complete]
-- Downloading... done
-- extracting...
src='/users/Zhihao/cpp/overlaybd/build/_deps/ext2fs-subbuild/ext2fs-populate-prefix/src/libext2fs.tar.gz'
dst='/users/Zhihao/cpp/overlaybd/build/_deps/ext2fs-src'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done
[ 33%] No patch step for 'ext2fs-populate'
[ 44%] No update step for 'ext2fs-populate'
[ 55%] No configure step for 'ext2fs-populate'
[ 66%] No build step for 'ext2fs-populate'
[ 77%] No install step for 'ext2fs-populate'
[ 88%] No test step for 'ext2fs-populate'
[100%] Completed 'ext2fs-populate'
[100%] Built target ext2fs-populate
-- Configuring done
-- Generating done
-- Build files have been written to: /users/Zhihao/cpp/overlaybd/build

@qi0523 these info are warning, and i think these warnings should not lead to failure.

@qi0523  this line is suspicious: c++: fatal error: Killed signal terminated program cc1plus, it seems compilation was killed. did the memory full or other abnormal cases on the system during compiling?

Details are as follows:
Firstly, when using
FetchContent_Declare(
  photon
  GIT_REPOSITORY https://github.com/alibaba/PhotonLibOS.git
  GIT_TAG v0.5.6
)

errors are as follows:
Scanning dependencies of target easy_weak
Scanning dependencies of target photon_obj
Scanning dependencies of target full_file_cache_lib
Scanning dependencies of target lsmt_lib
Scanning dependencies of target registryfs_lib
Scanning dependencies of target crc32_lib
Scanning dependencies of target cache_frontend_lib
Scanning dependencies of target ocf_env_lib
Scanning dependencies of target download_cache_lib
Scanning dependencies of target tar_lib
[  1%] Building CXX object _deps/photon-build/third_party/CMakeFiles/easy_weak.dir/easy_weak/easy_weak.cpp.o
Scanning dependencies of target baselayer
[  1%] Building CXX object src/overlaybd/lsmt/CMakeFiles/lsmt_lib.dir/file.cpp.o
[  2%] Building CXX object src/overlaybd/lsmt/CMakeFiles/lsmt_lib.dir/index.cpp.o
[  2%] Building CXX object src/overlaybd/cache/full_file_cache/CMakeFiles/full_file_cache_lib.dir/cache_pool.cpp.o
[  3%] Building CXX object src/overlaybd/zfile/CMakeFiles/crc32_lib.dir/crc32/crc32c.cpp.o
[  4%] Building CXX object src/overlaybd/cache/full_file_cache/CMakeFiles/full_file_cache_lib.dir/cache_store.cpp.o
[  4%] Building CXX object src/overlaybd/cache/frontend/CMakeFiles/cache_frontend_lib.dir/cached_file.cpp.o
[  5%] Building CXX object src/overlaybd/cache/ocf_cache/CMakeFiles/ocf_env_lib.dir/ease_bindings/env/utils_mpool.cpp.o
[  5%] Generating ../output/ext4_64
[  7%] Building CXX object src/overlaybd/cache/frontend/CMakeFiles/cache_frontend_lib.dir/cached_fs.cpp.o
[  6%] Building CXX object src/overlaybd/tar/CMakeFiles/tar_lib.dir/libtar.cpp.o
[  6%] Building CXX object src/overlaybd/cache/ocf_cache/CMakeFiles/ocf_env_lib.dir/ease_bindings/env/ocf_env.cpp.o
[  7%] Building CXX object src/overlaybd/tar/CMakeFiles/tar_lib.dir/header.cpp.o
[  7%] Building CXX object src/overlaybd/tar/CMakeFiles/tar_lib.dir/tar_file.cpp.o
[  8%] Building CXX object src/overlaybd/tar/CMakeFiles/tar_lib.dir/whiteout.cpp.o
[  9%] Building CXX object src/overlaybd/cache/download_cache/CMakeFiles/download_cache_lib.dir/download_cache.cpp.o
[  9%] Building CXX object src/overlaybd/registryfs/CMakeFiles/registryfs_lib.dir/registryfs_v2.cpp.o
[ 10%] Building CXX object src/overlaybd/registryfs/CMakeFiles/registryfs_lib.dir/registryfs.cpp.o
ext4_64
[ 11%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/identity-pool.cpp.o
[ 13%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/alog.cpp.o
[ 15%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/executor/executor.cpp.o
[ 14%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/estring.cpp.o
[ 14%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/expirecontainer.cpp.o
[ 14%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/checksum/crc32c.cpp.o
[ 16%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/ring.cpp.o
[ 15%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/memory-stream/memory-stream.cpp.o
[ 15%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/event-loop.cpp.o
[ 16%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/iovector.cpp.o
[ 16%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/perf_counter.cpp.o
[ 16%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/stream-messenger/messenger.cpp.o
[ 17%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/utility.cpp.o
[ 18%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/aligned-file.cpp.o
[ 17%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/common/uuid4.cpp.o
[ 18%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/async_filesystem.cpp.o
[ 19%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/exportfs.cpp.o
[ 20%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/httpfs/httpfs.cpp.o
[ 20%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/filecopy.cpp.o
[ 20%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/httpfs/httpfs_v2.cpp.o
[ 20%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/path.cpp.o
[ 21%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/localfs.cpp.o
[ 21%] Built target baselayer
[ 21%] Linking CXX static library ../output/libeasy_weak.a
[ 21%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/subfs.cpp.o
[ 21%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/virtual-file.cpp.o
[ 22%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/throttled-file.cpp.o
[ 23%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/curl.cpp.o
[ 23%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/fs/xfile.cpp.o
[ 24%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/basic_socket.cpp.o
[ 24%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/io/signal.cpp.o
[ 25%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/body.cpp.o
[ 26%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/cookie_jar.cpp.o
[ 27%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/message.cpp.o
[ 27%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/headers.cpp.o
[ 27%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/server.cpp.o
[ 27%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/client.cpp.o
[ 28%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/status.cpp.o
[ 29%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/kernel_socket.cpp.o
[ 29%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/http/url.cpp.o
[ 29%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/utils.cpp.o
[ 30%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/security-context/tls-stream.cpp.o
[ 30%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/net/pooled_socket.cpp.o
[ 30%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/rpc/out-of-order-execution.cpp.o
[ 31%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/photon.cpp.o
[ 32%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/thread/thread-key.cpp.o
[ 32%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/thread/thread-pool.cpp.o
[ 32%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/thread/workerpool.cpp.o
[ 33%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/io/aio-wrapper.cpp.o
[ 34%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/thread/thread.cpp.o
[ 34%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/thread/std-compat.cpp.o
[ 34%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/io/epoll.cpp.o
[ 35%] Building CXX object _deps/photon-build/CMakeFiles/photon_obj.dir/rpc/rpc.cpp.o
[ 35%] Built target easy_weak
/overlaybd/build/_deps/photon-src/fs/filecopy.cpp: In function ‘ssize_t photon::fs::filecopy(photon::fs::IFile*, photon::fs::IFile*, size_t, int)’:
/overlaybd/build/_deps/photon-src/fs/filecopy.cpp:36:21: warning: ignoring return value of ‘int posix_memalign(void**, size_t, size_t)’, declared with attribute warn_unused_result [-Wunused-result]
36 |     ::posix_memalign(&buff, ALIGNMENT, bs);
|     ^~~~~~
/overlaybd/build/_deps/photon-src/net/basic_socket.cpp: In lambda function:
/overlaybd/build/_deps/photon-src/net/basic_socket.cpp:240:54: error: expected ‘{’ before ‘->’ token
240 |     auto func = & attribute((always_inline)) -> ssize_t {
|                                                      ^~
/overlaybd/build/_deps/photon-src/net/basic_socket.cpp: In function ‘ssize_t photon::net::sendfile_fallback(photon::net::ISocketStream*, int, off_t, size_t, uint64_t)’:
/overlaybd/build/_deps/photon-src/net/basic_socket.cpp:240:54: error: base operand of ‘->’ has non-pointer type ‘photon::net::sendfile_fallback(photon::net::ISocketStream*, int, off_t, size_t, uint64_t)::<lambda()>’
/overlaybd/build/_deps/photon-src/net/basic_socket.cpp:238:10: warning: unused variable ‘buf’ [-Wunused-variable]
238 |     char buf[64 * 1024];
Then, using
FetchContent_Declare(
  photon
  GIT_REPOSITORY https://github.com/alibaba/PhotonLibOS.git
  GIT_TAG v0.5.1
)

errors are as above.

@qi0523 this line is suspicious: c++: fatal error: Killed signal terminated program cc1plus, it seems compilation was killed. did the memory full or other abnormal cases on the system during compiling?

When saw the error message, I terminated it.

itseems gcc 4.4 is used from the error info. it is too low, 7+ is preferred

$gcc -v
Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Thread model: posix gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
I have no idea why gcc is changed to 4.4 version!

@qi0523
I just tried compiling on ubuntu 20.04 with gcc 9.4.0 and it worked well.
my gcc info is as below:
root@iZ6wef2lh14l7m4n84l1c1Z:~/overlaybd# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.4.0-1ubuntu1~20.04.1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-Av3uEd/gcc-9-9.4.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
the main different other than version is at Configured with:, did you hide it or no content?  Some users have encountered with similar issue before by using a misconfigured or not configured gcc.

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-17ubuntu1.20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)

I have no idea
@lihuiba  @Coldwings  @beef9999  cc
the error is in photon basic_socket.cpp

I have no idea @lihuiba @Coldwings @beef9999 cc the error is in photon basic_socket.cpp

Yes, gcc can not identify this lambda!

@qi0523 Can you modify this basic_socket.cpp at line 240, and try below methods?

Change __attribute__((always_inline)) to inline
Remove __attribute__((always_inline))


fix: change "import" button label to "add" on files screen

Changed "import" button label to "add" on files screen to better fit new folder option. As suggested by #1951.

@brainsaysno thanks so much for getting this out so quickly. We discussed this in our GUI triage meeting and there seems to be a use-case for leaving import, but I think we agreed on adding a "Add new folder" button or similar. I'll update #1951


After updating outdated dependencies got issue to run mean app

Very first issue I got when I updated outdated dependencies, for ref I have pasted the package.json file content. error :  callback provided to sync glob Ref: https://github.com/isaacs/node-glob/issues/167 , then I modified config code and init code https://gist.github.com/nishant8BITS/f4ce80ce3e976f7532b3 and fix the callback provided to sync glob issue, then I run grunt I got error : https://gist.github.com/nishant8BITS/0d6dc5e51355c476d9ab
{
	"name": "meanjs",
	"description": "Full-Stack JavaScript with MongoDB, Express, AngularJS, and Node.js.",
	"version": "0.3.3",
	"private": false,
	"author": "https://github.com/meanjs/mean/graphs/contributors",
	"repository": {
		"type": "git",
		"url": "https://github.com/meanjs/mean.git"
	},
	"engines": {
		"node": ">=0.10.28",
		"npm": ">=1.4.28"
	},
	"scripts": {
		"start": "grunt",
		"test": "grunt test",
		"postinstall": "bower install --config.interactive=false"
	},
	"dependencies": {
		"express": "~4.12.4",
		"express-session": "~1.11.3",
		"body-parser": "~1.13.1",
		"cookie-parser": "~1.3.2",
		"compression": "~1.5.0",
		"method-override": "~2.3.0",
		"morgan": "~1.6.0",
		"connect-mongo": "~0.8.1",
		"connect-flash": "~0.1.1",
		"helmet": "~0.9.1",
		"consolidate": "~0.13.1",
		"swig": "~1.4.1",
		"mongoose": "~4.0.5",
		"passport": "~0.2.0",
		"passport-local": "~1.0.0",
		"passport-facebook": "~2.0.0",
		"passport-twitter": "~1.0.2",
		"passport-linkedin": "~0.1.3",
		"passport-google-oauth": "~0.2.0",
		"passport-github": "~0.1.5",
		"lodash": "~3.9.3",
		"forever": "~0.14.1",
		"bower": "~1.4.1",
		"grunt-cli": "~0.1.13",
		"glob": "~5.0.10",
		"async": "~1.2.1",
		"nodemailer": "~1.3.0",
		"chalk": "~1.0.0"
	},
	"devDependencies": {
		"supertest": "~1.0.1",
		"should": "~7.0.1",
		"grunt-env": "~0.4.1",
		"grunt-node-inspector": "~0.2.0",
		"grunt-contrib-watch": "~0.6.1",
		"grunt-contrib-jshint": "~0.11.2",
		"grunt-contrib-csslint": "^0.4.0",
		"grunt-ng-annotate": "~1.0.1",
		"grunt-contrib-uglify": "~0.9.1",
		"grunt-contrib-cssmin": "~0.12.3",
		"grunt-nodemon": "~0.4.0",
		"grunt-concurrent": "~2.0.0",
		"grunt-mocha-test": "~0.12.1",
		"grunt-karma": "~0.11.0",
		"load-grunt-tasks": "~3.2.0",
		"grunt-contrib-copy": "0.8",
		"karma": "~0.12.0",
		"karma-jasmine": "~0.3.5",
		"karma-coverage": "~0.4.2",
		"karma-chrome-launcher": "~0.1.2",
		"karma-firefox-launcher": "~0.1.3",
		"karma-phantomjs-launcher": "~0.2.0"
	}
}

I guess the best way to solve this - fork project and let's see what did you change at first.

@isotnikov  I did same.

Ok, good. Give us the link.

@isotnikov https://github.com/nishant8BITS/mean/tree/mean-dependency-update

@nishant8BITS - Are you setting your NODE_ENV upon execution?

@nishant8BITS can you explain what is not working exactly?I suspect @codydaig is on the right track there and would anyway suggest to clone 0.4.0 branch again

Closing due to no update


new implementation for positional encoding

New Feature Summary
ATM we have implemented three positional encoding scheme in the trainer code, but the way it's implemented for training as well as shipped in the app package (as checkpoint files) is very confusing for both devs and users. I'd like to address this problem by re-implementing the positional encoding in a simpler, robust way.
Current status (https://github.com/clamsproject/app-swt-detection/pull/26) and problems

we have three schemes (fractional, sinusoidal-concat, sinusoidal-add) for positional encoding but they behave different in different ways, which adds

confusion for model developers in terms different dimensions of vector representation,

fractional will add 1 more dimension to the backbone CNN vectors
sinusoidal-concat will add arbitrary number of dimension (some powers of 2, usually 256 or 512) to the backbone CNN vectors
sinusoidal-add does not add additional dimension

confusion between concepts of "absolute" and "relative" encoding. Sinusoidal encodings are inspired by the transfomer paper, where the original problem of "position" was token position in natural language sentences. That made sense since the main purpose of positional encoding in transformer architecture is to provide relative difference "between tokens", and to proxy a sequential representation. However, current CNN-based classification SWT model is not at all sequential, hence the absoluteness of the sinusoidal encoding makes not much sense here.
difficulties in grid search and result probing - this is simply by adding too much variation to the equation.
unnecessary limitation on input data format (#100)

Proposal
I'm proposing

we always use "sinusoidal-add": this will not change the dimension of feature vectors, and we will keep the CNN-backbone dims regardless of usage of positional encoding
we always use "relative" position: since absolute different between time 00:00:07 and 00:00:08 is not relevant information for current isolated image-based classifier.
we expose "on-off" switch of positional encoding in the runtime parameter: this implies that we always train two models given a set of hyperparams - one with sinusoidal-add, and another without - and the evaluation will be delegated to a separate evaluation module, possibly as a part of https://github.com/clamsproject/aapb-evaluations/issues/43

Related
No response
Alternatives
No response
Additional context
No response

As we can approximate pos_enc_name="none" by using pos_enc_coeff=0, we decided to completely drop the pos_enc_name config key.


[Feature Request] Item Groups and Grouping inside EMI

Even though I really like EMI and use it a lot, I am a bit nostalgic about REI feature for grouping items. Yes it needed to be done by hand by writing a bit of code, but in the end i was able to group similar items (like colored wool, buttons and such) into the same item so it doesn't waste space on the panel and i could expand and collapse when needed.
Will similar feature come to the EMI? I believe it would be very handy for people who have a lot of mods installed or want to clean their item list. I haven't seen this feature in the docs so i decided to submit a feature request. I also understand such a feature would be very hard to implement, especially if you go all user friendly and allow users to create groups inside the game (which is like a very good feature for many reasons as users don't have to leave the game and can tidy up their cluttered panels especially when there are lots of mods) unlike REI does.

Emi already stated that she does not intend to include other’s original ideas like item grouping in EMI, it would be very handy but it’s understandable that she wants EMI to be its own original project.

That's a very strange stance. No single mod holds a monopoly on general features, such as item grouping. And not including some features, just because it makes you a bit more similar to another mod only limits your own mod and doesn't really achieve anything meaningful.

If you really want it, you could develop an addon for EMI that adds the functionality

Bump and +1 for this, I'm in the process of making a request for another mod and one of the things I was going to request is grouping their items together.
I can't hide the items since the items are obtainable and logically should be in the creative tab that's dedicated for them.
There needs to either be an option to hide specific items, or to hide all items with a tag and display that tag as one item, via a config setting.


Fix textContent handling in xen-template

Ok, sorry, this is my fault. This bug was introduced by a hack, and unfortunately, your fix promotes the hack.
Specifically, bindings to textContent should go into textContent property, which is available on text nodes and therefore doesn't require any tree walking.
I had done a quick modification to set that content instead to innerHTML property (which can contain formatting tags) because I wanted to emit formatted text for the view descriptions.
However, in general, binding to innerHTML is an anti-pattern because it opens up avenues for XSS attacks. My intent is/was to replace this hack with a syntax that requires one to specifically request an unsafe binding (probably some kind of magic property name, e.g. div unsafe-html="{{someHtml}}"></div>).

Yes, I figured that something must be wrong with the current implementation (and with my fix too, of course:)))
I don't want to disrupt your vacation too much, so maybe it's ok to add a TODO for fixing this hack and submitting as is for now (until you get back and we fix it properly), so that the demo worked properly again (currently if I add a non-last product from Chooser, the text in the Chooser doesn't change - i emailed you about it yesterday)

Added the todo, merging now.


Update Array.concat type signature to fix #6594

I wasn't sure whether I should commit the LKG changes with the source lib changes; there was another change that hasn't propagated to LKG yet (removal of WeakMap/WeakSet.clear) but I didn't commit it.
This should fix #6594.

Hi @LPGhatguy, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Can you undo the changes to lib?

Yeah; does that mean that the updates to lib are done all at once?

This new diff no longer has the generic line; the following works in the playground:
interface Array<T> {
    myConcat(...items: (T | T[])[]): T[];
}

var x = [1,2,3].myConcat(23, [23]);
console.log(x);

While this does not, which is correct:
interface Array<T> {
    myConcat(...items: (T | T[])[]): T[];
}

var x = [1,2,3].myConcat([[23]]);
console.log(x);

Sounds good to me. @ahejlsberg, can you confirm that it's in line with what you were thinking?

:+1:

An interesting consequence of this change is the interplay with literal type freshness. Previously, the following was valid [{a: ''}].concat([{a: '', b: ''}]), but after the change it is not, because Object literal may only specify known properties. The old types implicitly allow for subtypes because of the type parameter U.


[#46] Use Angular 1.3 one time bindings where appropriate

Hi @soygul, it looks like we can use one time bindings in most cases.

Nice work! Works nicely and the page instantly feels snappier as new posts/comments on large pages don't trigger rebinding on one-time bound fields. Thanks for the contribution again.
Merging.

Closes #46


[Configs] TOML Configs for application-authentication.xml

Need the toml config for the sessionDataKey element in theapplication-authentication.xml as it is mentioned in [1]
[1] https://is.docs.wso2.com/en/5.9.0/develop/authentication-data-api/

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Wrong image name in k8s-deployment.yaml

In k8s-deployment.yaml the image is still set to image: docker.io/stv0g/withings-sync but should be image: ghcr.io/jaroslawhartman/withings-sync:master.

Check PR: https://github.com/jaroslawhartman/withings-sync/pull/157


Improve Google Login Button Icon Style ✨

Issue Description:
Currently, the login with Google button on our GitHub page displays a Google icon that is not visually appealing and could use some improvement to enhance the overall user experience. As part of this issue, I propose to revamp the style of the Google login button icon.
Currently :

After

Hey @Vaishnavi-Patil2211 Assign me the issue now I am ready with the code it improve a few styling it's now look good when the user hovers over login with Google button


Zigbee Device Support for newer Firtzbox models

I am trying to run my ZIGBEE Devices that i conneted to my 5690 Pro on FritzOS 7.62 trough this Plugin. I am pretty sure to have set the AIN etc. correctly but still get
[FritzPlatform] "NameOfDevice" (smarthome-lightbulb): Can not find light data - "accType" and/or options correct?
For every Device I try to connect. COntrolling them directly on the Firitzbox works perfectly.
I have tested this with lightbulbs with brightness control and and without temperature control, buttons and motion sensors.

I have the same problem. Does anyone already have an idea?

This actually does work for me with Homebridge v1.8.5, UI 4.65.1 and the plugin 6.0.19.
What did the trick for me was not to use the 17 digit AIN as displayed in FritzOS 7.62 (on the 5690 Pro), but the 19 digit UNIT number, as indicated in the AHA manual published by AVM:
"1.2.1 Identifier für Gerät und Unit
Zigbee Identifier Beispiel:
Gerät: Z0017880108AFB58C
Unit: Z0017880108AFB58C0B
Hinweis: der Unit-Identifier des Zigbee-Geräts ist 2 Zeichen länger, insgesamt immer 19 Zeichen"
-> For a zigbee device you need to add "0B" to AIN displayed in the Fritzbox.
This is addressing is also what the Fritzbox actually uses internally, when you look at the support log generated by the Fritzbox. It just does not display it properly. I have already opened a ticket with AVM in this respect.
Moreover, Philips HUE Zigbee lightbulbs should be registered in the homebridge plugin as "Grouped Device" "Switch & Lightbulb".

@Stationary-1  thanks for the input on this! I just tried an it did not work. Adding "0B" to my AIN Numbers i get  "Leselampe (smarthome-lightbulb): Can not find device with AIN: xxxxx0B". 5690Pro 8.0.1, Hb 1.8.5, Plugin 6.0.19. Where did you get your Unit Numebers from in the Log?

Good that it works for you now and that you found the log file and the correct number.
Interesting though that my 5690 precisely adds 0B as indicated in the AHA api manual, while yours adds 01.
However, in any case, zigbee devices need the 19-digit number found in the FritzBox support data and not the 17-digit number openly show on the smarthome information pages of the FritzBox.
Good also, that you could confirm the principle.


streamMixer.replaceStreams is not a function

please look into this.. either append stream or replace stream, both are not working
Let me know when it is going to be fix ? or should i switch to some other mixing plugin ?

Same question :/


Themes: admin

Allow to manage the themes in the admin:

List: Name, description, screenshot.
Enable/Disable.
Select default one for site and admin.

duplicate #469


Cote Just Doesn't Work

I try cote for the first time. I already run the time-service.js and client.js also with the monitoring tool. But nothing happened. Do i miss something?

@iwanjunaid "just doesn't work" is a bit too broad don't you think?
Can you share your code so we can see what you're doing?
see https://github.com/dashersw/cote-workshop for a sample work. Hope this helps

sorry for the missing details. Here is the code:
time-service.js
const cote = require('cote');
const timeService = new cote.Responder({name: 'Time Service'});

timeService.on('time', (req, cb) => {
  cb(new Date());
});

client.js
const cote = require('cote');
const client = new cote.Requester({name: 'Client'});

client.send({type: 'time'}, (time) => {
  console.log(time);
});

hi @iwanjunaid ,
The sample code above works. Just make sure you run the time-service.js first before running the client.js so by that time, the timeservice would be available
or better yet, replace your client.js code with
const cote = require('cote');
const client = new cote.Requester({name: 'Client'});

setInterval(()=>{
   client.send({type: 'time'}, (time) => {
  console.log(time);
})
}, 1000)

In fact, you don't even need to care about the order of execution. The Requesters queue queries until a Responder is active — so you can run the client first and then the service, it will work.
@iwanjunaid this code works. could you tell us a bit more about your environment?

@dashersw Ubuntu 16.04, node v6.10.1 and cote 0.15.1.

Here is what i got after run node time-service.js
Hello! I'm Time Service#b53a3d5d-91d8-417a-9d12-189ccdf70a97 on 8000
========================

and here is the ouput for client.js
Hello! I'm Client#1dbb4524-39bc-4696-b0b2-588826db86dc
========================

Are you running in the cloud, on your local machine or a virtual machine? Are you using Docker, multiple machines, etc?

@dashersw no, it is just a local machine on my laptop.

Is there a way to run cote verbosely ?

Looks like IP broadcast doesn’t work on your machine. You could try setting it up, or you could fall back to multicast, or even redis — see the readme for that.
For debugging, there’s an environment variable DEBUG that you can use, setting it to * will give everything.

I try explicitly set the broadcast IP address and now it works! @dashersw thanks a million

@dashersw If IP broadcast doesn't work on my machine (with macOS Mojave), how to make it work?

@arefaslani you can try the redis fallback.

I have Mac Mojave and everything works. Can you show code example?
On Mon, Dec 3, 2018, 12:56 AM Aref Aslani<EMAIL_ADDRESS>wrote:

@dashersw https://github.com/dashersw If IP broadcast doesn't work on
my machine (with macOS Mojave), how to make it work?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dashersw/cote/issues/56#issuecomment-443597415, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJl-ohY3hX28CMfDJuYmWHoz3rbgKM4Xks5u1L0EgaJpZM4OZej0
.

@matejthetree  This is the responder:
// server.js
const cote = require('cote');

const responder = new cote.Responder({ name: 'currency conversion responder' });

const rates = { usd_eur: 0.91, eur_usd: 1.10 };

responder.on("convert", req => req.amount * rates[`${req.from}_${req.to}`]);

and this is the requester:
// client.js
const cote = require('cote');

const requester = new cote.Requester({ name: 'currency conversion requester' });

const request = { type: 'convert', from: 'usd', to: 'eur' };

setInterval(
  async () => {
    const amount = Math.ceil(Math.random() * 100);
    const res = await requester.send({ ...request, amount });
    console.log(`result: ${res}`);
  }, 2000
)

When I run both client and server, services can't find each other by default:

But when I use Redis fallback they will find each other but nothing happens:

After using Redis fallback once, although without Redis, they will find each other sometimes but still nothing happens:

And in the end, when I return a Promise in the responder, everything works and I don't know why!
const cote = require('cote');

const responder = new cote.Responder({ name: 'currency conversion responder' });

const rates = { usd_eur: 0.91, eur_usd: 1.10 };

responder.on(
  "convert",
  req =>
    new Promise(
      (resolve, reject) => resolve(req.amount * rates[`${req.from}_${req.to}`])
    )
);

I'm totally confused!

you are right, actually you found the issue yourself. you can't return simple values in cote, they have to be promises.
responder.on("convert", req => req.amount * rates[`${req.from}_${req.to}`]);

will not work, it needs to be
responder.on("convert", req => Promise.resolve(req.amount * rates[`${req.from}_${req.to}`]));

@dashersw and @matejthetree thank you for quick response and sorry for late reply! Yesterday I was all day to what goes wrong. I've created a simple problem that looks like the original one. Suppose we have three services:

age responder: gets year of birth as integer and calculates the age
greeter: gets the age from age responder and listens to greet event to return a greeting message
greeter client: sends a name to the greeter service to show the greeting message

// age responder service
import { Responder } from "cote";

const ageResponder = new Responder({ name: "age responder" });

ageResponder.on("calculate age", req =>
  Promise.resolve(new Date().getFullYear() - req.yearOfBirth)
);

// greeter service
import { Requester, Responder } from "cote";

const ageRequester = new Requester({ name: "age requester" });
const responder = new Responder({ name: "greeter" });

(async () => {
  const age = await ageRequester.send({
    type: "calculate age",
    yearOfBirth: 1989
  });

  responder.on("greet", req =>
    Promise.resolve(`Hello ${req.name}! Your age is ${age} years.`)
  );
})();

// greeter client service
import { Requester } from "cote";

const requester = new Requester({ name: "greet requester" });

(async () => {
  const delay = ms => new Promise(resolve => setTimeout(resolve, ms));
  do {
    const res = await requester.send({ type: "greet", name: "Aref" });
    console.log(res);
    await delay(2000);
  } while (true);
})();

then I run all three services, each with a command like COTE_DISCOVERY_REDIS=true npx babel-node service-file-name.js and then services find each other but they didn't log anything! What is the problem here? How can I create a service that is at the same time a requester and a responder?

you can read more about this here: https://github.com/dashersw/cote#keys
basically, if you don't have keys for your requesters / responders, all your responders should be able to respond to the same messages. you can't have greet and calculate age messages in separate responders. if that would be the case, you should segregate these services.

Note: By default, every Requester will connect to every Responder it discovers, regardless of the request type. This means, every Responder should respond to the exact same set of requests, because Requesters will load-balance requests between all connected Responders regardless of their capabilities, i.e, whether or not they can handle a given request.

If you have multiple Responders with varying response handlers, you will experience lost requests. In cote, this separation between responsibilities is called segmentation, or partitioning. If you wish to segment your requests in groups, you can use keys. Check out keys for a detailed guide on how and when to use segmentation.

@dashersw Thank you! I'll notify you about the result.

I try explicitly set the broadcast IP address and now it works! @dashersw thanks a million

hey,
can you please share the code?


[ssr] Document restrictions on SSR compatible components

Investigate and document all of the current restrictions that determine whether a component can be pre-rendered with @lit-labs/ssr, including which lifecycle methods will be invoked, and what can and can't be done in each of those lifecycle methods.
See also https://github.com/lit/lit/issues/2351 and https://github.com/lit/lit/issues/2433

Closed by https://github.com/lit/lit.dev/pull/880


Cant add new block breaking/placing without the plugin losing the set

Sponge Version:  1.12.2-2611-7.1.0-BETA-2990
Forge Version:  1.12.2 - <IP_ADDRESS>18
Total Economy Version:  1.8.0
Description of issue
I added some wood and some saplings to the jobsets.conf to lumberjack and farmer after i have done that the plugin just dont know one set every set is mission i checken the {} but for me it look like everything is in good shape.
Console errors
[Server thread/WARN] [totaleconomy]: Job farmer has the nonexistent set "crops"
example happens with all other jobs as well.
Steps to reproduce
When i just add the normal jobsets.conf back and dont use my own it works fine but when i use my one with added blocks for the jobs it just say to every job! Even if i didnt add one thing to a set that error shows up for me. So i think i just use a mod that is not supported or i dont know
Related Configuration Files
Create a Gist (https://gist.github.com/) for each configuration file related to this issue
https://gist.github.com/mrmauwurf/64fde077442a30116ac65303dc9bd0a0
jobsets.txt

I would say there's an error with your configuration. Please check and include your server logs in order to see what the issue is.

The file seems to be quite large, so I recommend removing everything from it and then one by one add them back until the error shows up again. This way we can narrow it down in order to easily determine the problematic set.

@mrmauwurf Have you been able to try out what I said above? Or have you figured the issue out already? Thanks.

I figured already its pams harvestry saplings without them all works and its seems that the saplings arent a normal place event so cant be used in this plugin.

That's actually interessting... I would say your config would not be broken by an item with this behavior.
Can you investigate further?

@mrmauwurf Were you able to investigate this issue anymore? If so did you get it figured out and can I close this issue now? Thanks.

At this point I would say that this issues is stale.


fix intro logotype on tablet & mobile

https://github.com/codeigniter4projects/website/issues/162
Tablet

Mobile

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
245

Relevant Lines:
323

💛  - Coveralls

@lonnieezell


export parallel LATA to sequential vtk

Hello,
I performed a CFD computation of more than 320 millions nodes on 2304 CPUs. I would like to export lata files written in parallel to a single VTK file (as it is already the case for a sequential computation).
Is it possible with Visit?
Thank you in advance.
Edouard Butaye

Hmmm...the conditions of parallel and single VTK file are likely in conflict at multiple levels.
Is your goal merely to have just a single file with all the data? Or, do you also want that single file to represent a coherent single mesh or is it ok for it to be a bunch of different meshes that all just kinda sorta meet at their exterior nodes to form an aggregate larger mesh? Although VTK format may support the latter (I am not 100% sure if it does), our current VTK exporter will not do that. In any event, even if VTK does support a bunch of individual mesh pieces in one file, the next issue you have is writing all those pieces to the file. VTK is really a serialization format. So, it does not lend itself well to writing multiple pieces of a single file concurrently from different processors. You almost certainly would have to serialize that step to satisfy VTK format/API. Finally, even if you could write the VTK concurrently from multiple processors, you next need a file system that actually supports that too (e.g. Lustre or Spectrum Scale)?
If your goal is really to merge all the pieces into a single, coherent mesh, thats even more problematic given what you have described as the scale of the input (320M nodes across 2304 MPI ranks). You could use VisIt's Merge operator but you will likely run out of memory because it will attempt to build up the final result in memory before it ever attempts to write anything to disk.


Nested schemas with dependency fails

Expected behavior
When using nested schemas, I'd expect parent schema to pass down the option configuration down to the nested schemas so that we can use the option within predicate that are used by the nested schemas.
Here is an example:
begin
  require 'bundler/inline'
rescue LoadError => e
  $stderr.puts 'Bundler version 1.10 or later is required. Please update your Bundler'
  raise e
end

gemfile(true) do
  source 'https://rubygems.org'
  gem 'dry-validation', '~> 0.11'
end

schema = Dry::Validation.Schema do
  configure do
    option :email_check
    option :postal_code_check, -> { ->(input) { input.length == 6 } }

    def email?(value)
      email_check.call(value)
    end

    def postal_code?(value)
      postal_code_check.call(value)
    end
  end

  required(:email).filled(:email?)
  optional(:address).schema do
    optional(:postal_code).filled(:postal_code?)
  end
end

email_check = ->(input) { input.include?('@') && input.end_with?('.com') }
input = {
  email<EMAIL_ADDRESS>  address: {
    postal_code: '123456722'
  }
}
result = schema.with(email_check: email_check).call(input)

Actual behavior
In the case where the parent option has no default value and the nested schema option has a a default value, it actually raises an error dry_valid.rb:24:in postal_code?': undefined method call' for nil:NilClass (NoMethodError).
This happens because here the opt_vals won't be empty
since we pass the parent dependency. Then Hash[opt_keys.zip(opt_vals)] will zip over all the option keys, it will find a value for the parent dependency but none for the nested schema dependency and therefore setting the nested schema dependency to nil.

This type of functionality is being removed in 1.0.0. You'll be able to leverage the new rule API to achieve the same thing and a simpler way.


Preview nodes

This is a simple, non-optimized way to preview nodes. It works fine for the examples, at least.
Since it's just using load() and creating and destroying the scene whenever you toggle it, it's going to perform worse when the scenes are very intricate. For now, for me, it's fancy enough.
Key points are that the zone's scripts (saying "zone01 ready") only run in-game, as they aren't tools, and saving the scenes with previews enabled does not include the preview nodes, just the flag used to set it in editor. So when you open the game, it's behaving exactly as before.

Merged the change, thank you. I just removed on_ready.gd, I was good to see it is working but not useful for users, I hope it is ok.


Incorrect AST text for Change Modifier pattern?

The content of sourceBeforeFix and sourceAfterFix for CHANGE_MODIFIER pattern seems to be incorrect:
{
    "bugType": "CHANGE_MODIFIER",
    "fixCommitSHA1": "de55ca810b70f8a2dd144d409cb2491dceb16286",
    "fixCommitParentSHA1": "5b7edd00f3941e1fa5ce5bc4dae788d2fab1042d",
    "bugFilePath": "core/server/worker/src/main/java/alluxio/SessionInfo.java",
    "fixPatch": "diff --git a/core/server/worker/src/main/java/alluxio/SessionInfo.java b/core/server/worker/src/main/java/alluxio/SessionInfo.java\nindex 51a2fa5..11432aa 100644\n--- a/core/server/worker/src/main/java/alluxio/SessionInfo.java\n+++ b/core/server/worker/src/main/java/alluxio/SessionInfo.java\n@@ -24,7 +24,7 @@\n   private final long mSessionId;\n \n   private long mLastHeartbeatMs;\n-  private int mSessionTimeoutMs;\n+  private final int mSessionTimeoutMs;\n \n   /**\n    * Creates a new instance of {@link SessionInfo}.\n",
    "projectName": "Alluxio.alluxio",
    "bugLineNum": 27,
    "bugNodeStartChar": 829,
    "bugNodeLength": 30,
    "fixLineNum": 27,
    "fixNodeStartChar": 829,
    "fixNodeLength": 36,
    "sourceBeforeFix": "2",
    "sourceAfterFix": "18"
},
{
    "bugType": "CHANGE_MODIFIER",
    "fixCommitSHA1": "9d46108b66684d82750a5ad01460ab5bc1c16720",
    "fixCommitParentSHA1": "096ec2aa953065fca5141d415d74eaf00e5aa637",
    "bugFilePath": "components/camel-mock/src/main/java/org/apache/camel/component/mock/AssertionTask.java",
    "fixPatch": "diff --git a/components/camel-mock/src/main/java/org/apache/camel/component/mock/AssertionTask.java b/components/camel-mock/src/main/java/org/apache/camel/component/mock/AssertionTask.java\nindex 347ba0d..e5022b6 100644\n--- a/components/camel-mock/src/main/java/org/apache/camel/component/mock/AssertionTask.java\n+++ b/components/camel-mock/src/main/java/org/apache/camel/component/mock/AssertionTask.java\n@@ -26,6 +26,6 @@\n      *\n      * @param index the n\u0027th received message\n      */\n-    public void assertOnIndex(int index);\n+    void assertOnIndex(int index);\n \n }\n",
    "projectName": "apache.camel",
    "bugLineNum": 24,
    "bugNodeStartChar": 1015,
    "bugNodeLength": 150,
    "fixLineNum": 24,
    "fixNodeStartChar": 1015,
    "fixNodeLength": 143,
    "sourceBeforeFix": "1",
    "sourceAfterFix": "0"
}

Ok, I found out that it is the same bug as the one you've mentioned in the readme for Missing and Delete Throws Exception.


cliccl/load.go: update --as-of to display backup data at arbitrary timestamp

PR: https://github.com/cockroachdb/cockroach/pull/63181
From release notes:

Previously, --as-of of load show data had the restriction that users could only inspect data at an exact backup timestamp. The flag has improved to work with backups with revision history so that users can inspect data at an arbitrary timestamp. [#63181][#63181]

This issue is related to #10936 and docs will be covered with the PR linked to that issue. Closing this in favor of that


Add edge cases to initialization function checks

Context:
Many templates require a special shape of input parameters when run with 1 wire. For zero wires, all init functions should return an empty array.
So far, the tests did not consistently check these edge cases.
Description of the Change:
Rewrite test_init.py to test edge cases. For this the main fixture was rewritten to explicitly list all inputs.
The fix exposed 2 issues in the init functions which were fixed.
Benefits:
Be sure that template init functions work for edge cases.
Possible Drawbacks:
The fixture in the test is getting terribly long, but this will be addressed by changes in the template format soon, see issues #574 and #575.
Related GitHub Issues: #561

Thanks for review @antalszava .
As mentioned, this test file will disappear within the next few months when we introduce a better strategy for the init functions. The way it is now is a disgrace indeed.
The PR is more of a "hotfix".


Add shellsort

It would be better if you commit only the changes to your code and tests, but not the changes to your .idea files.


Gateway aka Reverse Proxy example works for http protocol, but not for https

Appreciate a hint/reference in this regard, if already available.  I can use apache, nginx, but I try to avoid them and use as much Rust code as possible.

This guide shows adding TLS (https).


BAU repair deregistration test

Test method DeregistrationEndpoint_Success was failing with a 401 (unauthorised) response.
The call to the deregistration endpoint in the test was providing:

user token
device id

In fact the following are required:

push token
device id

With the change, it succeed with a 200 response.

Force-merging this.


VPC Gateway Endpoint for S3

enhancement of #42
Current limitation:

VPC gateway endpoint needs to specify the service (S3, DynamoDB...)
VPC gateway endpoint needs a route table amendment to work

While you can have multimple VPC gateway endpoints, you can only have one route table amendment. That means, you need to pick which service is available via routing to you - the other service will remain unreachable.
We decided to implement S3, as this is currently needed the most.

Hi @oliver1980

Would it make sense to put route table entries with all the others in "vpc_route_tables.tf" ?
If create vpc endpoint is not set to true, the vpc endpoint route table association resources will currently still attempted to be created as no count is set + "aws_vpc_endpoint.s3[0].id" would not be accessible, e.g.:

resource "aws_vpc_endpoint_route_table_association" "s3_public_rt" {
  route_table_id  = aws_route_table.rt_public.id
  vpc_endpoint_id = aws_vpc_endpoint.s3[0].id
}

Thanks for updating the readme.md. Could you also update the changelog.md

Thanks!

@Geartrixy , all done as suggested!


Run rush update on renovate PRs

Related to https://github.com/cashapp/misk-web/pull/1849
Renovate docs: https://docs.renovatebot.com/configuration-options/#postupgradetasks
This PR attempts to fix our renovate configuration to run rush update when making dependency changes. This will prevent cases such as the above where the lock file wasn't updated by renovate, requiring another PR.

Not so sure if this will work, but going to give it a shot :shrug:. Worst case I'll revert this one


Update README.md files in EDP repositories

It's been a long time since README.md files for most of our EDP repositories were updated for the last time. We need to make them up-to-date again.

The README.md files have been updated for the following operators:

edp-keycloak-operator
edp-component-operator
edp-headlamp
edp-tekton
edp-cd-pipeline-operator
edp-nexus-operator
edp-sonar-operator
edp-gerrit-operator


Getting started running your first simulation doesn't tell that netCDF4 must be installed

netCDF4 is not automatically installed.
If user blindly follows the getting started tutorial, they will stumble upon an error when running
Env = Environment(
    railLength=5.2,
    latitude=32.990254,
    longitude=-106.974998,
    elevation=1400,
    date=(2020, 3, 4, 12) # Tomorrow's date in year, month, day, hour UTC format
)

Env.setAtmosphericModel(type='Forecast', file='GFS')

which results in the following error:
[NameError: name 'netCDF4' is not defined]()

There should be a reminder in the tutorial telling the user to install the optional package

Thanks for bringing this to our attention @skrobchik. This was brought to our attention recently and as you mentioned, the main problem is that netCDF4 is an optional package.
We brainstormed several solutions:

Make the note on our docs regarding netCDF4 more visible, by putting it in a big red box. Also add it to the installation page, besides the requirements page where it sits now. This is quite easy to do.
Instead of raising a bad error, clearly advise users without netCDF4 how to install it when rocketpy needs it and the user does not have it.
Add netCDF4 as a requirement. This makes sure that it is installed when rocketpy is installed. Should solve any hiccups for most users, however, in a few cases, installing RocketPy will not be possible anymore without changing the source code.
Get rid of netCDF4 and move to xarray (perhaps even herbie-data). This can be a great option but requires significant work.

And you just mentioned a fifth option, which is to also remind users to install it in our example. Anyways, I agree that having a package be an optional requirement while it is used in the first example that the user meets is not quite a good experience.
@Gui-FernandesBR, shall we make this issue a priority to solve it quickly?

I think checking for availability at runtime and instructing the user to install the package instead of throwing a bad error would be a good first solution. At least for the way I encountered it. Something like:
This feature of rocketpy requieres "netCDF4" which was not found. You can install it with: pip install netCDF4

Tks for openig this issue @skrobchik . I believe raising a warning as you suggest is better option here, would you like to create the pull request implementing that? If you don't feel confortable doing that, I can ask someone from our team to help you.
Honestly would be an honor for us if you try it, be welcome
Again tks for sharing it with us.
@giovaniceotto do you think it's still importnat adding a comment on "getting started"  to remind using netCDF4 before using environment models?

#127

Tks for openig this issue @skrobchik . I believe raising a warning as you suggest is better option here, would you like to create the pull request implementing that? If you don't feel confortable doing that, I can ask someone from our team to help you.
Honestly would be an honor for us if you try it, be welcome
Again tks for sharing it with us.
@giovaniceotto do you think it's still importnat adding a comment on "getting started"  to remind using netCDF4 before using environment models?

With the new implementation, I don't think it would be necessary.


add WriteBar app

https://writebar.js.org
https://github.com/alexander-shvets/writebar

this is really nice! cheers! 👍