Fixes leading slash being added to component-test module name

@Turbo87 As requested in https://github.com/ember-cli/ember-cli/pull/5673. Cheers

That's fast delivery, awesome! Could you maybe add a test case for that as well?

Yes! Definitely. I was looking for tests in the original ember-cli project but I couldn't find any blueprint tests.

They exist but they are much more hidden than here. Don't worry too much about the ember-cli repo though because we're about to remove the majority of the templates there soon. This repo here and ember.js will take over instead.

@Turbo87 Is this any good? I ran the tests and it fails as expected before the change in the other commit. Passes fine afterwards.
I've just written my first test. Yay!

Yeah, that looks exactly how it should be!
@homu r+

:pushpin: Commit 8db0fd5 has been approved by Turbo87

:hourglass: Testing commit 8db0fd5 with merge 623ec64...

:sunny: Test successful - status


misaligned params in vision transformer

Hello, I am getting this warning. Any idea how to fix it?
warnings.warn(
Resize the pos_embed shape from torch.Size([197, 768]) to torch.Size([577, 768])
['prompt_embeddings', 'deep_prompt_embeddings', 'text_proj.weight', 'text_proj.bias', 'prompt_proj.weight', 'prompt_proj.bias', 'prompt_norm.weight', 'prompt_norm.bias'] [] are misaligned params in vision transformer

This is a warning issued when interpolating the positional embeddings to match our resolution of 384 with the pre-trained resolution of 224 in CLIP. There are no issues caused by this output.


🧑💻:  Audio section not in center and not stylish

:red_circle: Title : Make Audio section stylish
:red_circle: Enhancement Aim : Better UI
:red_circle: Changes :  Position in center and add style.
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Bhavy Zala
What is your participant role? Gssoc'24

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@Avdhesh-Varshney Please assign me this task !

@zalabhavy go ahead.


Can`t get data.meta.link when fetch issues by labels

Hello! I have a trouble.
When I get repo issues list -> in response I have data.meta.link, that contain link to last page https://github.com/mikedeboer/node-github/blob/master/api/v3.0.0/issues.js#L110
I use this link to understand what page is last & it's work well
But, when I am trying to get repos issues list by any labels https://developer.github.com/v3/issues/#list-issues-for-a-repository - in response I haven`t data.meta.link and I cannot know what page is last by filter tags, why? And how can I fix it?

Doesn't that just mean the results take up a single page?
"use strict";

var Client = require("./../lib/index");

var github = new Client({
    debug: false
});

github.issues.getForRepo({
    user: "mikedeboer",
    repo: "node-github",
    labels: "feedback welcome"  // TODO: test with this commented/uncommented
}, function(err, res) {
    var hasNext = github.hasNextPage(res);
    console.log(hasNext);
    // console.log(err, res);
});

On a somewhat related note, I believe there's a bug in which providing multiple labels doesn't work.

Nevermind, the labels param does an intersection so if you provide labels A, B, it only gets issues that have both A and B as opposed to A or B.
Closing this. Feel free to open a new ticket if the problem persists.


sl/camera.hpp not found

Hey Guys
i have tried the code that was given in the tutorials. all the time i was getting the error that the sl/camera.hpp: no such file or directory. how to solve this

Hi,
Are you on Windows/Linux? Where did you install the ZED SDK?
Best,
OB

HI
I am using Jetson TX1 for using ZED camera and i have install this in
/usr/local. i have tried each and every thing but still i am not able to do
that.
Thank you
On Mon, Jun 25, 2018 at 3:14 AM Oliver Braun<EMAIL_ADDRESS>wrote:

Hi,
Are you on Windows/Linux? Where did you install the ZED SDK?
Best,
OB
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stereolabs/zed-examples/issues/82#issuecomment-399854884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmQy5FFxqBw3ncxPfJNsllu7wqXQ0xhqks5uAI3PgaJpZM4Uyoxr
.

--
Rahul Jain
Final Year Student
Department of Civil and Environmental Engineering
Indian Institute Of Technology (IIT) Patna
+91-<PHONE_NUMBER>
India

I am on windows and am also receiving the same error.


test: GtfsAgencyTableContainer class

closes #570
Summary:
This PR provides additional unit tests for GtfsAgencyTableContainer.
Expected behavior:
No code change, tests should pass.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "feat: -new feature short description-" (PR title must follow the conventional commit specification)
[x] Linked all relevant issues
~[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)~

Closing as a trivial test to avoid artificially inflating the code base.

Closing as a trivial test to avoid artificially inflating the code base.


BHT-002-GBLW thermostat not working any more

Describe the bug
A clear and concise description of what the bug is.
I have a thermostat device BHT-002-GBLW
2021.9.7 all worked fine. Now it does not work at all.
The thermostat card no longer show a power on/off button. It just shows the temperature dial, device name and 'Off' state.
The temp adjustment clearly has no effect as it is not visible in the tuya iot. Nor is a change made in the tuya iot visible in the card.
The entity_state page shows
hvac_modes: []
min_temp: 1
max_temp: 7
target_temp_step: 0.5
current_temperature: null
temperature: 5
current_humidity: 0
friendly_name: WTS ensuite
supported_features: 1

Expected behavior
Ability to turn heat on and off and control the target temperature and receive the current temperature.
Screenshots
I have added screenshots from iot.tuya.com which seems to indicate that the device is in touch with their cloud, however the temperature of the device reported (4.2c) is unlikely to be correct, the room temp will be in excess of 20c.
Home Assistant Version
2021.10.0
Device info (please complete the following information, which can be found in log):
Have followed the above and enabled critical and tuya as requested - and restarted !
logger:
  default: critical
  logs:
    custom_components.tuya_v2: debug

The only reference to tuya in the logs is this:
2021-10-08 11:39:39 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'tuya', 'timer', 'energy', 'input_boolean', 'evohome', 'device_tracker', 'google_assistant', 'spotify', 'cast', 'spotcast', 'owntracks', 'network', 'media_source', 'samsungtv_smart', 'deconz', 'persistent_notification', 'favicon', 'var', 'broadlink', 'mobile_app', 'pi_hole', 'utility_meter', 'system_health', 'discovery', 'xiaomi_miio', 'shelly', 'octoprint', 'input_select', 'input_datetime', 'binary_sensor', 'automation', 'input_number', 'updater', 'default_config', 'hydrawise', 'scene', 'history', 'ipp', 'usb', 'zeroconf', 'hue', 'python_script', 'map', 'sonoff', 'sonos', 'tts', 'trace', 'met', 'sensor', 'input_text', 'sun', 'tag', 'mqtt', 'light', 'hacs', 'my', 'blueprint', 'google', 'nmap_tracker', 'dhcp', 'switch', 'yeelight', 'tplink', 'browser_mod', 'camera', 'group', 'ssdp', 'script', 'ifttt', 'speedtestdotnet', 'notify', 'climate', 'zone', 'counter', 'logbook'}
2021-10-08 11:40:57 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 80.39s
**Device specifications
BHT-002-GBLW
Additional context
Add any other context or logs about the problem here.
I also have a tuya smart plug which continues to work.

New Tuya/Home-assistant update 2021.11 made my BHT-002 work again - but the "Divider problem" still exists.
In the "old integration" I was able to set-up "custom-deviders per device" directly in the integration on the "integrations->Tuya->Options" button.
This is described in the post here:
https://community.home-assistant.io/t/smart-life-tuya-show-wrong-temperature/89093/157

It would be great to have that option to set- "custom-deviders" in the integration per device (Again) .


Issues with pathing to haarcascade_frontalface_alt.xml

Hey Tristan, great eye tracking system first of all. 😄
Just a heads up, your current implementation as it is in the repository won't run due to the path given to the haarcascade_frontalface_alt.xml file in main.cpp. Since eyeLike's post-build executable location is under build/bin/, the double ellipse count should be two, not three, eg:
cv::String face_cascade_name = "../../res/haarcascade_frontalface_alt.xml";
I might suggest turning the path of said xml file into an argument, so the user can specify where the xml file is without needing to recompile.

Yah that's probably reasonable. The path is correct for the way I build eyeLike with XCode, which puts the binary under build/bin/Debug/, but that's not what happens with command line CMake.
It being a command line parameter that defaults to two levels up seems like a better option indeed.


chore: test only active Django versions

Django 3.0 and 3.1 already got on EOF
I also had forgot to add the Django 4.0 on GHA

would make sense to remove python 3.6 and 3.7 since django 4.0 does not support it anymore ?
https://docs.djangoproject.com/en/4.0/releases/4.0/#python-compatibility


gdp.to_raggedarray

Implement a function gdp.to_raggedarray that is a convenience wrapper of executable code from the GDP hourly example.
clouddrift.adapters.gdp.to_raggedarray() can now be used to generate the ragged array NetCDF from hourly individual files.
Also bumped version to 0.5.0.
Not adding this to the Sphinx docs as its not intended for users. Is that reasonable? We can add this module to the API docs if you think it would be useful.

Could this type of function systematically include an example usage in the help? is that common/good practice?

I generally like examples in docstrings. I think it's a matter of style. For example, here's an examples section for help(np.diff):
    Examples
    --------
    >>> x = np.array([1, 2, 4, 7, 0])
    >>> np.diff(x)
    array([ 1,  2,  3, -7])
    >>> np.diff(x, n=2)
    array([  1,   1, -10])

    >>> x = np.array([[1, 3, 6, 10], [0, 5, 6, 8]])
    >>> np.diff(x)
    array([[2, 3, 4],
           [5, 1, 2]])
    >>> np.diff(x, axis=0)
    array([[-1,  2,  0, -2]])

    >>> x = np.arange('1066-10-13', '1066-10-16', dtype=np.datetime64)
    >>> np.diff(x)
    array([1, 1], dtype='timedelta64[D]')

Xarray also includes examples in docstrings for some functions, though not all.
I'm in favor of it.

Yes, that is great. Let's incorporate those systematically, if possible.

Cool. I'll add examples for this function in this PR, and examples for the rest of the library in a separate PR.

Will add examples to the docstrings in a separate PR and merge this as is. Thanks all.


fix(hotkey): fix two hidden dangers in hotkey_collector

This PR is to solve two hidden dangers in hotkey_collector.
Because the related codes of two dangers are overlapped, I solve them in one PR.
The first hidden danger is if FLAGS_xxx variable is dynamically changing in the future, FLAGS_data_capture_hash_bucket_num might be changing when capturing data, which will cause the memory overflow.
The second hidden danger is _internal_collector might be reset while other threads are using it.

The second hidden danger is _internal_collector might be reset while other threads are using it.
I don't understand what is the hidden danger of it, and how you fix it, maybe you can add more description about it.


