text:
DVAS-1236: Fix guess_java_version function for Java 11.

Add unit tests to cover all of the strange legacy edge cases.
Refactor a little to make the function more unit testable.

@markbastiaans - would you mind taking a look here too, please? Thank you in advance!

Release Notes:
This release contains a bug fix in the m2ee library.
Bug fix addresses the java version detection logic mainly to account for the JDK version-string scheme changes introduced as per JEP-223

repo: mendix/cf-mendix-buildpack


text:
Document change of User Role for Admin(MxAdmin) account

Changes of role are only applied when the admin account password is changed.

Approved over Slack.

source: gharchive/pull-request

repo: mendix/docs

license_type: permissive

license_source: github-api


text:
Document behavior on DDL commands

See https://mendix.slack.com/archives/C5SASDZBN/p1630679438064000
Hopefully this will improved, but for now we should document the way it currently works.

I see I only did the Mendix 9 document. The Mendix 8 and Mendix 7 docs should be updated as well, I think?

We normally only do the current version but, since it is you asking, I'll do 7 and 8 as well.

authors: MarkvanMents feddovanede


text:
NC gradient background widget

The widget is not released yet.

Hey @ConnorLand , the widget is released and we are ready to proceed with this PR


text:
Added SynchronizationCleanupInterval setting

@ConnorLand

Please also add this to mx9


text:
[WC-2278]: Add auto-label feature to combobox-web widget

Pull request type
New feature (non-breaking change which adds functionality)

Description

changed target branch to combobox_v2 for now.

authors: gjulivan samuelreichert

repo: mendix/web-widgets


text:
delete all landmarks

Would be nice to be able to delete all landmarks to start afresh

Technically possible from v1.5.0 with the key combination a -> d or shift click on landmarks sidebar + d.

no this is fine, although I do wonder if maybe we should add a delete button to the UI for discoverability? It's behavior would be the same as 'd', as in delete whatever is selected. Thoughts?

Could it be part of the group editing overlay we were talking about ? Like a trash icon in a corner.

source: gharchive/issue

authors: jabooth lirsacc

license_source: bigquery


text:
AttackSpeed Stat type

I suppose since Attack Speed/HealAndShieldPower are measured in Percentages in LoL, it also has to be in a percent section rather than flat. It's a little counter intuitive to look for the Attack Speed stats in the "flat" section even though it's stacked additively (Lifesteal is also additive but is "percent" stat). In addition, here when you parse passives, you put them into "percent". But raw stats are put in flat: here and here

At this point we are not considering changes to the format of the JSON because any format changes will result in downstream apps breaking.

authors: PushaBe jjmaldonis

repo: meraki-analytics/lolstaticdata

license: MIT


text:
Fix tests refactor

Fix #583
Cambios introducidos :

Tests corren en el branch de refactor

Revisión

[ ] Todos los textos se encuentran localizables
[ ] No se introducen warnings al proyecto
[ ] Se incluyen cambios de UX ? se verificó que se vean bien tanto en iPhone SE y S6 : NA
[ ] No se agregan logs / prints innecesarios
[ ] No se agregan comentarios basura

Testeo

[ ] Testeado en BETA con emulador
[ ] Testeado en BETA con dispositivo
[ ] Test unitarios OK
[ ] Test funcionales OK
[ ] Documentación actualizada

Codecov Report

:exclamation: No coverage uploaded for pull request base (pmSelection-refactor3.0@4299f66). Click here to learn what that means.

@@                    Coverage Diff                     @@
##             pmSelection-refactor3.0     #584   +/-   ##
==========================================================
  Coverage                           ?   24.23%
==========================================================
  Files                              ?      261
  Lines                              ?    14585
  Branches                           ?        0
==========================================================
  Hits                               ?     3534
  Misses                             ?    11051
  Partials                           ?        0

Impacted Files
Coverage Δ

MercadoPagoSDK/MercadoPagoSDK/Item.swift
44.11% <100%> (ø)

...oPagoSDKTests/PaymentVaultViewControllerTest.swift
98.02% <100%> (ø)

...K/MercadoPagoSDKTests/CheckoutPreferenceTest.swift
100% <100%> (ø)

...rcadoPagoSDKTests/CheckoutViewControllerTest.swift
100% <100%> (ø)

Continue to review full report at Codecov.

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

authors: codecov-io edentorres

repo: mercadopago/px-ios

license: mit


text:
Attach data to hg_bulk_t and hg_addr_t

Is your feature request related to a problem? Please describe.
In Margo we use HG_Set/Get_data to attach data to hg_handle_t handles (typically we attach the margo_instance_id that was used to create the handle, along with some other information). A similar mechanism for hg_bulk_t and hg_addr_t would be really useful.
Describe the solution you'd like
hg_return_t HG_Bulk_set_data(hg_bulk_t handle, void *data, void (*free_callback)(void *));
void * HG_Bulk_get_data(hg_bulk_t handle);

hg_return_t HG_Addr_set_data(hg_addr_t handle, void *data, void (*free_callback)(void *));
void * HG_Addr_get_data(hg_addr_t handle);

Yes I think I agree and that would prevent you for example from re-implementing another hash table or something similar to retrieve whatever you need to associate to the addr / bulk.

authors: mdorier soumagne

repo: mercury-hpc/mercury


text:
Indicator Plan: Goal indicators disappear when indicator plan is grouped by results chain.

From Slack, Goal indicators disappear when indicator plan is grouped by Results chain.

I am consistently seeing indicators for the top level, regardless of how I group them in the indicator plan.

authors: jennyhavah sanjuroj

repo: mercycorps/TolaActivity


text:
Problems accessing date picker in Reporting period modal and Results pop-up

This ticket was peeled away from #258
Reporting period pop-up
My ability to open the date picker is inconsistent. The first time I click into a text box, it's usually fine. But as I click back and forth between the Start date and End date fields, or switch between clicking on the calendar icon and clicking in the date field, the date picker does not consistently open. And sometimes it gets detached, like so:

Results pop-up
In general, the date picker seems to open a bit more consistently. But this sometimes happens.

per our conversation just now I removed the calendar icons. Should be visible on demo in the next deployment

I am still having problems with both date pickers, and can reproduce on both machines I use at work. However, I seem to be the ONLY person experiencing this, so I'm going to move to the Backlog for now to see if anyone else experiences it.

I've now replicated the date picker on a third machine -- my home laptop.

Are you logging into your Google Chrome account on all three machines?
When we have a chance, I'd like you to try to replicate the bug in these conditions on all your machines:

In incognito mode
after logging out of Google Chrome
using Canary without logging into your Google Chrome account,
…and then again with logging in

Home laptop
Incognito

Reporting period modal: FAIL (meaning after I go back and forth between the two date fields a few times, the date picker stops showing up.)
Results "date collected" field: FAIL