Listen on random port

Hi,
Is it possible to listen on random port and get this port in listen callback somehow?

https://unetworking.github.io/uWebSockets.js/generated/index.html#us_socket_local_port
I think you pass 0 as port, then get it

Yes, this works.
Thank you.


Check .env file post checkout

Close #29

@Rantignac or @senzowayne, to test this PR i think that 2 developers must pushed .env changes on this branch.
So if one of you at least can push changes on .env file that would be nice.
Thanks 🙏


When create a proposal, execution period display error

Description
When create a proposal, execution period display error
Steps To Reproduce

Log in...
Ensure a DAO page
Create a Governance proposal, choose voters

Current Behavior

Execution period display error

Expected Behavior

Execution period should display correctly

Environment

Platform: PC
Node: v18.18.0
Browser: Chrome 126.0.6478.56

Display errors, non-contractual errors


TUMUT3 Unit DUIDs incorrect

TUMUT3 list of DUIDs is incorrect. The TUMUT3-1, TUMUT3-1 etc. DUIDS were retired and merged into TUMUT3 as a single DUID

TUMUT3 unit DUID is currently on station SNOWYP - should be on TUMUT3 and the old DUIDs retired

07c3f44c1e131efbf15f59bb25649e47f76da9c2


zx crashes every time a process is sent to scratchpad

As long scratchpad ist empty, sx starts without any problems. Once you sent a process to scratchpad sx crashes immediately with the message "Aborted (core dumped)". Even if some process is already in scratchpad, once you start sx it also stops working.

I can confirm thids behaviour.

Confirm.
(process:30126): GLib-GObject-CRITICAL **: 21:01:08.229: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
*** stack smashing detected ***: <unknown> terminated
[1]    30126 abort (core dumped)  zx -d -p

Cconfirm too


Add label variations for good first issue

I found some project that match the criteria to be added but have variations of the good first issue labels like good-first-issue and :wave: Good First Issue I would like to add these label variations and subsequently add these repos.
Example:

https://github.com/JetBrains/Exposed/issues?q=is%3Aopen+is%3Aissue+label%3Agood-first-issue
https://github.com/apollographql/apollo-kotlin/issues?q=is%3Aopen+is%3Aissue+label%3A"%3Awave%3A+Good+First+Issue"

I assume that adding these labels to labels.json would be sufficient.

I will create a PR for this.

@vasanthdharmaraj This has been merged.


Create ac.eap.gr

domain for ac.eap.gr
Hellenic Open University

@nikosrapt I am sorry, the domain ac.eap.gr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).

@nikosrapt I am sorry, the domain ac.eap.gr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Create Alert List Page

Describe the task
Create the alert list page that lists all the existing alerts
Acceptance Criteria

[ ] Page is created that shows the existing alerts
[ ] create new alert backend end point to return a list of alerts (this will be a public api)
[ ] view button will be created that will load the view page component, but won't have anything in it

PR https://github.com/bcgov/nr-rfc-alertauthoring/pull/21


remove nginx static content as zafira is default tool for login

it seems like this folder is not needed anymore: https://github.com/qaprosoft/qps-infra/tree/master/nginx/html
but we have to test how mcloud/seleniub hub is displayed after removal

during testing we should ensure that

http://hostname - open Zafira
http://demo:demo@hostname/mcloud/grid/console - open mobile selenium hub (make sure static content is displayed correctly like icons, images etc)

Verified on qps-infra develop. Will be created a separate issue for UI page http://demo:demo@hostname/mcloud/grid/console


feat: lunar use dnsaddr

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

Project coverage is 45.38%. Comparing base (2469e7a) to head (f4e75a7).
Report is 191 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3741      +/-   ##
==========================================
+ Coverage   44.83%   45.38%   +0.54%
==========================================
  Files         265      281      +16
  Lines       14620    16032    +1412
==========================================
+ Hits         6555     7276     +721
- Misses       7313     7910     +597
- Partials      752      846      +94

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


Only attempt to use dirvish if b:dirvish exists

This was causing persistent errors when you run, for example,
ls | nvim -c 'setf dirvish'

as dirvish will not yet have set that local variable yet airline will
attempt to use it.

All CI has falled.

included as of 27b52ac


Add declaration for PyEval_InitThreads

As pointed out in the Cython documentation if a C callback function which manipulates Python objects is called from non-Python threads, the PyEval_InitThreads function has be called before the callback is invoked otherwise the interpreter will crash. As Cython does not have a declaration for this function users have to manually create one.
Would it make sense to add a declaration for this function to the existing declarations for CPython?
I am happy to submit a PR if this makes sense.

Sure, anything that's missing should be added, but the easiest is probably to set the C macro __PYX_FORCE_INIT_THREADS=1.

That being said, a less hidden way would probably be nice, e.g. a new directive.

It may worth noting, as mentioned in the posted google-groups link along with the documentation link, that just cimporting the cython.parallel Cython module should suffice to ensure that PyEval_InitThreads is called, doing so would add the InitThreads utility code to the module initialization function, specifically, to __Pyx_InitGlobals.
Therefore, you don't exactly need to use anything from the cython.parallel module to initialize the GIL, and that's independent of whether __PYX_FORCE_INIT_THREADS is defined or not, unlike the case with using the threading library which only initializes the GIL when creating a new thread.


compatibility with older python versions

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 14.703%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
161

Relevant Lines:
1095

💛  - Coveralls


Have the web implementation point to React Native Web instead of React Native

Feature request
Currently, UnimplementedView is used as a general support mechanism to have render compatibility for other non-supported platforms.
For web, ToolbarAndroid.web.js attempts to use it like so
https://github.com/react-native-community/toolbar-android/blob/e7b37ad740580c5ac202524fa888768af419cd67/js/ToolbarAndroid.web.js#L13-L21
However, most web installations alias react-native with react-native-web. Webpack would then try to look for the module in react-native-web/Libraries/Components/UnimplementedViews/UnimplementedView which doesn't exist and thus will always throw a warning.
I think the path should reference react-native-web's actual UnimplementedView path instead of react-native's.
Since .web files are normally only picked up during web targeted builds, I would guess that react-native-web should almost always be installed as well.
Why it is needed