Logging out of Google Chrome

Reporting period modal: FAIL
Results "date collected" field: FAIL

Using Canary without logging into Google Chrome
To be continued...
Using Canary after logging into Google Chrome
To be continued...
Work laptop
To be continued...
Work desktop
To be continued...

authors: axoplasm jennyhavah


text:
Dreame Bot D9 Max

Device model
dreame.vacuum.p2259
The unique model of your device, e.g zhimi.fan.za5.
Device name
Dreame Bot D9 Max
The friendly name of the device used by the manufacturer, e.g. Smartmi Standing Fan 3.
Does the device require a MiCloud connection?
Yes
Most devices which were introduced to the market in 2020 and later does not require MiCloud.
Anything special about the device?
Does it already work with the plugin with a limited scope (can be controlled using the auto created switch)?

Will add support in the next update!

Please also add the Dreame D9 Pro. At the moment it can be added, but in HomeKit it is marked as „unsupported Device“ and has no function at all. Thank you!

@phipsey please create a separate issue for that!

The device is now added in version 1.0.6

authors: izumovn merdok phipsey

repo: merdok/homebridge-miot


text:
New Bluesky profile

{
"title": "Darren Robinson",
"bluesky": "darrenjrobinson.com",
"twitter": "darrenjrobinson",
"category": "Security","Azure"
"type": "MVP"
}

Done!

authors: darrenjrobinson merill

repo: merill/bluesky


text:
cannot find type AK... in scope

Added a pull request for version restriction (as mentioned in above comment) and panning functionality in iOS.

authors: mrprabbs siherrmann


text:
Is there a plan for add mini GUI to mesalock-linux ?

hi,
Is there a plan for add mini GUI to mesalock-linux ?
For some reason , or demo purpose for people who first time touch mesalock-linux , a GUI interface will be more acceptable for them .
Do we have a road map ?
thanks.

GUI is not on the plan right now. Since GUI on Linux has a huge C/C++ stack, making them memory safe is a big project. We are focusing on docker image, (high-end) IoT system in the short term. When all building blocks for GUI are ready, we can push forward to the GUI thing.
For demonstration purpose, we have a web service written in Rust right now. Later, we may consider adding more samples in various scenarios for demonstration. If you have any ideas on the demo, feel free to propose here. Thanks.

Another direction on these non-memory-safe packages is that we can constrain the processes's capabilities (e.g., using AppArmor). Therefore, although there are attack surfaces of the non-memory-safe processes, we can minimize the the consequences. Of course, all efforts here aim to achieve the rules-of-thumb for hybrid memory-safe architecture mentioned in the README.
For the GUI thing, firstly, we need to evaluation how large the non-memory-safe code base will be involved and how to constraint these code.

Great explanation!

authors: cloudtrends mssun

repo: mesalock-linux/mesalock-distro


text:
[Applications] Support kustomize applications as Meshery Applications

Current Behavior
A Meshery Application can be generated using Meshery's Designer features or can be imported (and further customized) as a Helm Chart, Docker Compose, or Kubernetes Manifest - each of these are importable application types.
Desired Behavior
Ideally, Kustomize applications are also supported application import type.
Implementation

Acceptance Tests

Mockups

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Marking with the v0.8.0 milestone.

repo: meshery/meshery


text:
[CI] Enhance Edge Release Channel with Versioning

Current Behavior
Of the two Meshery release channels the only the stable channel has version numbers. The edge release channel only has latest.
Desired Behavior
Support version of the edge releases, just like versioning of stable releases.
Implementation

Add version to seed version by updating https://github.com/meshery/meshery/blob/master/.github/workflows/build-and-release-edge.yml#L29 edge release workflow and replace with GIT_VERSION=${GITHUB_REF/refs/tags//}.
Add version to docker tags. This change won’t affect docker tagging.

Acceptance Tests

mesheryctl system version functions as expected while running an edge release.
mesheryctl system login using the meshery provider works.
mesheryctl system channel able to set / pin to a version number for an edge release.
Meshery UI: Ability to use Meshery as the remote provider when running edge release.

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Hi, So whenever a new tag is pushed we need a versioning of edge release is that like that as currently whenever new changes are pushed to master edge release is done

// @theBeginner86


text:
Create staging playground deploy workflow and other updates

Notes for Reviewers
This PR fixes #11042

Create workflow for updating the meshery helm release in the staging playground. Added this to the edge release workflow
Updated the playground reset job to use secrets.METAL_SERVER1
Use pinned version of actions/checkout@v4 in the edge release workflow

Signed commits

[X] Yes, I signed my commits.

Updated to use mesheryctl @leecalcote @MUzairS15

Good deal. I think that this command is all that we need. We'll find out shortly. 😉


text:
Fixed nil error causing panic

Signed-off-by: ashish ashishjaitiwari15112000@gmail.com
Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #4688 (a928740) into master (ab49fb3) will decrease coverage by 6.97%.
The diff coverage is n/a.

:exclamation: Current head a928740 differs from pull request most recent head 2c88d09. Consider uploading reports for the commit 2c88d09 to get more accurate results

@@            Coverage Diff             @@
##           master    #4688      +/-   ##
==========================================
- Coverage   32.83%   25.86%   -6.98%
==========================================
  Files          61       61
  Lines        5107     5107
==========================================
- Hits         1677     1321     -356
- Misses       2991     3457     +466
+ Partials      439      329     -110

Flag
Coverage Δ

gointegrationtests
?