Some CI systems fail on warning by default (that's mine!)
Even though it shouldn't be used on Web

It will error since the module will return {} rather than a generic View component that UnimplementedView implements
This should circumvent that above scenario majority of the time

Even if the module is not found, it will still have the same intended fallback behavior before the change

The current workaround is using webpack's resolve.alias like so
resolve = {
  alias: {
      'react-native/Libraries/Components/UnimplementedViews/UnimplementedView$': 'react-native-web/dist/modules/UnimplementedView',
      'react-native': 'react-native-web',
      ...
  }
}

but I think in a create-react-app scenario, it'd be a huge hassle to tell users to modify the webpack config since it's not readily available.
Possible implementation
Change the path to  react-native-web/dist/modules/UnimplementedView
Code sample
let m;
try {
  // This is an optional dependency. However, webpack might still show warning message.
  m = require('react-native-web/dist/modules/UnimplementedView');
} catch {
  // If failed to find react-native-web's UnimplementedView, just returns an empty module so
  // this won't cause bundling related error, however any subsequent attempt of using this module
  // in such situation shall caused compile-error because it really should not be used for web.
  m = {};
}

I can open a PR if you'd like.

hmmm... if react-native-web is to alias react-native components, I wonder why UnimplementedView is an exception? Would it be better for react-native-web to address this?

Yeah, good point.
I remember finding a comment somewhere by react-native-web's maintainer about module paths being unstable and that we should avoid directly referencing them like in my proposed solution.
So I assume there's some reasoning behind that exception, but I'll try to dig up that comment and maybe open a question/issue in that repo instead.


Performance on iPad2.

Hi,
Thanks for the nice plugin. I am building a word scramble game with phaser and using input plugin. The plugin works nice on desktop and on android devices. But there are some serious performance issues on iPad2. Initially I tried creating several text input fields, but there are some performance issues on iPad2. So I tried creating a single text input field and tried moving it around. But the issue remains same.
Any tips on improving performance on iPad?

Hi vikramarka,
The phaser input plugin not working on mobile devices in my case. Can you please tell me how it is working for you?
This is my code in create function-which works good on desktop, but not working on mobile devices. I have tested it on ipad, and android mobile.
//enable plugin for text input
game.add.plugin(PhaserInput.Plugin);
    //textfield
    name=game.add.inputField(200, 230, {
        font: '29px casual',
        fill: '#000',
        width: 380,
        padding: 10,
        borderWidth: 4,
        borderColor: '#169AC5',
        borderRadius: 20,
        placeHolder:'Name',
        placeHolderColor:'#00549C',
        textAlign:'center',
        type: PhaserInput.InputType.text
    });

Thanks in advance.


build doesn't work with yarn 3

just an FYI because berry yarn 3 is pre-packaged with node 16.10 and beyond via their corepack.
yarn 3 doesn't have the license command so the build breaks here:
https://github.com/looker-open-source/malloy/blob/ab01aa24bce72d591366d658131acd308ddcfaea/demo/malloy-demo-composer/scripts/package.ts#L38

Moved to npm :D


[FEATURE REQ] Return ETag in the response for UpdateDigitalTwinAsync

Library name
Azure.DigitalTwins.Core
Please describe the feature.
In the current implementation of the UpdateDigitalTwinAsync and DeleteTwinAsync methods, the response  class has the ETag buried in Heather element, Could you expose it as a public property similar CreateOrReplaceTwin?

@uriel-kluk Thanks for the feedback! We have routed this issue to the appropriate team to review and provide an update here.


Leaky bucket strategy

Description
I am crossposting this from express-rate-limit, since it is a Store improvement suggestion.
Original post:  #https://github.com/express-rate-limit/express-rate-limit/issues/359#issue-1799456039
Why
.
Alternatives
.

This would be a great feature.


Change the name of -o flag to -overlap flag

Checklist

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[x] I've applied the relevant labels to this PR
[x] I've added relevant tests for my contribution
[x] I've updated the documentation and/or added correct docstrings
[x] I've assigned a reviewer
[x] I've consulted ADS's internal developer documentation to ensure my contribution is in line with any relevant design decisions

Description
As pointed out by Julien in the issue https://github.com/neuropoly/axondeepseg/issues/460, the -o flag for segmenting the images sounds like output, in this PR I've renamed the overlap flag from our default -o flag to -overlap flag.
How to test this PR?

First, do pip install -e . in this branch.
Segment an image using changed flag name; axondeepseg -i <image_name.png> -t <Modality type> -overlap <overlap_value>

Changed Documentation of this PR
https://axondeepseg--474.org.readthedocs.build/en/474/documentation.html#segment-a-single-image
Linked issues
Fixes #460

I think single dash CLI flags are usually meant for single letters. I don't see the point of using -overlap if we already also have --overlap.
Thoughts from anyone else?

In some RTDs, I've seen the practice of single dashed even for words. That's why I added that. If it is true that single dashed are only for letters then perhaps we can remove the -o flag ( in CLI's of several other packages, -o flag usually means 'output'  so it can create confusion among the users) and keep the double dashed --overlap flag of the CLI.

I think single dash CLI flags are usually meant for single letters. I don't see the point of using -overlap if we already also have --overlap.

indeed-- single letter after "-" is the POSIX convention.  I was not aware we already had "--overlap", in this case we can simply drop "-o". In general i'm in favour of getting rid of single dash single letter (becomes confusing).
For some context. It all started (in the lab, inspired by FSL) with SCT using single dash with long words, and no double-dash. We are having this discussion regularly in other projects. Recently for shimming toolbox we decided to stick to POSIX (eg double dash for long words), but avoid single dash. Few discussions:

https://github.com/shimming-toolbox/shimming-toolbox/issues/222
https://github.com/neuropoly/spinalcordtoolbox/issues/2939
https://github.com/neuropoly/spinalcordtoolbox/issues/3159

Perfect - thank you for clarifying the new lab convention @jcohenadad !
So @vs74, I guess all that needs to be done in this PR is removing the -o flag and then it can be merged, correct?

For now, I've dropped the -o flag, and this PR is ready for review. I've dropped the -o flag, changed the documentation added a unit test that was missing for the overlap flag. But we should open an issue too just for the case that if in future we wish to switch to single dash or double-dash entirely for CLI flags, we could refer to that issue.


Neutron - E2E Integration

Some of the Cosmos SDK commands appear to be broken on the neutron node. Our e2e test framework is heavily dependent on the interchaintest framework, and several commands used by the interchaintest framework are causing errors while conducting e2e tests, so we might need to consider an alternative strategy to testing e2e with neutron.
https://discord.com/channels/986573321023942708/1029032555405651998/1133366991189717102
Albert — Yesterday at 5:40 PM
Neutron is consumer chain, gentx command is not working. You can use neutrond add-consumer-section  instead. And also I'd recommend you to build neutron with make install-test-binary  if you want to run it standalone.


Revert "Add no-index tag to /reuse files"

Reverts SumoLogic/sumologic-documentation#3883

Hey, @kimsauce, it looks like the Algolia crawler is working again! So it looks like adding "noindex" to all the reuse content was the cause of the error. I hope you can figure out how to get the crawler to work after you remove indexing from reuse content.


everything is right but it goes error when running

Cause the grid data and the velocity data are stored in different files, I define the Field by the most primitive way
U = Field('U',u,lon = lon , lat =lat,time=time,transpose=False) V = Field('V',v,lon = lon , lat =lat,time=time,transpose=False) fieldset = FieldSet(U,V)
and the sampled the particles at places in the area.
but when running it always goes with the error, out of bounds.
I wonder if there is something important that I have ignored.

Dear @wongchieh. We can't help you without more information. Please provide the full error that you get, and also more information on what the files etc are. An ErrorOutOFbounds typically means that you try to compute a particle on a location that is not within the Field


prevent KeyError exception, fix #532

Coverage remained the same at 68.83% when pulling aef01184a706c0535655cec1f144479ef67cabbe on bashu:patch-3 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.

Coverage remained the same at 68.83% when pulling aef01184a706c0535655cec1f144479ef67cabbe on bashu:patch-3 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.

Coverage remained the same at 68.83% when pulling aef01184a706c0535655cec1f144479ef67cabbe on bashu:patch-3 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.

Coverage remained the same at 68.83% when pulling aef01184a706c0535655cec1f144479ef67cabbe on bashu:patch-3 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.


Dragging doesn't work with New Architecture (0.76)

Thanks for maintaining this library. After upgrading to the latest React Native version 0.76.3, the dragging behaviour is not working. The item doesn't move vertically.
Can you please have a look at what could be the solution?
Thanks!
repo: https://github.com/hollanderbart/RN-BusinessCards
https://github.com/user-attachments/assets/1d92ac52-103a-46e2-a9c0-e4bc00b6aae1
@fivecar can you please review the issue?

Thanks for taking the time to report this, @hollanderbart . Super unclear what the problem was. Empirically derived the solution, which you can see in index.tsx in https://github.com/fivecar/react-native-draglist/pull/54 (ignore all the other changes in that PR, which upgraded the example project to RN 0.76.3).
Searching the internet didn't yield a reason for this breakage either. But I've now gotten things working.

Release 3.6.3 just done, based on this issue. Thanks again, @hollanderbart , for taking the time to make this project better. https://github.com/fivecar/react-native-draglist/releases/tag/3.6.3

We use the project in our app, so we had to have a fix for this issue 😉
I like the philosophy of this solution and also made a blogpost about it: https://xebia.com/blog/drag-drop-sort-implementing-draggable-sorting-in-react-native/
That's for your quick response and fix 🎉

@hollanderbart : thank you! Just linked to your article via https://github.com/fivecar/react-native-draglist/pull/56 in the project's README.md.


LICENSE.md

:author_name <:author_email> Attention to details. Why are there still placeholders in  the License file

This issue has been fixed


Build Failure with MinGW on Windows using vcpkg due to Misuse of target_compile_definitions()

Git commit reference
28d390cb52c019badd4111c208af47ccb6c15225
Describe the bug
Misuse of target_compile_definitions() in CMakeLists.txt for adding compiler flags. This misuse causes a build failure when building on Windows with MinGW, as the command expects preprocessor macros but receives compiler flags instead.
To Reproduce

Attempt to build the library on Windows using MinGW. The relevant CMakeLists.txt file uses target_compile_definitions() to add compiler flags.
Observe the build failure, with error messages indicating "macro names must be identifiers".

Expected behavior
The build process should complete without errors. Compiler flags should be added with target_compile_options() instead of target_compile_definitions().
System Details:

OS:
Compiler: MinGW, GCC
Build system: CMake

Additional context
The problematic CMake code appears to be here:
target_compile_definitions(
	"${LIB_NAME}" PUBLIC
	"DPP_BUILD"
	"$<$<PLATFORM_ID:Windows>:$<$<CONFIG:Debug>:/sdl;/std:c++17;/Od;/DEBUG;/sdl;/MP;/DFD_SETSIZE=1024;/Zc:preprocessor>>"
	"$<$<PLATFORM_ID:Windows>:$<$<CONFIG:Release>:/std:c++17;/O2;/Oi;/Oy;/GL;/Gy;/sdl;/MP;/DFD_SETSIZE=1024;/Zc:preprocessor>>"
)

These lines try to add compiler flags (such as /sdl, /std:c++17, etc.) using target_compile_definitions(), which is (as far as I can understand) meant for preprocessor macros, not compiler flags. As a result, the build process fails with error messages about "macro names must be identifiers".

vcpkg with mingw is not supported.
please use msvc with mingw. we are not able to support every weird combination of compiler everyone throws at it. if you really want to use gcc, use wsl2, and use gcc in its native environment instead of trying to shoehorn it into windows.

issue was reintroduced by https://github.com/brainboxdotcc/DPP/pull/745

Fixed again by https://github.com/brainboxdotcc/DPP/pull/844


035c-idelay-use: fuzzer to get the IN_USE tag for idelays

Signed-off-by: Alessandro Comodi<EMAIL_ADDRESS>This PR is needed to document the IN_USE bits of the IDELAYs.
Being those bits highly correlated to other IDELAYs features, they could not be solved in the idelay original fuzzer.
This small fuzzer instead filters out bits for relative to IDELAYs features to get only the ones relative to the IN_USE tag.

@litghost I wonder whether this PR is actually useful given that I have just learned that https://github.com/SymbiFlow/prjxray/pull/976 solves the same bits.

@litghost I wonder whether this PR is actually useful given that I have just learned that #976 solves the same bits.

I'm evaluating that now.  I think I'd rather just merge #976, as the change that decouples the IOI3 pips is probably a good change to have either way.

Duplicate of #976


A typo of Task[A] in the document

In https://monix.io/docs/3x/eval/task.html
Here, the type of Task[A] may be () => (A => Unit) => Unit rather than (A => Unit) => Unit?

I don't think so.
The (A => Unit) part is the "callback" that can be called when the task has produced a value, and is part of the signature of the various run methods.
A signature like () => (A => Unit) => Unit would lead to client code like task.run()(handleValue)... the first () is unnecessary.

You can view Task as being equivalent to () => (A => Unit) => Unit, this being basically Task's runToFuture.
But the regular runAsync is no different in its signature than Future's onComplete, being (A => Unit) => Unit. I think the confusing factor here is Future, because Future is memoized (being essentially a var), serving as an indirection, but you don't see that when looking at its signature.
Not sure how to describe this to make it correct, however in general in Scala, if you have strict behavior, to make it lazy you wrap it in a thunk, so if A is strict, then () => A will be non-strict and if (A => Unit) => Unit is strict, then () => (A => Unit) => Unit will be non-strict.

In other words, this is a complicated problem and both of you are correct 🙂

Got it. I just read the doc of Monix and Cats Effect, found the difference between these two tables and I was confusing about it. Learned a lot!


OurDB-Database with read-design in README.md?

Hi all.
1. Idea
I would like to send my first read-design commit, that is to improve the visual aspect of the main file: README.md - where people will read general information from OurDB. Please, see this: OurDB-readme.md
1.1 img 1 before

1.2 img 2 after

2. why?

It's an early commit
I would just like to improve the visual aspect of a part of the readme.md file

"-> do not commit direct any new update first contact with author than they will test your module and they will commit."

I want to know if this idea is good or bad before I submit an initial PR.

3. question/feedback
What do you all think of the idea?

thanks for your suggestions. Now I changed the logo as you said to improve visuals. 👍


Trouble extracting patch_d2.mpq

Hey,
Thanks for providing these tools! Alas, when I loading patch_d2.mpq with the MPQ module, I get the following error:
> ts-node src/extract.ts

(node:12412) UnhandledPromiseRejectionWarning: Error: Mpq.Compression: undefined not supported
    at Object.decompressSector (...\node_modules\@diablo2\mpq\src\compression\index.ts:12:13)
    at MpqFile.extract (...\node_modules\@diablo2\mpq\src\mpq.ts:158:39)

I debugged the compression code and the file flags in sector[offset] are just plain "0", if that helps at all. Couldn't find any reference as to what that's supposed to mean. FWIW, also tried bintools but that just doesn't seem to do anything - no error, but also no data extracted it appears.
I am using the code sample from the README:
  // Read from file
  const mpq = Mpq.load('D:\\Games\\Diablo II\\patch_d2.mpq');
  const lang = await mpq.extract('data\\local\\LNG\\ENG\\patchstring.tbl');

The game version is 1.14d, I can connect to b.net just fine and patch installers see no issue with the file. FWIW, it's not the CD distro but downloaded and installed via my b.net account. Maybe CD + patch installation is different to what they ship there?
miffels@LONGEST-JOHNSON-YET:/mnt/d/Games/Diablo II$ sha1sum patch_d2.mpq
331045d97e1e0f439918eeb7151c3b5ff4f65d82  patch_d2.mpq

Alas, I have no reference MPQ file to compare. Any idea what I might have done wrong? Also happy to help/submit fixes if you can point me in the right direction.

Thanks for reporting this, looks like this was caused by a couple of bugs.
mpq.exists(fileName) was always returning true :(
and uncompressed data was not being extracted correctly, I have pushed two commits which should fix both of these issues.
Let me know if they help.

Thanks! Couldn't build it locally for some reason so I did some awful surgery I'd rather not comment, but the mpq bit appears to be passing now. Couldn't quite get the bintools to work, but that may be due to a screw-up on my part. Now I just gotta figure out what to do with those buffers... ;) Loading some of text files from data/global/excel and dumping it as utf-8 resulted in a heap of garbled characters, but it may just be that I need to take a closer look at the specs (or your code :))

Couldn't build it locally for some reason

What was the error you get with building locally? Is it related to installing pcap ?

I think I've found the problem...
My earlier fix was just plain wrong :)  the v1.14 example patch_d2.mpq I just found is compressed with isImplode being set I dont handle isImplode https://github.com/blacha/diablo2/blob/master/packages/mpq/src/mpq.ts#L132
Once I added isImplode logic  the tbl files extracted fine, however they are version 1 not version 0 so Ill need to add some logic for version 1 tbl Ill look to do that tonight if I get some time.

I have fixed the MPQ implode handling
https://github.com/blacha/diablo2/commit/f0e50d7057bbb6ec77303f13ecaf0184312f87ed
I have also fixed the issue with v1 .tbl turns out the index count and hash table count of the files differed (All the MPQs I have had the same numbers)
https://github.com/blacha/diablo2/commit/77d2f8504dabf76ac73c23ac0efc380bfe2eb1a1
Ive also added some test MPQs with tests so hopefully it should just work going forward .
If you could check if it works for you, Ill then version bump and publish a new copy.

Holy cow, you're on fire :)
Sorry for not getting back earlier. I am based in EU so the night got in the way ;)
For reference, this is the install issue I am facing:
$ git status && npm i && npm run build
On branch master
Your branch is up to date with 'origin/master'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)

        package-lock.json

nothing added to commit but untracked files present (use "git add" to track)
npm WARN<EMAIL_ADDRESS>requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.

added 2 packages from 1 contributor, removed 2 packages and audited 948 packages in 4.737s
found 0 vulnerabilities

><EMAIL_ADDRESS>build ...\workspaces\dev\diablo2
> tsc -b

packages/mpq/src/header.ts:1:32 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

1 import { bp, StrutInfer } from 'binparse';
                                 ~~~~~~~~~~

packages/bintools/src/lang/lang.reader.ts:1:32 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

1 import { bp, StrutInfer } from 'binparse';
                                 ~~~~~~~~~~

packages/bintools/src/monster/monster.stat.reader.ts:1:32 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

1 import { bp, StrutInfer } from 'binparse';
                                 ~~~~~~~~~~

packages/bintools/src/item/item.reader.ts:1:20 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

1 import { bp } from 'binparse';
                     ~~~~~~~~~~

packages/bintools/src/item/item.reader.ts:2:38 - error TS2307: Cannot find module 'binparse/build/src/string' or its corresponding type declarations.

2 import { StrutTypeStringFixed } from 'binparse/build/src/string';
                                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~

packages/bintools/src/item/item.reader.ts:3:54 - error TS2307: Cannot find module 'binparse/build/src/type' or its corresponding type declarations.

3 import { StrutParserContext, StrutParserInput } from 'binparse/build/src/type';
                                                       ~~~~~~~~~~~~~~~~~~~~~~~~~

packages/bintools/src/item/item.reader.ts:15:37 - error TS2554: Expected 0 arguments, but got 1.

15 const ItemCode = new ItemCodeParser(4);
                                       ~

packages/bintools/src/mpq.loader.ts:1:44 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

1 import { Diablo2Mpq, Diablo2MpqData } from '@diablo2/data';
                                             ~~~~~~~~~~~~~~~

packages/bintools/src/mpq.loader.ts:2:21 - error TS2307: Cannot find module '@diablo2/mpq' or its corresponding type declarations.

2 import { Mpq } from '@diablo2/mpq';
                      ~~~~~~~~~~~~~~

packages/bintools/src/mpq.loader.ts:3:39 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

3 import { StrutInfer, StrutType } from 'binparse';
                                        ~~~~~~~~~~

packages/packets/src/packet.ts:2:73 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

2 import { bp, StrutAny, StrutInfer, StrutParserContext, StrutType } from 'binparse';
                                                                          ~~~~~~~~~~

packages/packets/src/factory.ts:2:36 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

2 import { StrutParserContext } from 'binparse';
                                     ~~~~~~~~~~

packages/packets/src/packets-pod/data.ts:1:77 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

1 import { Act, Attribute, Difficulty, PlayerClass, UnitType, WarpType } from '@diablo2/data';
                                                                              ~~~~~~~~~~~~~~~

packages/packets/src/packets-pod/data.ts:2:20 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

2 import { bp } from 'binparse';
                     ~~~~~~~~~~

packages/packets/src/packets-pod/data.ts:11:61 - error TS7006: Parameter 'id' implicitly has an 'any' type.

11 export const DataAttribute = bp.lookup('Attribute', bp.u8, (id) => Attribute[id] ?? 'Unknown');
                                                               ~~

packages/packets/src/packets-pod/client.ts:2:20 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

2 import { bp } from 'binparse';
                     ~~~~~~~~~~

packages/packets/src/parser.item.ts:1:103 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

1 import { Diablo2Mpq, ItemActionType, ItemCategory, ItemContainer, ItemDestination, ItemQuality } from '@diablo2/data';
                                                                                ~~~~~~~~~~~~~~~

packages/packets/src/parser.item.ts:2:74 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

2 import { BitStream, bp, StrutBase, StrutInfer, StrutParserContext } from 'binparse';
                                                                           ~~~~~~~~~~

packages/packets/src/parser.npc.ts:1:28 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

1 import { Diablo2Mpq } from '@diablo2/data';
                             ~~~~~~~~~~~~~~~

packages/packets/src/parser.npc.ts:2:69 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

2 import { BitStream, bp, StrutBase, StrutParserContext, toHex } from 'binparse';
                                                                      ~~~~~~~~~~

packages/packets/src/parser.npc.ts:47:53 - error TS2339: Property 'name' does not exist on type 'DataTypeNpc'.

47     if (packetId !== 0xac) throw new Error(`[${this.name}] Invalid packet: ${toHex(packetId)}`);
                                                       ~~~~

packages/packets/src/packets-pod/server.ts:3:20 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

3 import { bp } from 'binparse';
                     ~~~~~~~~~~

packages/packets/src/packets-pd2/client.ts:1:20 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

1 import { bp } from 'binparse';
                     ~~~~~~~~~~

packages/packets/src/packets-pd2/server.ts:1:20 - error TS2307: Cannot find module 'binparse' or its corresponding type declarations.

1 import { bp } from 'binparse';
                     ~~~~~~~~~~

packages/packets/src/packets.ts:1:32 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

1 import { Diablo2Version } from '@diablo2/data';
                                 ~~~~~~~~~~~~~~~

packages/packets/src/packets-pod/__tests__/item.test.ts:2:76 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

2 import { ItemActionType, ItemCategory, ItemDestination, ItemQuality } from '@diablo2/data';
                                                                             ~~~~~~~~~~~~~~~

packages/packets/src/packets-pod/__tests__/npc.test.ts:1:28 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

1 import { Diablo2Mpq } from '@diablo2/data';
                             ~~~~~~~~~~~~~~~

packages/packets/src/packets-pod/__tests__/packet.test.ts:1:21 - error TS2307: Cannot find module '@diablo2/data' or its corresponding type declarations.

1 import { Act } from '@diablo2/data';
                      ~~~~~~~~~~~~~~~

Found 28 errors.

I imagine this is related to some missing MPQ data dump for a few components. binparse may just be missing from the dependencies, perhaps?

Ahh, This project is a monorpepo and uses yarn workspaces  and lerna to manage all the packages.
looks like workspaces was only added to npm v7, so you can upgrade to npm v7 or just use yarn
> npm --version
7.6.0
> ⟩ npm i && npm run build
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. p-limit provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142

added 1095 packages, and audited 1104 packages in 27s

55 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

><EMAIL_ADDRESS>build
> tsc -b

Sorry for not getting back earlier, had to time to take a look this weekend. So I figure there are other issues related to Windows here, but thanks for pointing me top npm v7. I used it somewhere before, but only did so much with monorepos so I might just have forgotten how it worked... :)
In Windows WSL, there are a few extra things to install:

Make
g++

Then the install fails at
npm ERR! make: Warning: File 'pcap_binding.target.mk' has modification time 0.44 s in the future
npm ERR! ../pcap_binding.cc:2:10: fatal error: pcap/pcap.h: No such file or directory
npm ERR!     2 | #include <pcap/pcap.h>
npm ERR!       |          ^~~~~~~~~~~~~
npm ERR! compilation terminated.

Which appears to be a known issue with Windows. I'll see later if any of those workarounds there help.

Sorry missed the response,
PCAP is a bit of a pain to build, its only required if you want to sniff diablo2 network traffic, so I have removed it from the main buildpipeline.
I have also added a windows build to the CI system so hopefully window users wont have issues going forward.

@miffels  If your ok with this, I am going to close the ticket and make a new release. I believe your problem has been fixed.