unittests
25.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/start.go
1.11% <0.00%> (-58.52%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
2.50% <0.00%> (-47.50%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-47.44%)
:arrow_down:

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-34.74%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
1.78% <0.00%> (-23.22%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.39% <0.00%> (-22.38%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
3.29% <0.00%> (-20.88%)
:arrow_down:

Continue to review full report at Codecov.

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

@Revolyssup is this issue affecting v0.6.0-rc-1 or was this issue introduced after that release?

authors: Revolyssup codecov-commenter leecalcote


text:
[Docs] Add Release Channel Selector to Compatibility Matrix

Description
This PR fixes #5144
Notes for Reviewers

Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit bace871aca1bcaed7a120a16b1499b9a26c811e6 at: https://622064b2dcc5de6e3336e915--meshery-docs-preview.netlify.app

🚀 Preview for commit 551c023a81919801993cbc94ee0f5d0e5d7b8320 at: https://6220684ed61264702fccfbda--meshery-docs-preview.netlify.app

🚀 Preview for commit a6cb0962b2cd7e662a8311be7ed372ad922af32d at: https://6220bd9702673ae4a7b093b3--meshery-docs-preview.netlify.app

Dang @warunicorn19 . Shouldn't have added you as a reviewer 😂

Oops, sorry @Nikhil-Ladha 🥲🥲😂😂

We have the console logs on the other pages too, so I thought since its a copy paste we can just move forward with it 😅😅

We have the console logs on the other pages too, so I thought since its a copy paste we can just move forward with it sweat_smilesweat_smile

Ahh....no worries.


text:
Added some transition effects to buttons on the home page

This is a follow up to the issue raised regarding lack of transition effects on buttons.
Notes for Reviewers
This PR fixes #73
Signed commits

[X] Yes, I signed my commits.

@leecalcote can you please have a look at his whenever possible? Thanks.

Hi @sidtohan , good job on the changes. Think of this as a add on to your changes, so I was thinking about adding a little box shadow on hover for the buttons, kinda like a glow effect as the current effects are not that prominent, do let me know what you think about that. If you have any other suggestion in mind please feel free to share it too, thanks

@Avi-88 that's a great idea. Other than that i don't think anything else is needed, it's best if the effects are subtle.
I'll get to work on the box shadows. Thanks.

@Avi-88 I have done the required changes. If there are any further improvements that can be made, please kindly tell.
Thanks.

If it's all good, can it be merged? There's another issue I would like to move on to.
Thanks.
@leecalcote @Avi-88

Don't worry about it @sidtohan , your PR will get merged once the final approving review is done. It might take some time as there are many other PR's to go through as well. Just so you know , if any of your PR goes unnoticed for too long you can just ping it in slack or bring it up in the weekly dev call, thanks

I see. @Avi-88 thanks a lot for your guidance.

@sidtohan Good stuff here, just a minor to look the bottom border is getting cut here. Will you make a fix for this?

Alright sure I'll look into this.

@Chadha93 I have fixed the issue. Kindly take a look whenever possible.
Thanks.

repo: meshery/play


text:
Vague error when file not in git when building package

I just started using mesonpy and I went through the tutorial and hit a temporary wall that I think could be clarified. When creating a new file but before comiting the file to the git repository, the editable installs worked and the pip install . works. But running pipx run build or python -m build . resulted in
...
../meson.build:3:0: ERROR: Nonexistent build file 'src/meson.build'
...

or
../src/meson.build:10:3: ERROR: File bar.pyx does not exist.

even though the files existed.
If you haven not staged the changes then you get no warning that explains the reason why this is happening.
If you have staged changes, the issue appears earlier in the output with the warning WARNING: Repository has uncommitted changes that will not be included in the dist tarball.
../meson.build:3:0: ERROR: Nonexistent build file 'src/meson.build' also led me down a different rabbit trail that took some time to figure out.
I don't personally think we need to change anything in mesonpy or meson unless catching this is easily done. But I think the https://meson-python.readthedocs.io/en/latest/how-to-guides/config-settings.html wiki page could be reworked into a "Building your package" page that includes a warning about this. I'd be happy to submit a PR with whatever you suggest.

Found it in the docs
https://meson-python.readthedocs.io/en/latest/tutorials/introduction.html#building-the-project

repo: mesonbuild/meson-python


text:
Bug/Feature Request: Cassandra data and commit log on different drives

For high volume Cassandra performance, the commit log and the data should be placed on separate volumes.  There is a very large performance increase doing this in the tests we tried and is directly mentioned in multiple Cassandra performance documents
The biggest performance gain for write is to put commit log in a separate disk drive

commit log uses sequential write and most hard drive will meet the throughput requirement
However, if SSTables share the same drive with commit log
I/O contention between commit log & SSTables may deteriorate commit log writes and SSTable reads

Reference

https://wiki.apache.org/cassandra/CassandraHardware
http://jonathanhui.com/cassandra-performance-tuning-and-monitoring

We identified this issue as a critical item to be solved. Any plan to address this?

authors: fksimon zemmet

repo: mesosphere/dcos-commons


text:
Verify: Restarting Tasks during Deployment with Deps should use correct App Version

#1898 causes AppRepository writes to happen earlier. We have to verify that replacing tasks while upgrading does not start tasks with a new app definition if dependencies are still not restarted.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-3151. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.

authors: kolloch meichstedt

repo: mesosphere/marathon


text:
Removed old python scale tests

since we moved away from them a while ago to the new performance test driver.

I'm sorry @kensipe , I understand there is a lot of sentimental value in them. If you want, you can highjack this PR and merge it in your name - you totally deserve it! 😊


text:
Use eventually instead of shakedown.deployment_wait().

Summary:
The deployment_wait method of Shakedown uses a busy, noisy spinner.
The assert_that(..., eventually(...)) pattern on the other hand gives
more insight into errors.

Close in favour of #6440.


text:
Mux Protocol - ARBITRUM_ONE

Review Info

Description
Info

Subgraph Reviewed
https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/id/QmY8zEbstD3gzDyzYSHRMDFR1TLcqiJqnGNXA64dqdg4my&tab=protocol

Schema Version
1.3.1

Subgraph Version
1.0.0

Methodology Version
1.0.0

Evidence Spreadsheet
https://docs.google.com/spreadsheets/d/1pHi5JYdOGMACoPSzTpwF6eehiN_heDbL/edit?usp=share_link&ouid=104027705798814439445&rtpof=true&sd=true

Metric to Review
Total Pool Count

The total pool count should be reduced to one instead of three pools.
On the official website, only the 'MUXLP' pool is displayed.
Please refer to the 'Protocol' and 'Pool_Overview' sheets for more information.

Notes on Revenue
Only sanity check is performed for the revenue, which are within reasonable range but we are not able to further ascertain they are accurate. The official website does not provide specific data for the Arbitrum network, so it's not possible to compute the implied revenue for Arbitrum.
To be specific, the revenue and fee data shows from Defi Llama and Token Terminal are different, likely calculated their revenue data using their own methodologies. The subgraph's revenue is categorized into three components: supply side, protocol side, and stake side. Token Terminal only displays the supply side and protocol side revenue, while Defi Llama only shows the total revenue.
Please refer to the attached worksheet for more details.

@corerouter QA for MUX!

@ishraq8 This QA might actually be good on the first go around. If you could quick scan the feedback and give it a final ok whenever you get the chance that would be great!

@corerouter QA for MUX!

I will study the QA report and give feedback later. Thanks!

will take a look once courrouter takes a look at initial comments

Thank you very much for the QA report and I highly appreciate it!
On the Total Pool Count, there are two key components in the MUX Protocol: one is MUX Leveraged Trading Protocol, which just likes other Perp protocol and uses MUX own liquidity pool to facilitate trading, while the other is MUX Leveraged Trading Aggregator, which automatically uses other Perp protocol to facilitate trading.
As there are currently two other protocols, GMX and Gains Trade, which MUX routes user for trading, so right now, there are three pools in the subgraph, MUX own pool, GMX and Gain Trade. The subgraph needs to have pools for GMX and Gain Trade in order to track the trading revenue related with these two protocols which MUX routes users for trading.

repo: messari/subgraphs


text:
Warning: Asking to pad to max_length but no maximum length is provided and the model has no predefined maximum length.

System Info
Cuda 12.1
PyTorch 2.3.0
Python 3.11
Thu May 23 15:30:20 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.23.06              Driver Version: 545.23.06    CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA A100-SXM4-80GB          Off | 00000000:0F:00.0 Off |                    0 |
| N/A   37C    P0              61W / 400W |      4MiB / 81920MiB |      0%      Default |
|                                         |                      |             Disabled |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|  No running processes found                                                           |
+---------------------------------------------------------------------------------------+

Information

[ ] The official example scripts
[X] My own modified scripts

🐛 Describe the bug
Thanks for the open source model. I init Llama 3 70B as per the recipe for local inference. However when I do inference I see warning:

Asking to pad to max_length but no maximum length is provided and the model has no predefined maximum length. Default to no padding.
Asking to truncate to max_length but no maximum length is provided and the model has no predefined maximum length. Default to no truncation.

I took max_length=None from the recipe. Also, at HF, at here, they advise to do tokenizer(batch_sentences, padding='max_length', truncation=True) (without max_length but it is None by default). However, the model doesn't provide the max_length. So how to set max_length
My code:
        self._model = AutoModelForCausalLM.from_pretrained(
            llm,
            return_dict=True,
            load_in_8bit=llm_kwargs["load_in_8bit"],
            load_in_4bit=llm_kwargs["load_in_4bit"],
            device_map="auto",
            low_cpu_mem_usage=True,
            attn_implementation="sdpa" if llm_kwargs.get("use_fast_kernels", False) else None,
            torch_dtype=torch.bfloat16
        )
        self._model.eval()

        tokenizer = AutoTokenizer.from_pretrained(self._llm)
        prompt = tokenizer.apply_chat_template(
            prompt, tokenize=False, add_generation_prompt=True
        )
        tokenizer.pad_token = tokenizer.eos_token
        batch = tokenizer(
            prompt,
            padding='max_length',
            truncation=True,
            max_length=None,
            return_tensors="pt"
        )
        batch = {k: v.to("cuda") for k, v in batch.items()}
        outputs = self._model.generate(
            **batch,
            **self._gen_kwargs,
        )
        # Take only response:
        outputs = outputs[0][batch['input_ids'][0].size(0):]
        response = tokenizer.decode(outputs, skip_special_tokens=True)

Error logs
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
> Asking to pad to max_length but no maximum length is provided and the model has no predefined maximum length. Default to no padding.
> Asking to truncate to max_length but no maximum length is provided and the model has no predefined maximum length. Default to no truncation.
> Setting `pad_token_id` to `eos_token_id`:128001 for open-end generation.

Expected behavior
No warning expected.

Hey @artkpv the repo has been updated, can you try with the latest code please?

repo: meta-llama/llama-recipes


text:
SA - Icons

Sender: ritheshkdr@gmail.com
Comment: few icons are not displaying
Open #30 in Usersnap Dashboard

Download original image
Browser: Chrome 72 (Windows 10)
Referer: https://api.amexio.org/api/v5.5/index.html#/navigation/sidenav-page-demo
Screen size: 1600 x 900 Browser size: 2000 x 946
Powered by usersnap.com

This has been resolved.. Closing it.

authors: arafkarsh ketan-gote


text:
Make verbose option for ansible config block more flexible

Fixes documentation showing verbose: True which wasn't actually supported.
Adds support for verbose: True and sets it to vvvv. Necessary for better clarity since we'll accept verbose: False.
Fixes #134

LGTM

authors: abrown-sg cimarron-pistoncloud

repo: metacloud/molecule


text:
Normal Text to md5 hash in python

I would like to contribute a normal text to md5 hash converter in pyhton. PLease assign me this project

I am student of BITS Pilani, india. I would love to work on this. Please assign me this issue.
@DebdattaRay

I would like to work on this issue.Can you please assign this to me.

authors: DebdattaRay protocolog yashshroff07

repo: metafy-social/python-scripts


text:
add OWNERS_ALIASES support

OWNERS_ALIASES groups are needed for fair blunderbuss review requests.

/cc @lentzi90 @kashifest

/approve

authors: dtantsur tuminoid


text:
Support mirroring traffic from pod's localhost

Following Discord:
https://discord.com/channels/933706914808889356/1252971596663095396
mirrord mirroring is interface based, meaning it only mirrors from one interface:

It looks up 8.8.8.8, and takes the interface that the OS picks for resolving as the one it'll mirror from.
If the lookup doesn't work, it tries "eth0"

Possible solutions:

Bind all interfaces - issue is if host acts as of some router, we might see a stream twice. Not sure how we could "ignore it".
Support binding multiple interfaces, let use specify - same problem as above but atleast controlable.
Change mirroring to use iptables - we can use nflog - though above problems can still happen? using nflog will also help us with tcp assembly (I think? or maybe it was worse? can't remember)

Pending user input on Discord

repo: metalbear-co/mirrord


text:
User runs yarn/npm with mirrord, their app does not start

Bug Description
On CLI - new shell opens, on vscode - Nothing happens.
Steps to Reproduce
Did not reproduce for me, but here is what the user reported:

git clone https://github.com/hmcts/civil-citizen-ui && cd civil-citizen-ui
yarn install && yarn webpack
mirrord exec -t .. -- yarn start
A new interactive shell opens, the yarn app does not run.

For vscode:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "program": "${workspaceFolder}/src/main/server.ts"
        },{
            "command": "npm start",
            "name": "Run npm start",
            "request": "launch",
            "type": "node-terminal"
        }
    ]
}

And user only sees this output:
echo 'yarn run start' | DYLD_INSERT_LIBRARIES=/tmp/10779832966104285419-libmirrord_layer.dylib /var/folders/82/bndhr3411j90b382k_dh7kjw0000gn/T/mirrord-bin-ghu3278mz/bin/zsh -is
user@User-Mac civil-citizen-ui % echo 'yarn run start' | DYLD_INSERT_LIBRARIES=/tmp/10779832966104285419-libmirrord_layer.dylib /var/folders/82/bndhr3411j90b382k_dh7kjw0000
gn/T/mirrord-bin-ghu3278mz/bin/zsh -is

This output is valid, I get it too, but for me the app then starts, so I think maybe something in the session start gets stuck or takes very long and so the user is stuck on that phase.
Backtrace
No response
Relevant Logs
No response
Your operating system and version
macOs
Local process
node
Local process version
v21.7.1
Additional Info
https://canary.discord.com/channels/933706914808889356/1280178791469023314

I couldn't manage to reproduce the error, mirrord exec .. yarn -- start works as expected, though there are some problems I did have to change because of my local setup, I don't have a tls redis and the string value from env variable propagated to comparison and "false" is truthy
-- const protocol = config.get('services.draftStore.redis.tls') ? 'rediss://' : 'redis://';
++ const protocol = config.get('services.draftStore.redis.tls') === 'true' ? 'rediss://' : 'redis://';

I have a feeling something in ~/.zshrc or similar is involved here because we are running zsh with mirrord so it's probably related to that and not the underlying nodejs or npm

I also use zsh

User can't reproduce, everything works now.

authors: DmitryDodzin aviramha gmikerlemos t4lz


text:
(ISO 19135) Presentation XML: discrepancy between PDF/Word presentation of Requirement

Encoding:
(document: https://github.com/metanorma/iso-19135/tree/main/sources/iso-19135-2021)
[.requirement]
====
The register owner shall appoint a register manager.
====

[example]
A register owner can serve as the register manager, or appoint another
organization to serve as the register manager.

[.requirement]
====
The register owner shall appoint a control body.
====

[example]
The register owner can serve as the control body, or delegate that role to a
subgroup within an entity or to the register manager.

[.requirement]
====
The register owner shall appoint a register system manager.
====

[.requirement]
====
A register owner shall specify the criteria to qualify as a proposer.
====

[.requirement]
====
A register owner shall specify the register users eligible for access to the
register.
====

Word:

PDF:

Both Word/PDF rendering should be in accordance with the Presentation XML.

ISO xslt updated - styles added for the requirement element:

Closing, this is resolved.

repo: metanorma/metanorma-iso


text:
Update cpyMSpec

We've been sticking to cpyMSpec version 0.3.5 to ensure annotations are generated consistently, as cpyMSpec 0.4.2 gives slightly different results due to using a different algorithm. cpyMSpec 0.4.2 requires half as much time to calculate centroids, which means a significant speed up on annotations that use new database combinations. However, we haven't done any extensive evaluation whether the upgrade is safe yet.
analysis_version==2 already uses cpyMSpec 0.4.2, but it will still be a while before we can make analysis_version==2 the default version. We should check whether it's possible to change the analysis_version==1 behavior to use 0.4.2 as well.
Analysis

[ ] For each of the 18 possible instrument profiles (2 polarities * 9 unique resolving powers (we also snap resolving power to the nearest preset value for better cacheability)), generate the top 4 centroids for each unique formula in HMDB for both versions of cpyMSpec and compare them. If all of them are within 0.01ppm between both versions, awesome, proceed to implementation. If not, raise it for discussion on #metaspace_dev.
Implementation
[ ] Change all dependencies on the cpyMSpec_0_3_5 module to use cpyMSpec instead
[ ] Remove the cpyMSpec_0_3_5 dependency

I checked the calculated masses, and I don't think we should upgrade it for analysis_version==1. Calculated masses change significantly between the two versions due to imbalance in the sampling during centroid mass estimation.
E.g. for a 140k RP TOF instrument, version 0.3.5 will consistently report the first mass at ~0.11ppm lower than the true mass (calculated by just summing element masses and adding/subtracting an electron mass), and version 0.4.2 will consistently give values ~0.14ppm higher. This numerical bias can be reduced by increasing the points_per_fwhm argument when calculating the centroids, however this linearly scales both accuracy and processing time, i.e. doubling this value will take twice as long to calculate and will approximately halve the error. It's undesirable to significantly increase the calculation time, as it is already quite significant for large databases.
I'm closing this issue because v2 aka analysis_version==3 uses the new version and hopefully everyone will eventually migrate to use v2 by default.


text:
transform snapshot uses JSON parser

Description
JSON property can have a null value.
When creating a snapshot in json this caused a null exception when creating a snapshot in json
Related Issue :
#1455
How Has This Been Tested?

edit rule on dataflow
using set rule makes any column to have a null value
make a snapshot

and

create a dataset with JSON file
create a dataflow with the dataset
create a snapshot with them

Both must be successful.
Types of changes

[x] 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 change)

Checklist:

[ ] My code follows the code style of this project. it will be added soon
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document. it will be added soon
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Additional Context

run build
deploy to 4

@ksparknot  http://52.231.153.96:8188/app/v2/management/datapreparation/dataflow/ac96f25f-d75e-4b39-b87f-cd451be4aeff  can you make hive snapshot with this?

http://52.231.153.96:8188/app/v2/management/datapreparation/dataflow/ac96f25f-d75e-4b39-b87f-cd451be4aeff

That is a problem of another issue .
If you are using STAGING_DB type dataset, Connection doesn't work. (it has resolved on master branch)
please test this issue with FILE or DATABASE type dataset

authors: ksparknot paigechoi

repo: metatron-app/metatron-discovery


text:
SideMenuContainer: Uncaught TypeError: Cannot read property 'side' of null

ionSideMenuContainer.created always results in Uncaught TypeError: Cannot read property 'side' of null
When removing next code in meteoric_ionic.js, the problem seems to be solved:
Template.ionSideMenuContainer.created = function () { this.side = this.data.side || 'both'; };
Moreover in the app under meteoric/demo, this piece of code does not exists.

This was fixed over the weekend but I haven't pushed a new version to Atmosphere yet. I'll plan on doing that today, but in the meantime you can symlink the repo into your packages directory if you want.

authors: fbeenaerts nickw

repo: meteoric/meteor-ionic


text:
Feature/add unstable participant api

Related to adpater.RobotUpdateHandle.get_unstable_participant().
Also traj creation adpater.schedule.make_trajectory().

Note: pending fix on bad shutdown after Participant.set_itinerary()

Wrong repo, sorry!


text:
barcoding experiment

Figure S16 (histogram) and figure S17 (Sankey plots)
I added a new property for cells (barcode) but since each lineage has a unique barcode, I didn't really need to use it, but I thought it wouldn't hurt to keep it as a cell's property.
I understand the histogram figures are not very elegant for going into a publication. If we are only showing them to the editors, they may suffice? If we are planning to insert them into the supp figures, please let me know.
I was not sure how to link a go figure to our getSetup. I created those figures in the terminal and saved them. I can manually upload them to the output folder if we want to have them in the repo. But the figure for both drugs is in the thmm channel in Slack.

Thanks, could you please also merge this?

repo: meyer-lab/tHMM


text:
Unable to chain factory.onCreate

In order to clean up my subscriptions in a way that's as clean as possible, I'd like to be able to chain factory.onCreate.
Currently this is impossible to do.
The factory.onCreate will always be the only function that gets called in the stack.

Thanks for the issue!
Chaining onCreate currently doesn’t work as expected and leads to previously added callbacks being replaced.
This is because the factory stores only a single callback instead of an array.
Should be pretty easy to implement. Feel free to send a PR, or I’ll try to get it done when I have some time.

authors: hellowodl mfellner

repo: mfellner/valtio-factory


text:
Compilation error with SuiteSparse

Hello,
I am trying to compile MFEM with the flag MFEM_USE_SUITESPARSE ?= YES.
The SUITESPARSE_DIR variable is set to the right directory. I am using the last SuiteSparse sources (v4.4.5), available at http://faculty.cse.tamu.edu/davis/suitesparse.html
The compilation error is (using make serial) :

In file included from linalg.hpp:33:0,
from solvers.cpp:12:
solvers.hpp:23:21: fatal error: umfpack.h: No such file or directory
#include < umfpack.h >

MFEM is looking for headers in SuiteSparce_DIR/include but there is no such folder in my SuiteSparse directory. The headers for UMFPACK are in SuiteSparse/UMFPACK, the headers for AMD are in SuiteSparce/AMD etc...
One "working" solution I have found is to add many symlinks in my SuiteSparse directory but this is not really clean.
Am I doing something wrong or the current MFEM makefile was designed to work with other or older versions of the SuiteSparse library ?
Thank you for your help, and thank you for providing MFEM, this is an awsome FEM library !

Hi maxenceR,
The typical practice for the libraries is to collect all the header files in one 'include' directory after you 'install' the library. I believe this is the case for SuiteSparse as well. Here is a paragraph from the README.txt:
(6) To install, type "sudo make install".  This will place copies of all
    libraries in /usr/local/lib, and all include files in /usr/local/include.
    You can change the install location by editting SuiteSparse_config.mk.
    These directories must already exist.

So, you might want to set up the proper install locations in the SuiteSparse_config.mk and 'make install'.
Best,
Mikhail

Yes you are right I did not install SuiteSparse. Now it works perfectly, thank you !
Maxence

authors: martemyev maxenceR

repo: mfem/mfem


text:
Silence partial override warnings from #3806

Adds a missing using BilinearFormIntegrator::AssemblePA; to ElasticityIntegrator missing from https://github.com/mfem/mfem/pull/3806. Also fixed the whitespace in bilininteg.hpp for the other integrator classes for consistency (hopefully reduce the likelihood of these copy-paste issues in the future).
I didn't see any warnings with clang or gcc, but nvcc complains loudly about these types of warnings, and building MFEM with CUDA support uses nvcc on every file (maybe it should only be on files with GPU kernels?).

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#4101
@sebastiangrimberg
@pazner
@pazner + @jandrej
1/31/24
1/31/24
⌛due 2/21/24

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...

Yes, these warnings are nvcc specific -- other compilers do not issue them. Looking at our internal nightly CUDA tests, I now see the warnings, however they do not trigger failures, so we do not see them usually. Maybe we can change the test behavior to trigger failures on warnings.

Should be fixed by 4caab0f, sorry about that. I just removed the docstring in GradientInterpolator which is consistent with all other derived classes; the docstring from the base class BilinearFormIntegrator is the one to reference.

There is still a warning with this fix.
linalg/../fem/bilininteg.hpp(3069): warning #611-D: overloaded virtual function "mfem::NonlinearFormIntegrator::AssemblePA" is only partially overridden in class "mfem::ElasticityComponentIntegrator"
class ElasticityComponentIntegrator : public BilinearFormIntegrator

Need fix before L3092 too?

There is still a warning with this fix.
linalg/../fem/bilininteg.hpp(3069): warning https://github.com/mfem/mfem/issues/611-D: overloaded virtual function "mfem::NonlinearFormIntegrator::AssemblePA" is only partially overridden in class "mfem::ElasticityComponentIntegrator"
class ElasticityComponentIntegrator : public BilinearFormIntegrator

Yes good catch. Fixed in 5480f08.

Re-merged in next for testing...

authors: adam-sim-dev pazner sebastiangrimberg v-dobrev


text:
false positives with typescript 2.1.4

Bug Report

Codelyzer version: 2.0.0-beta.1
TSLint version: 4.0.2
TypeScript version: 2.1.4
Running TSLint via: CLI/ Visual Studio / ts-loader

Note: TSLint passes if i remove codelyzer rules & codelyzer from rulesDirectory
TypeScript code being linted
In code below, it's complaining about missing whitespace after equals (=) in the string literal
let offset = 10;
let result = `<path d="M${offset},${offset}/>`;

In code below, it's complaining about missing whitepsaces afer coma (,) inside of the regexp
const hasPercent = /= {0,1}(\.{0,1}\d+)/g.test(this.data.join(','));
In code below, it's complaining about missing semicolon at class closing tag ( } ). It stops complaining if i remove constructor.
import { Component } from '@angular/core';
@Component({
  template: `
    <router-outlet></router-outlet>
  `
})
export class AppBodyComponent {

  constructor(
  ) {}
}

with tslint.json configuration:
{
    "rulesDirectory": [
        "node_modules/codelyzer"
    ],
    "rules": {
        "directive-selector": [true, "attribute", "jm", "camelCase"],
        "component-selector": [true, "element", "jm", "kebab-case"],
        "use-input-property-decorator": true,
        "use-output-property-decorator": true,
        "use-host-property-decorator": true,
        "no-attribute-parameter-decorator": true,
        "no-input-rename": true,
        "no-output-rename": true,
        "no-forward-ref": false,
        "use-life-cycle-interface": true,
        "use-pipe-transform-interface": true,
        "pipe-naming": [true, "camelCase", "jm"],
        "component-class-suffix": true,
        "directive-class-suffix": true,
        "import-destructuring-spacing": true,
        "templates-use-public": true,
        "no-access-missing-member": true,
        "invoke-injectable": true,

        "class-name": true,
        "comment-format": [ true, "check-space" ],
        "indent": [ true, "spaces"],
        "no-duplicate-variable": true,
        "no-eval": true,
        "no-internal-module": true,
        "no-trailing-whitespace": true,
        "no-unsafe-finally": true,
        "no-var-keyword": true,
        "one-line": [ true, "check-open-brace", "check-whitespace"],
        "semicolon": [ true, "always" ],
        "triple-equals": [ true, "allow-null-check" ],
        "typedef-whitespace": [ true,
            {
                "call-signature": "nospace",
                "index-signature": "nospace",
                "parameter": "nospace",
                "property-declaration": "nospace",
                "variable-declaration": "nospace"
            }
        ],
        "variable-name": [ true, "ban-keywords" ],
        "whitespace": [ true,
            "check-branch",
            "check-decl",
            "check-operator",
            "check-separator",
            "check-type"
        ]
    }
}

Not sure my issues are the same but I would say it looks like false positive too.
For the following template (based on ng-boostrap popover example)
<template #popContent>Hello</template>
<a ngbPopover]="popContent">click me</a>