Hey, sorry for not getting back earlier - I appreciate your support and am sorry to say that I got somewhat sidetracked by Valheim, among other things... :) Don't have access to my home PC atm but tried running the build on a Windows VM. A few setup notes:
> choco list --localonly
Chocolatey v0.10.15
chocolatey 0.10.15
chocolatey-core.extension <IP_ADDRESS>
chocolatey-dotnetfx.extension 1.0.1
chocolatey-visualstudio.extension 1.9.0
chocolatey-windowsupdate.extension 1.0.4
dotnetfx <IP_ADDRESS>90930
git 2.31.0
git.install 2.31.0
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
make 4.3
nodejs 15.12.0
nodejs.install 15.12.0
python 3.9.2
python3 3.9.2
vcredist140 14.28.29913
vcredist2015 14.0.24215.20170201
visualstudio-installer 2.0.1
visualstudio2019-workload-nativedesktop 1.0.1
visualstudio2019buildtools <IP_ADDRESS>
23 packages installed.

Also had to install VS 2019 Community Edition + Desktop Development with C++ separately via the MS manual installer, for some reason, despite setting  npm config set msvs_version 2019 and installing visualstudio2019buildtools and visualstudio2019-workload-nativedesktop via choco. Now I am back at
> pwd

Path
----
C:\Users\...\workspaces\other\diablo2
> npm -v
7.6.3
> npm i
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. p-limit provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code 1
npm ERR! path C:\Users\...\workspaces\other\diablo2\node_modules\pcap
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node-gyp rebuild
npm ERR! Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
npm ERR!   pcap_binding.cc
npm ERR!   pcap_session.cc
npm ERR! C:\Users\...\workspaces\other\diablo2\node_modules\pcap\pcap_binding.cc(2,10): fatal error C1083: Cannot open include file: 'pcap/pcap.h': No such file or directory [C:\Users\...\workspaces\other\diablo2\node_modules\pcap\build\pcap_binding.vcxproj]
npm ERR! C:\Users\...\workspaces\other\diablo2\node_modules\pcap\pcap_session.cc(2,10): fatal error C1083: Cannot open include file: 'pcap/pcap.h': No such file or directory [C:\Users\...\workspaces\other\diablo2\node_modules\pcap\build\pcap_binding.vcxproj]
npm ERR!   win_delay_load_hook.cc
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| win32 | x64
npm ERR! gyp info find Python using Python version 3.9.2 found at "C:\Python39\python.exe"
npm ERR! gyp info find VS using VS2019 (16.9.31112.23) found at:
npm ERR! gyp info find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community"
npm ERR! gyp info find VS run with --verbose for detailed information
npm ERR! gyp info spawn C:\Python39\python.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   'C:\\Users\\...\\workspaces\\other\\diablo2\\node_modules\\node-gyp\\gyp\\gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'msvs',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\...\\workspaces\\other\\diablo2\\node_modules\\pcap\\build\\config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\...\\workspaces\\other\\diablo2\\node_modules\\node-gyp\\addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\...\\AppData\\Local\\node-gyp\\Cache\\15.12.0\\include\\node\\common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=C:\\Users\\...\\AppData\\Local\\node-gyp\\Cache\\15.12.0',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\...\\workspaces\\other\\diablo2\\node_modules\\node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=C:\\\\Users\\\\...\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\15.12.0\\\\<(target_arch)\\\\node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=C:\\Users\\...\\workspaces\\other\\diablo2\\node_modules\\pcap',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'C:\\Users\\...\\workspaces\\other\\diablo2\\node_modules\\pcap\\build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   'build/binding.sln',
npm ERR! gyp info spawn args   '/clp:Verbosity=minimal',
npm ERR! gyp info spawn args   '/nologo',
npm ERR! gyp info spawn args   '/p:Configuration=Release;Platform=x64'
npm ERR! gyp info spawn args ]
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onExit (C:\Users\...\workspaces\other\diablo2\node_modules\node-gyp\lib\build.js:194:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:369:20)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Windows_NT 10.0.19042
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\...\\workspaces\\other\\diablo2\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd C:\Users\...\workspaces\other\diablo2\node_modules\pcap
npm ERR! gyp ERR! node -v v15.12.0
npm ERR! gyp ERR! node-gyp -v v5.1.1
npm ERR! gyp ERR! not ok

npm ERR!      C:\Users\...\AppData\Local\npm-cache\_logs\2021-03-18T11_19_33_519Z-debug.log

Can you confirm that commit 6309f292446d0d5cd4ba015c7d8d91ad44356398 (master HEAD as of now) should not include pcap?

Can you confirm that commit 6309f29 (master HEAD as of now) should not include pcap?

pcap is not mentioned anywhere in the yarn.lock so there should not be any pcap.
I just cloned a fresh copy and ran yarn and no pcap was installed.
> ls node_modules/pcap
ls: cannot access 'node_modules/pcap': No such file or directory

Curious - installing with Yarn does work for me, as opposed to NPM. Looking good!


Support DNS over proxy

I often need to connect to an internal network (for example a docker overlay network) through a socks proxy. In docker swarm, services are accessed through their service names. I think it works the same way for k8s and other similar cloud solutions. The IP addresses are never fixed (services are stopped and created dynamically). The service names will resolve to the correct IP address, but only if the DNS resolver of the docker overlay network (or the equivalent) is used.
It is possible to overcome this problem by installing dnsmasq, and configuring a split-brain DNS resolver over a port that is forwarded through the socks proxy. But it has lots of disadvantages. It is difficult to configure, and it interferes with the local DNS resolver (especially the DNS servers pushed by VPN connections).
A much better solution would be the following. We could have a checkbox on the connection/network proxy tab. The label for the checkbox would be this: "use DNS over the proxy". When the SOCKS connection is initiated, DBeaver would send the hostname to that, instead of resolving the IP address with the local resolver.

Thank you for request


Crashes during drafting of reply

Environment
Pixel 4a running CalyxOS, Android 11.
F-droid Mobile App v1.5.0
Steps to reproduce

Received email from ProtonMail address.
Clicked reply at the bottom of app screen.
Near immediate crash of app. Message was saved in Drafts.
Re-entered app, entered Drafts, clicked on saved draft to construct reply.
Immediate crash.

Expected behavior
Allow me to construct reply email.
Actual behavior
Instant and repeated crashes.
Including (low quality lol) screen recording below.
https://user-images.githubusercontent.com/74485231/126925409-8acd2ca3-b101-40db-9f4f-cb0e1b86d30d.mp4

Hello @SecretestSquirrel ! Unfortunately, I was unable to repeat the issue you described. Perhaps there were some unusual characters in the received letter, or was it formed with additional parameters?
You can also enable the Report bugs in the app settings, restart the app and repeat steps to reproduce this issue on your device. This will help us to analyze which errors in the code lead to this issue.

Yeah, I have force stopped, then when ahead and completely uninstalled/reinstalled, I cannot even begin to draft an email or response whatsoever. As soon as I tap the compose button it takes me to the email composition page, then within 2 seconds crashes completely and all I'm left with is a floating notification at the bottom of the screen letting me know it had been saved as a draft. This is on reply or compose direct.
Honestly have no idea what to do, the app is completely unusable for me, again on Pixel 4a running CalyxOS v2.8.0, Android 11. The web version works perfectly fine, so I am able to do what I need to do from there, but I am really at a loss as to how I can help try to fix this issue in the F-droid app v1.5.0.

hi @SecretestSquirrel . You can help find the cause of the error. If you can, please activate the bug reports feature in the app settings as I described above, and then repeat the steps for reproducing the issue on your device.

having the same issue 👋
xiaomi mi 9
android 11 (aosp)

not sure if it can be related
I changed a lot of settings before this started to happen
and also I replaced my pgp keys (and also lost all my emails 😂)
and now also:
my contacts crush
turning off contacts decryption is not working

hi @SecretestSquirrel . You can help find the cause of the error. If you can, please activate the bug reports feature in the app settings

I have done this, and created a couple more crashes. Note, these are on the newest version of the app now, v1.5.1, rather than the original v1.5.0 the original report was about. It actually seems to have gotten a little worse now, as I cannot even begin to simply compose a message, not just a reply.
https://user-images.githubusercontent.com/74485231/130525790-56bfbe73-86cf-47de-a569-b50835e24493.mp4

@alexdwork2018
Did you get the error's traceback to debug?

@xxxcrow In the new version. The new version now handles broken contacts that cannot be decrypted. But the ability to break contacts is still there, be it an unusual flow with generating and removing additional keys in mailboxes or intentional user actions. It will be fixed when enough details will be collected about this issue.


add adapters sequences from BGI/MGI sequencing data to built-in adapters

Hi.
I noticed that on the SEQanswers forum a document from BGI has been posted that lists all sequences for the oligos and primers used for BGISEQ/DNBSEQ/MGISEQ library preparation.
See here for the thread (2nd post).
On page 7:
The following sequences are used to filter the adapter contamination in raw data.
Forward filter:  AAGTCGGAGGCCAAGCGGTCTTAGGAAGACAA
Reverse filter:  AAGTCGGATCGTAGCCATGTCGTTCTGTGAGCCAAGGAGTTG

Could these 2 (or maybe all listed) sequences be added to the set of built-in adapters fastp uses?
Thanks,
Guido

Ok, I will add them.

After a search, I cannot confirm that this two sequences are BGI-Seq adapters.
I will contact BGI-Seq team to get their official adapter sequences, and update fastp as well.

Great, thanks for your willingness to do this!
BTW, out of curiosity, how did you check this / were not able to confirm?

I have got response from BGI team, they will send me the adapter list in a couple of days.
I will update then and release a new fastp version.

Being curious: was the BGI team able to provide the adapter sequences?

Any update on this? I also just received my first BGISeq data.

Kind reminder; I am about to receive another BGISeq data set. Thanks!

Hi, I just got the sequences from MGI. I will update the built-in adapter  sequences.

I just add MGI/BGI adapter sequences to the known adapters:
knownAdapters["AAGTCGGAGGCCAAGCGGTCTTAGGAAGACAA"] = ">MGI/BGI adapter (forward)";
knownAdapters["AAGTCGGATCGTAGCCATGTCGTTCTGTGAGCCAAGGAGTTG"] = ">MGI/BGI adapter (reverse)";

Could you please try the latest build, or use the latest prebuilt binary?
If you can upload a small MGI/BGI data, I can also have a try.

Sorry for my delayed reply.
I used the latest version on Github (0.21), and compared the results obtained with the version before (0.20.1). To my surprise, both results were exactly the same. Is this expected, even though adapter trimming likely was done by BGI??
Still, I would have expected that some BGI adapters should have been found/trimmed, especially when these are specifically searched for. Thus that the results should (at least) be slight different, but not identical.
Filtering result:
reads passed filter: 43562268
reads failed due to low quality: 0
reads failed due to too many N: 0
reads failed due to too short: 0
reads failed due to low complexity: 2182
reads with adapter trimmed: 2837340
bases trimmed due to adapters: 14182202