ng lint says The property "popContent" that you're trying to access does not exist in the class declaration.
And for the following statement in template
{{t.errorData.errorMessages[0].message}}

ng lint says The property "message" that you're trying to access does not exist in the class declaration. while it is absolutely correct and even intellisense displays message option if I move this code to TS file.

@mikhailmelnik your issue is duplication of https://github.com/mgechev/codelyzer/issues/179 and fixed but not yet published.
I believe I worked on {{t.errorData.errorMessages[0].message}} as well, not sure if it is in beta.1 yet but I'll verify and if it isn't there I'll work on it.
@guojenman your issues are not related to codelyzer but seems related to tslint. It is weird that you're no longer getting errors with codelyzer. I'll still check and see what's wrong.

@mgechev it is 2.0.0-beta.1, installed with angular-cli v1.0.0-beta.22

Thanks @mgechev. Weird indeed. I've created minimum reproducible project, which I should've included with the original bug report, but attached below instead.
after npm install,
if you run "npm run lint", it will fail.
if you run "npm run lint-no", which is not using codelyzer in rulesDirectory, then works.
codelyzer-lint.zip
btw, loving codelyzer.

@guojenman thanks for this! It'll be really helpful!

@mikhailmelnik the issue is fixed here https://github.com/mgechev/codelyzer/commit/20ce61a64346b9ac17a1d5d5f364889ef90e6d47.