Adapter or bad ligation of read1
The input has little adapter percentage (~0.217030%), probably it's trimmed before.

Adapter or bad ligation of read2
The input has little adapter percentage (~0.217030%), probably it's trimmed before.

fastp run command:
fastp --in1 ./TEST_IN/RNA-1/RNA-1_1.fq.gz --in2 ./TEST_IN/RNA-1/RNA-1_2.fq.gz --out1=./TEST_OUT/RNA-1/RNA-1_1.fq.gz --out2=./TEST_OUT/RNA-1/RNA-1_2.fq.gz --low_complexity_filter --thread=16 --json ./TEST_OUT/RNA-1/RNA-1.fastp.json --html ./TEST_OUT/RNA-1/RNA-1.fastp.html

Since your data is paired-end, fastp can trim the adapters without adapter sequence provided. So it already worked before.

Aha, I got it.
I was a little confused; I assumed that since the adapter sequence auto-detection is disabled by default for PE data, adapter detection overlap analysis would also be disabled.
However, I now understand that these are 2 separate processes, and that for PE data the latter (= adapter detection by per-read overlap analysis) is always occurring (and apparently cannot be disabled). Hence, results between versions are identical...

Aha, I got it. I was a little confused; I assumed that since the adapter sequence auto-detection is disabled by default for PE data, adapter detection overlap analysis would also be disabled. However, I now understand that these are 2 separate processes, and that for PE data the latter (= adapter detection by per-read overlap analysis) is always occurring (and apparently cannot be disabled). Hence, results between versions are identical...

above your fastp run command: had no --detect_adapter_for_pe, becuase it default is turn off for your PE data, so it you got the same result for two runs(0.21 + 0.20.1) ?
For PE data, the adapter sequence auto-detection is disabled by default since the adapters can be trimmed by overlap analysis. However, you can specify --detect_adapter_for_pe to enable it.


Less with the death

Having the life of a baby seal hang in the balance was far too much pressure for pr reviews. Plus, have you ever had a baby seal be disappointed in you? Very motivating.

I just noticed this change in action and I love it so much! Thank you! 🙇


Removed low-value browser tests

I removed a lot of browser tests that were a bit fragile. Here are the cases were I removed tests.

If the test was testing if a string existed
If the test didn't test any logic in the template
If the test could be broken by the CMS alone

I updated a few tests to include missing stories from the activity log and adjust for adding - Consumer Financial Protection Bureau to all our titles.
Testing

gulp test:acceptance or gulp test:acceptance --sauce=false

Review

@anselmbradford
@jimmynotjim
@sebworks

Todos

There's a lot of things that could be tested on wagtail pages, but since we don't have a good way to match what we have locally to beta, this is hard to do. Additionally we run into the same problems of depending on CMS generated content that can break tests.

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

:+1: , I would remove qa-hooks from the templates as well if they are being deleted from the tests.

:+1: When everything is moved to wagtail, we might just have to check items exist, or the text length is greater than zero since we won't be able to guarantee the content.

Would it make sense to check high-traffic pages that don't change often for functional things, like expandables working and multi-selects generating properly.

@sebworks Good looking out on the extra unused qa-hooks. Removed in 033a1ec

:+1: , @KimberlyMunoz.


Skip PF for "i915" resource when it has VFs

NOTE: this has impact only for GPUs which are virtualized with SR-IOV.
Access to physical devices (PFs) is disabled for "i915" resource when they have configured virtual devices (VFs).
This is because:

GPU resources are expected to be evenly split between VFs in such configurations

But PF resource amount is expected to differ from VFs and typically retain only enough resources (just few MB of RAM), to be able to provide GPU metrics that are not available from VFs

Neither the current GPU plugin, nor Kubernetes scheduling in general, has proper support for heterogeneous GPUs (= capability based scheduling)

Therefore "i915" resource needs to be limited to GPU devices with homogeneous amount of resources, which in SR-IOV configurations is expected to be the case only with VFs (when such are present).

Related sysfs files are described e.g. here: https://android.googlesource.com/kernel/common/+/refs/heads/android-mainline/Documentation/ABI/testing/sysfs-bus-pci

PS. Current HW / FW / i915 kernel module combination does not support resource amounts differing between VFs, or PF having same amount of resources as what VFs have.  But configuring them differently should be possible later on.
It would be good to have a note about the expected SR-IOV GPU configuration also in Intel plugins documentation before that, but I don't know where.
(If devices operator will get support for setting up i915 kernel module, I assume it will also have support for setting up suitable SR-IOV configuration for it.)

What the heck is "opae-nlb-demo" image build:
standard_init_linux.go:219: exec user process caused: no such file or directory
The command '/bin/sh -c ldconfig' returned a non-zero code: 1
make: *** [opae-nlb-demo] Error 1
Makefile:140: recipe for target 'opae-nlb-demo' failed

and why it would fail when I'm only modifying "intel-gpu-plugin" files and build of that succeeds both with docker & buildah?

and why it would fail when I'm only modifying "intel-gpu-plugin" files and build of that succeeds both with docker & buildah?

it's a random Clear Linux thing.

If it's randomly failing, is there some reason why it's not dropped from CI (or fixed)?
And can I get the PR CI tests to be re-run without modifying my branch, or do I need to do some dummy change for that?

Chatted with Dmitry and pushed following changes:

Dropped "vf-no-pf" case.  It's not relevant for this change (it was remains from additional changes I had re-factored out)
Dropped "physfn" sysfs files as they're not needed by this particular change (also remains from additional changes)
Updated test-case descriptions (added "sriov-" prefix & numeric PF/VF counts)

(And added link to PCI device files descriptions to first PR comment.)

Mikko said that ClearLinux image / CI issue is fixed, so I pushed no-op "git commit --amend -C HEAD" to re-trigger testing.
Note that depending on whether #628 or this PR gets in first, I need to refactor the other PR to take into account test-case changes.  I have no preference on which goes in first.


[fix] cms board posts #delete

Coverage remained the same at 82.868% when pulling 5da8ee17a36d140e356d56ad519df2332e2783b3 on itowtips:board into 034031cc612ae50da114e9060219da54352aa735 on shirasagi:master.


scipy.sparse.diags does not handle empty diagonal (IndexError: list index out of range)

import scipy.sparse
scipy.sparse.diags([], 0)

Expected result: 0x0 sparse matrix
Actual result:
/home/shomea/a/andreros/anaconda3/envs/py27/lib/python2.7/site-packages/scipy/sparse/construct.pyc in diags(diagonals, offsets, shape, format, dtype)
    138         # now check that there's actually only one diagonal
    139         try:
--> 140             iter(diagonals[0])
    141         except TypeError:
    142             diagonals = [np.atleast_1d(diagonals)]

IndexError: list index out of range

I havent looked too much into the code, but changing line 141 to except (TypeError, IndexError) seems like a quick fix.
Python 2.7.11 |Anaconda 2.4.0 (64-bit)| (default, Dec  6 2015, 18:08:32)
scipy.version '0.16.1'
numpy.version '1.10.4'

I can confirm that this still happens on the master branch. I submitted a PR (linked above) with a fix.

This was fixed.


fbaby.yml

[x] Have you signed the Contributor License Agreement?
[x] Are you working against an Issue?

Microsoft Reviewers: Open in CodeFlow

Without any discussion around why a new workflow would be desired, this PR is getting closed.


Change debug_symbols scons argument from bool to enum

resolves https://github.com/godotengine/godot/issues/72247
Seems simpler than adding logic to coerce debug_symbols to True when debug_symbols=yes is passed
EDIT: switching to an enum while preserving old behavior

In the long term, we should move this setting to an enum with the values debug_symbols=no|embedded|separate.

Old values should be read for compatibility with existing scripts, with yes being embedded and separate_debug_symbols=yes turning this into separate if debug_symbols is yes.

Technically, if we want true compatibility, we should accept all the values of BoolVariable.
TRUE_STRINGS = ('y', 'yes', 'true', 't', '1', 'on' , 'all')
FALSE_STRINGS = ('n', 'no', 'false', 'f', '0', 'off', 'none')

https://scons.org/doc/latest/HTML/scons-api/_modules/SCons/Variables/BoolVariable/

Thanks for the contribution! I'll need to review this in depth. I appreciate the effort to preserve compatibility, but at the same time I'm not too fond of the added complexity and relative hackiness of what we need to do for this. But I'm not asking for any change of design, I need to review properly first and see if I eventually agree with the design decision, or want to propose an alternative approach.

That's fair! I'll probably revisit this myself later as I agree it would be a good change.


DSSAT Not recognizing irrigation filex information for reported dates or days after planting

Hello,
After numerous trial-and-error, I am unable to get DSSAT to recognize the irrigation information in my filex file for the cases of irrigation on reported dates or irrigation on days after planting. I carefully followed the example filex from the DSSAT help, but when I run the simulation, irrigation is not applied on the dates set in the filex.
I'm attaching here a zip file containing my experiment file G0000001.MZX with all necessary input files and my DSSAT 4.8 executable (compiled for windows from the latest code available from github).
To run the simulation, unzip the contents to a folder, open Windows command prompt in that folder and run the command:
.\DSCSM048 A G0000001.MZX
The OVERVIEW.OUT file will say:
WATER BALANCE  : IRRIGATE ON REPORTED DATE(S)
IRRIGATION     :        0 mm IN     0 APPLICATIONS
After checking my filex for errors, I think this is a bug in DSSAT.
When I modify my filex however to run with automatic irrigation, the simulated crop does receive irrigation. It is only in "reported dates" or "days after planting" mode that no irrigation is applied.
If someone can help me resolve this issue that would be greatly appreciated.
Irrigate_Reported_Dates_Test.zip

Hi @helsharif!
I checked your file. Your file is missing the irrigation level in treatment section. You need to select the irrigation level for your treatment.
Here is your file corrected (rename the extension back to MZX):
G0000001.txt
Please use the https://dssat.net/contact-us/ for questions, even if you think is a bug. We can check and then open an issue afterwards if needed.
Thank you.
Fabio Oliveira


Using async data for meta while using GoRouter

First: thanks for developing this package! It is surprising that something like this is missing from Flutter.
I am trying to build an ecommerce web app. The routing (using GoRouter) to the page of the product is something like "product/:id".
In your example of how to use meta_seo with GoRouter you hard-code the meta information. However, I do not have access to the meta information at the moment you suggest we add the meta info.  That information would be loaded within the page, after fetching it from the API using the product ID.
Would it be OK to define the meta object and add it once the API response with the product data is received?

Need some code snippets to understand you.