I'm seeing another instance of this:

I'm using:
"codelyzer": "~3.0.1",
"tslint": "~4.5.1",

But still getting the same issue!

authors: JohannesRudolph almothafar guojenman mgechev mikhailmelnik

repo: mgechev/codelyzer


text:
Does textwrap actually need Canvas#data

Hi,
I'm trying to run textwrap on a canvas that I'm creating in a Node environment. I'm able to create a Canvas normally like the browser one, but in a Node environment, however, I want to optimize resources as much as possible.
Is canvas._data used in anyway in the calculations ?
Kindly.

Hi @yanna92yar,
Textwrap itself doens't know anything about canvas or node. However, I wrote a demo to show how you can call Textwrap from a wasm environment: https://github.com/mgeisler/textwrap/tree/master/examples/wasm.
The code there uses the canvas to measure the size of the text, then tells Textwrap about those sizes, wraps the text, and finally draws the text on the canvas.
I hope that helps?

Actually I managed to call draw function just like delivered on the wasm demo, and I'm using a Node canvas implementation, thanks a lot.
for instance , I'm passing same values that would work on the demo just to test what's going wrong:
https://github.com/mgeisler/textwrap/blob/872f221fede7aa78e730bb7895074455269a431a/examples/wasm/www/index.js#L35
this function draw does not fail, however I think it does not change my canvas object (as far as I could inspect)
ok , as long as textwrap does not necessarily deal with the canvas (except the example); do you provide some API with raw results ? (of calculations) ? hopefully in wasm build as well.
Thanks a lot :)