Sure!
I am talking about setting up the metadata after fetching the data of the product, since I don't know it beforehand.
Something like this:
fetchProductData(string id) async {
  http.get(Uri.parse('https://example.com/api/v1/products/$id'))
      .then((response) {
        // Define MetaSEO object with optional needed attributes
        MetaSEO meta = MetaSEO(
            ogTitle: response.name,
            description: response.description,
            keywords: response.tags
        );

        // add meta seo data for web app
        meta.seoOGTitle();
        meta.seoDescription();
        meta.seoKeywords();
      };
  }

Is this ok?
Isn't metadata linked to a specific URL? How would it know it?

Good question. Yes just wrap the MetaSEO into GoRouter builder with FutureBuilder.
Example:
GoRoute(
path: '/',
builder: (BuildContext context, GoRouterState state) {
    return FutureBuilder(
      initialData: 0,
      future: Future.delayed(const Duration(seconds: 2), () {
        // TODO:: Define MetaSEO object with optional needed attributes
        MetaSEO meta = MetaSEO(
            author: 'Eng Mouaz M AlShahmeh',
            description: 'First Screen',
            keywords: 'Flutter, Dart, SEO, Meta, Web, First Screen');

        // TODO:: add meta seo data for web app
        meta.seoAuthor();
        meta.seoDescription();
        meta.seoKeywords();

        return 1;
      }),
        builder: (context, snapshot) {
        if(snapshot.data == 1) {
          return const FirstScreen();
        } else {
          return const LoadingScreen();
        }
    });
  },
)

Thanks,

Or like this

Yes just wrap the MetaSEO into GoRouter builder with FutureBuilder.

Can you please explain why this is necessary?
I'd rather not wrap a full page with future builder (for architectural reasons). I'd rather initialize the page and, in that page, do the loading.
Is there an issue if I use the same approach but not directly inside the GoRoute method?


Allow passing non heap objects to WeakRef

This should allow at least pointers to the data section to work seamlessly with WeakRef and in some cases even allow stack pointers to be passed, for the crazy. This should increase the usability of WeakRef since it allows passing static data for testing or other purposes.
This also renames WeakRef#target to WeakRef#get WeakRef#value. get seems to be the more general, more widely used and shorter name. value is consistent with Pointer. Additionally target feels like it's leaking implementation details as
that's the name of the internal instance variable too.
As expected this is slightly slower for the heap case, given the additional check, and slightly faster for the non-heap case, given the check is less expensive than registering a pointer with GC. A quick benchmark with collection disabled so the second testcase wouldn't crash:
            WeakRef heap  14.42M ( 69.36ns) (±11.41%)       fastest
        WeakRef constant  10.55M (  94.8ns) (±45.52%)  1.37× slower
    CheckingWeakRef heap   9.14M ( 109.4ns) (±45.29%)  1.58× slower
CheckingWeakRef constant  11.48M ( 87.07ns) (±83.27%)  1.26× slower

Java use #get. C# use #target.
I think I picked from C# back then.
I could agree that changing to #value since it would match the Pointer(T) method. But I feel that #get is too generic.

I could live with value, what do others think?

#value to be consistent with Pointer looks good to me.

I like #value too :-)

@jhass Nice! I always test WeakRef with WeakRef.new("foo") and see it crash and then remember "oh, it's not in the heap". It's something ugly that should probably not crash at all, so this PR is very welcome! :-)


fix(retry): fix the retry policy do not take affect

What type of PR is this?

What this PR does / why we need it (en: English/zh: Chinese):
The logic of retry is before the router, the value of key RouterClusterKey can't be found, so use wildcard temporarily.
en:
zh: 执行重试策略的逻辑在 router 前面，重试策略获取的 key 是 router 的时候设置的，会导致在获取重试策略的时候找不到对应的配置。暂时先通过设置一个通用的重试策略解决，这样就没法根据路由给每个 route 配置一条单独的重试策略，只能全局配置一个。
Which issue(s) this PR fixes:

We can extent the retryer to use router logic and do the retry based on retry policy from RDS.

We can extent the retryer to use router logic and do the retry based on retry policy from RDS.

Fixed, I will test in actual environment later

We can extent the retryer to use router logic and do the retry based on retry policy from RDS.

Fixed, I will test in actual environment later

ok👍


请更新一下docker image里面matplotlib或python的版本

描述问题
docker image build无法通过，matplotlib和py版本不兼容
重现步骤
直接clone仓库下来，sudo ./docker.sh run就会中招
截图&日志
[ysun@SYSUCC-ZQ-server 12306]$ sudo ./docker.sh run
[sudo] password for ysun:
Building ticket
Step 1/8 : FROM python:2.7.15
 ---> afc94ac1e19b
Step 2/8 : WORKDIR /usr/src/app
 ---> Using cache
 ---> 52adcb230d51
Step 3/8 : ADD . /usr/src/app
 ---> Using cache
 ---> 25efc37f39fb
Step 4/8 : ENV DEBIAN_FRONTEND noninteractive
 ---> Using cache
 ---> b936bdc16ca4
Step 5/8 : ENV TZ Asia/Shanghai
 ---> Using cache
 ---> 6e08223a4709
Step 6/8 : RUN pip install -i https://pypi.tuna.tsinghua.edu.cn/simple pyspider --no-cache-dir -r requirements.txt
 ---> Running in f1be6c468a4c
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting pyspider
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/d0/97/d6062c928f53d899ff2a8538fed11d4d425ba3d27c96248a2c601c1c9fef/pyspider-0.3.10.tar.gz (110kB)
Collecting beautifulsoup4==4.5.3 (from -r requirements.txt (line 1))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/cf/9b/8a6891f8c349431ee94669ce592fc375a19d4e3f4273a01a47207c7990b2/beautifulsoup4-4.5.3-py2-none-any.whl (85kB)
Collecting bs4==0.0.1 (from -r requirements.txt (line 2))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/10/ed/7e8b97591f6f456174139ec089c769f89a94a1a4025fe967691de971f314/bs4-0.0.1.tar.gz
Collecting PyYAML==5.1.1 (from -r requirements.txt (line 3))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/a3/65/837fefac7475963d1eccf4aa684c23b95aa6c1d033a2c5965ccb11e22623/PyYAML-5.1.1.tar.gz (274kB)
Collecting six==1.10.0 (from -r requirements.txt (line 4))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/c8/0a/b6723e1bc4c516cb687841499455a8505b44607ab535be01091c0f24f079/six-1.10.0-py2.py3-none-any.whl
Collecting requests==2.18.4 (from -r requirements.txt (line 5))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/49/df/50aa1999ab9bde74656c2919d9c0c085fd2b3775fd3eca826012bef76d8c/requests-2.18.4-py2.py3-none-any.whl (88kB)
Collecting Pillow (from -r requirements.txt (line 6))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/cc/a4/79b5f36d1e1a2b426073bd62217d1530fcd939950c2936651e6b39127a9b/Pillow-6.1.0-cp27-cp27mu-manylinux1_x86_64.whl (2.1MB)
Collecting wrapcache==1.0.8 (from -r requirements.txt (line 7))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/39/5f/fee52c29d0887a0457f256d7503d2bea1ad3fe9d02d269b1374db400a757/wrapcache-1.0.8.zip
Collecting ntplib==0.3.3 (from -r requirements.txt (line 8))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/29/8b/85a86e01c510665b0790d3a9fd4532ad98aba9e185a676113a0ae3879350/ntplib-0.3.3.tar.gz
Collecting sklearn (from -r requirements.txt (line 9))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/1e/7a/dbb3be0ce9bd5c8b7e3d87328e79063f8b263b2b1bfa4774cb1147bfcd3f/sklearn-0.0.tar.gz
Collecting opencv-python (from -r requirements.txt (line 10))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/1e/c8/37b2c4520fcb24e68c1b2a9e20dee679ac813bc6750777aa5ba064c8056f/opencv_python-<IP_ADDRESS>-cp27-cp27mu-manylinux1_x86_64.whl (28.7MB)
Collecting keras==2.2.4 (from -r requirements.txt (line 11))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/5e/10/aa32dad071ce52b5502266b5c659451cfd6ffcbf14e6c8c4f16c0ff5aaab/Keras-2.2.4-py2.py3-none-any.whl (312kB)
Collecting tensorflow (from -r requirements.txt (line 12))
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/d3/59/d88fe8c58ffb66aca21d03c0e290cd68327cc133591130c674985e98a482/tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl (109.2MB)
Collecting matplotlib>=3.0.2 (from -r requirements.txt (line 13))
  Could not find a version that satisfies the requirement matplotlib>=3.0.2 (from -r requirements.txt (line 13)) (from versions: 0.86, 0.86.1, 0.86.2, 0.91.0, 0.91.1, 1.0.1, 1.1.0, 1.1.1, 1.2.0, 1.2.1, 1.3.0, 1.3.1, 1.4.0, 1.4.1rc1, 1.4.1, 1.4.2, 1.4.3, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 2.0.0b1, 2.0.0b2, 2.0.0b3, 2.0.0b4, 2.0.0rc1, 2.0.0rc2, 2.0.0, 2.0.1, 2.0.2, 2.1.0rc1, 2.1.0, 2.1.1, 2.1.2, 2.2.0rc1, 2.2.0, 2.2.2, 2.2.3, 2.2.4)
No matching distribution found for matplotlib>=3.0.2 (from -r requirements.txt (line 13))
You are using pip version 19.0.3, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
ERROR: Service 'ticket' failed to build: The command '/bin/sh -c pip install -i https://pypi.tuna.tsinghua.edu.cn/simple pyspider --no-cache-dir -r requirements.txt' returned a non-zero code: 1

环境信息

Manjaro Linux
使用docker
订票小助手版本 1.1.101

FROM python:3.7.4就可以了

@bioinformatist 您好，请问一下docker image还可以用吗

我试着用了一下，似乎chrome会有问题，一直302

@zhtangsh docker image里面似乎没有chrome，把COOKIE_TYPE设置为0试试吧

此工具已经停止支持python2了。请使用最新代码进行构建。


Questions regarding lfs_tag_splice(), LFS_TYPE_SPLICE, tempcount

I'm trying to investigate the source code of littlefs. From what I understand, LFS_TYPE_SPLICE is the type1 for LFS_TYPE_CREATE and LFS_TYPE_DELETE, and for LFS_TYPE_CREATE lfs_tag_splice() returns 1 while for LFS_TYPE_DELETE it returns 0xff but I cannot understand what's the actual meaning of these values. For example, this return value is used in the following piece of code:
if (lfs_tag_type1(tag) == LFS_TYPE_NAME) {
                // increase count of files if necessary
                if (lfs_tag_id(tag) >= tempcount) {
                    tempcount = lfs_tag_id(tag) + 1;
                }
            } else if (lfs_tag_type1(tag) == LFS_TYPE_SPLICE) {
                tempcount += lfs_tag_splice(tag);

                if (tag == (LFS_MKTAG(LFS_TYPE_DELETE, 0, 0) |
                        (LFS_MKTAG(0, 0x3ff, 0) & tempbesttag))) {
                    tempbesttag |= 0x80000000;
                } else if (tempbesttag != -1 &&
                        lfs_tag_id(tag) <= lfs_tag_id(tempbesttag)) {
                    tempbesttag += LFS_MKTAG(0, lfs_tag_splice(tag), 0);
                }
            } else if (lfs_tag_type1(tag) == LFS_TYPE_TAIL) {

which I cannot understand so far. My assumption is that tempcount holds the currently calculated number of files in the directory but I'm not sure since in the line
tempcount += lfs_tag_splice(tag);

from what I understand, we add 1 for LFS_TYPE_CREATE, and 0xff for LFS_TYPE_DELETE that makes no sense to me. Also, in lines
                if (lfs_tag_id(tag) >= tempcount) {
                    tempcount = lfs_tag_id(tag) + 1;
                }

Does this mean that the number of files in the directory is always bigger than the number of the biggest tag id in the directory?

I already figured it out. Initially, I didn't pay attention that the 0xff value is cast to int8_t, i.e. it's turned into -1.

Ah yes, the theory here is we could at some point add "splice" tags with deletions to the mdir larger >1. But I think this is unlikely to ever actually happen....


fix(list): minification-safe element type comparison

Codecov Report

Merging #509 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #509      +/-   ##
==========================================
+ Coverage   96.62%   96.62%   +<.01%
==========================================
  Files          59       59
  Lines        1984     1985       +1
  Branches      235      235
==========================================
+ Hits         1917     1918       +1
  Misses         67       67

Impacted Files
Coverage Δ

packages/list/index.js
89.18% <100%> (+0.09%)
:arrow_up:

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 179b865...b525147. Read the comment docs.

TESTS: https://github.com/material-components/material-components-web-react/pull/511

@dan-kwiat while we wait for tests please sign the PR by commenting "I signed it"


i want to download pdf in ie <= 9 version  doc.save to use

Hi dude i want to download pdf in lower versions in IE <=9  jspdf.js which is not supporting in internet explorer.please suggest me.

IE <=9 support being discussed in the following issues: https://github.com/MrRio/jsPDF/issues/485 and https://github.com/MrRio/jsPDF/issues/425

Duplicate of various IE support issues


.Net: AutoFunctionCalling with multiple functions used is slow and costly

Describe the bug
When my prompt is targeting 2 functions, using AutoFunctionCalling with ChatCompletionService, it spams... And takes a very long time to output the first thing. It took ~3-4 minutes before it finished. Look at my outputs below<PHONE_NUMBER>s etc.)
This is my prompt:
Correct my text and then write an article based on it: There wes once a chield named Bob, he was 20 year's old and, skipped school many times.
These are my 2 functions imported into the kernelBuilder.Plugins:
public sealed class Prompts
{
	public static PromptTemplateConfig WriteArticlePrompt => new()
	{
		Name = "WriteArticle",
		Description = "Write an article based on the input text.",
		Template = @"
					The article should be around {{$wordCount}} words, and written in a professional yet engaging manner that gives readers in-depth insight.

					The information you receive is either a JSON format or regular text:
					+++++
					{{$input}}
					+++++

					Your article should balance detail with an easy-to-understand presentation so that it appeals to both professionals and general readers who want to gain a deeper understanding of the data.

					Important: Always respond in danish.",
		InputVariables = [
			new() { Name = "input", Description = "Input text for article creation, which can be provided in either JSON format or as plain text.", IsRequired = true },
			new() { Name = "wordCount", Description = "The amount of words in the article", IsRequired = false, Default = 250 }
		],
		ExecutionSettings = PromptHelper.GetOpenAIPromptExecutionSettings(maxTokens: 4000, temperature: 0.7, topP: 0.9)
	};

	public static PromptTemplateConfig ProofReadPrompt => new()
	{
		Name = "ProofRead",
		Description = "Proof read the input text.",
		Template = @"
					You are an expert in proofreading, and you must correct spelling and grammar errors from the input text.
					You must retain the structure and formatting.

					The text to be proofread is:
					+++++
					{{$input}}
					+++++

					Important: Always respond in danish.",
		InputVariables = [
			new() { Name = "input", Description = "The text to be proofread.", IsRequired = true }
		],
		ExecutionSettings = PromptHelper.GetOpenAIPromptExecutionSettings(maxTokens: 4000, temperature: 0, topP: 0)
	};
}

PromptHelper:
public static Dictionary<string, PromptExecutionSettings> GetOpenAIPromptExecutionSettings(int maxTokens, double temperature, double topP)
{
	return new()
	{
		["default"] = new OpenAIPromptExecutionSettings()
		{
			ToolCallBehavior = ToolCallBehavior.AutoInvokeKernelFunctions,
			MaxTokens = maxTokens,
			Temperature = temperature,
			TopP = topP
		}
	};
}

outputs this in console:
info: ProofRead[0]
      Function ProofRead invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 227. Completion tokens: 45. Total tokens: 272.
info: ProofRead[0]
      Function ProofRead invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 227. Completion tokens: 44. Total tokens: 271.
info: ProofRead[0]
      Function ProofRead invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 226. Completion tokens: 44. Total tokens: 270.
info: ProofRead[0]
      Function ProofRead invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 226. Completion tokens: 44. Total tokens: 270.
info: ProofRead[0]
      Function ProofRead invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 226. Completion tokens: 44. Total tokens: 270.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 226. Completion tokens: 44.
info: ProofRead[0]
      Function ProofRead succeeded.
info: ProofRead[0]
      Function completed. Duration: 3.8613405s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 513. Completion tokens: 61. Total tokens: 574.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 513. Completion tokens: 61.
info: ProofRead[0]
      Function ProofRead succeeded.
info: ProofRead[0]
      Function completed. Duration: 14.923791s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 476. Completion tokens: 60. Total tokens: 536.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 476. Completion tokens: 60.
info: ProofRead[0]
      Function ProofRead succeeded.
info: ProofRead[0]
      Function completed. Duration: 26.9558434s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 475. Completion tokens: 60. Total tokens: 535.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 475. Completion tokens: 60.
info: ProofRead[0]
      Function ProofRead succeeded.
info: ProofRead[0]
      Function completed. Duration: 36.3937266s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 474. Completion tokens: 60. Total tokens: 534.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 474. Completion tokens: 60.
info: ProofRead[0]
      Function ProofRead succeeded.
info: ProofRead[0]
      Function completed. Duration: 46.6882647s
info: WriteArticle[0]
      Function WriteArticle invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 256. Completion tokens: 49. Total tokens: 305.
info: WriteArticle[0]
      Function WriteArticle invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 256. Completion tokens: 49. Total tokens: 305.
info: WriteArticle[0]
      Function WriteArticle invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 256. Completion tokens: 49. Total tokens: 305.
info: WriteArticle[0]
      Function WriteArticle invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 256. Completion tokens: 49. Total tokens: 305.
info: WriteArticle[0]
      Function WriteArticle invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 256. Completion tokens: 49. Total tokens: 305.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 256. Completion tokens: 49.
info: WriteArticle[0]
      Function WriteArticle succeeded.
info: WriteArticle[0]
      Function completed. Duration: 3.702877s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 559. Completion tokens: 509. Total tokens: 1068.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 559. Completion tokens: 509.
info: WriteArticle[0]
      Function WriteArticle succeeded.
info: WriteArticle[0]
      Function completed. Duration: 47.5458742s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 1090. Completion tokens: 509. Total tokens: 1599.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 1090. Completion tokens: 509.
info: WriteArticle[0]
      Function WriteArticle succeeded.
info: WriteArticle[0]
      Function completed. Duration: 94.9418102s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 1095. Completion tokens: 509. Total tokens: 1604.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 1095. Completion tokens: 509.
info: WriteArticle[0]
      Function WriteArticle succeeded.
info: WriteArticle[0]
      Function completed. Duration:<PHONE_NUMBER>s
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 1097. Completion tokens: 509. Total tokens: 1606.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 1097. Completion tokens: 509.
info: WriteArticle[0]
      Function WriteArticle succeeded.
info: WriteArticle[0]
      Function completed.
Screenshots
All above, as text.
Platform

OS: Windows 11
IDE: VS 2022
Language: C#
Source: 1.4.0

Additional context
No

Update:
After changing the PromptHelper class above, to this (removing AutoInvoke in there, because I use it already in my ChatCompletionService):
public static Dictionary<string, PromptExecutionSettings> GetOpenAIPromptExecutionSettings(int maxTokens, double temperature, double topP)
{
	return new()
	{
		["default"] = new OpenAIPromptExecutionSettings()
		{
			MaxTokens = maxTokens,
			Temperature = temperature,
			TopP = topP
		}
	};
}

It started to be faster, but still slow.
Now the output is:
info: ProofRead[0]
      Function ProofRead invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 113. Completion tokens: 28. Total tokens: 141.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 113. Completion tokens: 28.
info: ProofRead[0]
      Function ProofRead succeeded.
info: ProofRead[0]
      Function completed. Duration: 2.2518528s
info: WriteArticle[0]
      Function WriteArticle invoking.
info: Microsoft.SemanticKernel.Connectors.OpenAI.OpenAIChatCompletionService[0]
      Prompt tokens: 143. Completion tokens: 583. Total tokens: 726.
info: Microsoft.SemanticKernel.KernelFunctionFactory[0]
      Prompt tokens: 143. Completion tokens: 583.
info: WriteArticle[0]
      Function WriteArticle succeeded.
info: WriteArticle[0]
      Function completed. Duration: 79.961413s

It looks like all of the slowness is coming from the WriteArticle prompt. It doesn't look like it's using that many tokens. Are you using a slow version of gpt-4? Are you able to use gpt-3.5-turbo for the article generation?
Function calling may also be slow because you are sending the entire article back to the chat history, which would consume a lot of tokens (every subsequent function call would have to be sent the entire article). You may be able to drive greater performance by wrapping the prompts in a native function that saves the article in Kernel.Data. You could then access this from subsequent functions so that prompt tokens are wasted passing the article back and forth.

Hi @matthewbolanos I don't remember. At the time of the post, I always use the latest and best GPT version.
The issue was probably that my WriteArticle prompt did have executionSettings with AutoInvoke in it as well as my calling with InvokeAsync that also has executionSetttings with AutoInvoke.