ok, let's forget about the Canvas object , as long as textwrap does not necessarily deal with the canvas (except the example); do you provide some API with raw results ? (of calculations) ? hopefully in wasm build as well.

The interface is abstract: you implement Fragment yourself and this trait is then used by the rest of the Textwrap calculations. As an example, the wrap_first_fit function has this signature:
pub fn wrap_first_fit<'a, 'b, T: Fragment>(
    fragments: &'a [T],
    line_widths: &'b [f64]
) -> Vec<&'a [T]>

which means that you give it a slice of fragments (can be anything, you decide the T type here since you've have implemented Fragment for it) and then you get back the wrapped lines in the form of a vector of slices.
That's the most raw result in Textwrap. You're then supposed to use the vector of slices in your own drawing routine: you will presumably walk through each slice and draw the fragments one after each other. That's what the Wasm demo I include does.

Ok thanks a lot @mgeisler for the clarifications I appreciate that.

Great, I'm glad to hear that you got it working!

repo: mgeisler/textwrap


text:
How to read by column name, not by index

At present, the index is used when reading a column, so it is impossible to determine which column is being read. Is there any way to specify the column name to read?

No, its indexes only.

At present, the index is used when reading a column, so it is impossible to determine which column is being read. Is there any way to specify the column name to read?

@FreeVB not feasible if file is not having row(first) with headers

authors: FreeVB hnmange mgholam

repo: mgholam/fastCSV


text:
🛑 Merchant APP (Core Config API) is down

In 2bfb692, Merchant APP (Core Config API) (https://gateway.wavemoney.io/v2/merchant-api/merchant-core-config) was down:

HTTP code: 403
Response time: 88 ms

Resolved: Merchant APP (Core Config API) is back up in d145381 after 56 minutes.

repo: mgmgpyaesonewin/strapi-upptime


text:
customGETLIST with nested array parameters

Is it possible to use a nested array as a parameter when using customGETLIST to get data from a collection based on the passed in argument? So the code will look something like:
Restangular.all('data').customGETLIST('', {
    user: {
        email: 'email@domain.com'
    }
}).then(function (data){
    $scope.data = data;
    console.log(data);
});

What is the end result you are trying to accomplish? It looks like you're trying to put an object in the URL parameters?

Closing due to the nature and age of issue. Please consider the updated issue guidelines and reopen if needed.

authors: bostrom daviesgeek oakerele

repo: mgonto/restangular


text:
Changes in install generator template

Rails command rails destroy feature:install was not working
Change install generator to take input from user so table name / class
name can be defined by user.
Adds specs for install template using generator_spec gem. Could not add migration spec. Had some
problems with time stamp.

Coverage decreased (-59.6%) to 37.333% when pulling 0dec1ee52c1399c4176e1a35fb87c76e434e6a5b on laertispappas:lp/generator_destroy_fix into 37ea89a1dfbb6a19f56d4e14212f67a36e7d8889 on mgsnova:master.

authors: coveralls laertispappas

repo: mgsnova/feature


text:
Remove no formatters defined message

This is a bit of a preference than a fix, but I think the log doesn't make much
sense & removing it actually can simplify the setup a bit.
autocmd BufWritePre * Format

Instead of keeping track of which filetypes that should be formatted in two
places, the table inside setup & the autocmd.
The user can just add this autocmd & forget about it & the plugin will do the
right thing.

I think im going to keep things the way they are. Thanks thought!

authors: ahmedelgabri mhartington


text:
Error when initializing RedisMemoryServer in global Jest setup

Description
I prefer to use a Jest Global setup file when downloading binaries as opposed to letting it happen during the first occurrence in a test file. This makes it so I don't have to modify Jest timeouts to accommodate for the binary taking longer than the Jest default timeout to download and install, etc
When I try to do this with redis-memory-server, I get some errors. This may be due to the Jest global setup file being in native Node.js and having no TypeScript transformer and the library not being tested to work with native Node.js.
Reproduction Steps

Git clone the reproduction repository at:
npm i
Inspect the global setup file at jest.global-setup.js

const RedisMemoryServer = require("redis-memory-server");

module.exports = async () => {
  const redis = await RedisMemoryServer();
  await redis.stop();
};

npm t
See failures in console

❯ npm t                                                                                15:59:39

> test-redis-memory-server@1.0.0 test /Users/[REDACTED]/Github/test-redis-memory-server
> jest

TypeError: Jest: Got error running globalSetup - /Users/[REDACTED]/Github/test-redis-memory-server/jest.global-setup.js, reason: RedisMemoryServer is not a function
    at module.exports (/Users/[REDACTED]/Github/test-redis-memory-server/jest.global-setup.js:4:23)
    at /Users/[REDACTED]/Github/test-redis-memory-server/node_modules/@jest/core/build/runGlobalHook.js:125:19
    at ScriptTransformer.requireAndTranspileModule (/Users/alecbrunelle/Github/test-redis-memory-server/node_modules/@jest/transform/build/ScriptTransformer.js:895:24)
    at async _default (/Users/[REDACTED]/Github/test-redis-memory-server/node_modules/@jest/core/build/runGlobalHook.js:116:9)
    at async runJest (/Users/[REDACTED]/Github/test-redis-memory-server/node_modules/@jest/core/build/runJest.js:352:5)
    at async _run10000 (/Users/[REDACTED]/Github/test-redis-memory-server/node_modules/@jest/core/build/cli/index.js:408:7)
    at async runCLI (/Users/[REDACTED]/Github/test-redis-memory-server/node_modules/@jest/core/build/cli/index.js:261:3)
    at async Object.run (/Users/[REDACTED]/Github/test-redis-memory-server/node_modules/jest/node_modules/jest-cli/build/cli/index.js:163:37)
npm ERR! Test failed.  See above for more details.

Please look more closely at the README. I don't think await RedisMemoryServer() is a valid way to use this library. This should work:
const { RedisMemoryServer } = require('redis-memory-server')
module.exports = async () => {
  const redis = new RedisMemoryServer()
  const host = await redis.getHost()
  // ...
  await redis.stop()
}

Meant to use new 😵
Thanks


text:
Secure connection failed for Waterfox user-agents

There are reports about people using the Waterfox fork of Firefox not being able to access certain websites. They are getting "Secure connection failed" errors. They can change their user-agents to work around this. It seems not to happen for Linux users.
https://github.com/MrAlex94/Waterfox/issues/178 mentions

https://www.codedog.pl which has "Server: Caddy" in its headers
https://www.beamdog.com which has "Server: Caddy" in its headers
https://pricehipster.com which according to this fairly obscure website has had a "Caddy-Sponsors" header once (now behind Buttflare) http://pricehipster.com.rankank.com/

That's pretty much the only hint at what be going on, they are all served by Caddy.
I suspect the MITM detection to be the culprit as that is the only place where *fox mentioned in the code. Could someone take a look at this? Thanks! :)

Just found https://quakewiki.org has the same issue and of course https://www.quaddicted.com.

What's in the server logs when the connection fails?

All those sites work fine for me in Waterfox. I'd love to see what the logs are.

For https://www.quaddicted.com/ :
I installed Waterfox 56.0.4.1 (64-bit) and the addon UAControl.
I set the user-agent for quaddicted.com to "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0.2 Waterfox/56.0.4"
I get

Secure Connection Failed
The connection to www.quaddicted.com was interrupted while the page was loading.

Clicking the cert info thing in the address bar shows the normal cert dialog and all is fine there.
I see absolutely nothing about that request in the server logs that are configured as
log / /var/log/caddy/access.log "{combined}"
errors /var/log/caddy/errors.log

With ngrep -q "*" all I see is one packet from my client and one packet back from the server. HTTPS so they are encrypted and I have no clue what they say...
If I set the user agent to "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0.2" (same but without the Waterfox suffix), it works fine.
If I set the user agent to "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0.2 " (trailing space), it breaks in the same way as before.

Which version of Caddy are you using? And what does the process log say? (You'll have to use -log to get that.)

Oh ouch, it was still on 0.10.4. It seems to work fine with 0.10.11 now.

authors: SpiritQuaddicted iaretard mholt

repo: mholt/caddy


text:
bifocals didn't draw a card equal to the number of available special achievements

There were about 15 available and it drew a 1 instead.

https://boardgamearena.com/2/innovationalpha?table=422185801

Oh I updated the implementation but forgot to update the actual text of the card. It should say "Draw and foreshadow a [7].  If Bifocals was foreseen, draw and foreshadow a card of value equal to the lowest available standard achievement."

ahh

1 definitely wasn't available so that probably isn't working right either.

Oh this was caused by the AVAILABLE_ACHIEVEMENTS bug. The card behavior will get updated next time I refresh the card list (so we don't need a bug tracking this now).

authors: micahstairs ultimatefiend

repo: micahstairs/bga-innovation


text:
[Feature Request] Improve comment navigation

A shortcut key to scroll to a comment's parent.

Any suggestions? I think it would need to include a keyboard modifier, like shift+j / shift+k?

authors: michael-lazar woorst

repo: michael-lazar/rtv


text:
Update README.md

Removed non existent sync parameter from contents function

Thanks!

authors: aendrew jaimeagudo

repo: michael/github


text:
Add example animating routes

From the comment from UXLayout here: https://github.com/ReactTraining/react-router/issues/3936 doesn't look like there's a "happy path" for this yet.

https://reactcommunity.org/react-transition-group/

https://github.com/animatedjs/animated/issues/63 - should probably wait for this to be ready for latest react

can be done without that lib

https://github.com/michaelBenin/react-ssr-spa/pull/66

repo: michaelBenin/react-ssr-spa


text:
Hotfix 0.12.1 - blender 2.8 install fix

I jumped the gun, please ignore.

Closed due to it being already fixed in the development version.

repo: michaeldegroot/cats-blender-plugin


text:
Wrong compilation

If I understand the following syntax correct - FWS is at least a A or B in the end with and optional amount of A or B before and optional CD
CR = %d43
LF = %d44
WSP = %d41 / %d42
FWS = [*WSP CR LF] 1*WSP

Valid
AAAACDAAA
BABCDBA
CDA
A
AAAABBA
AA

Invalid
AACD
CAA
AAD
DA

But the regex produced is
^((A|B)*CD){0,1}$
Which is missing the end A or B ( again if I read correct)

Aaah it's the repition rule it can't parse
1*WSP gives  ^$

The * was not showing in the start of the code

@KalleDK Could you clarify your comment?
From my own testing of the above ABNF, it looks like it isn't adding the last token to the rules array...

[master c190785] Add missing token at the end of a rule set.

The last comment was just that github didn't show the * in the first post. And you closed before i could answer ;)

Seems to work correct now :)

authors: KalleDK michaelrsweet

repo: michaelrsweet/abnf