gevent upgrade breaks pykafka 2.4.0 import

PyKafka version: pykafka==2.4.0
Kafka version: N\A
pykafka 2.4.0 is failing to import due to revision on gevent library
previous working version of gevent which was getting installed was 1.2.2, but now it's pulling in version 1.3.0 which breaks as below:
  File "/home/ubuntu/our-product/libs/pos/task/common.py", line 11, in <module>

    from core.kafka.kafka_utils import send_kafka

  File "/home/ubuntu/our-product/core/kafka/kafka_utils.py", line 6, in <module>

    from pykafka import KafkaClient

  File "/home/ubuntu/our-product/.tox/py27/local/lib/python2.7/site-packages/pykafka/__init__.py", line 3, in <module>

    from .cluster import Cluster

  File "/home/ubuntu/our-product/.tox/py27/local/lib/python2.7/site-packages/pykafka/cluster.py", line 36, in <module>

    from .topic import Topic

  File "/home/ubuntu/our-product/.tox/py27/local/lib/python2.7/site-packages/pykafka/topic.py", line 23, in <module>

    from .balancedconsumer import BalancedConsumer

  File "/home/ubuntu/our-product/.tox/py27/local/lib/python2.7/site-packages/pykafka/balancedconsumer.py", line 31, in <module>

    from kazoo.handlers.gevent import SequentialGeventHandler

  File "/home/ubuntu/our-product/.tox/py27/local/lib/python2.7/site-packages/kazoo/handlers/gevent.py", line 32, in <module>

    class SequentialGeventHandler(object):

  File "/home/ubuntu/our-product/.tox/py27/local/lib/python2.7/site-packages/kazoo/handlers/gevent.py", line 63, in SequentialGeventHandler

    class timeout_exception(gevent.event.Timeout):

AttributeError: 'module' object has no attribute 'Timeout'

We're on a fairly older version of pykafka, so I'm hoping there's a slightly newer version that might have changed the requirement that we can easily upgrade to, otherwise we're just pinning gevent==1.2.2 for now.
A patch revision on 2.4.0 that pessimistically pins to gevent ~>1.2 would also work.
Thanks

PyKafka version: pykafka==2.5.0
We are seeing the same problem with Gevent's latest release.
Traceback (most recent call last):
  File "/test/test_collect.py", line 14, in <module>
    from collectlib.collect import collect_main
  File "/app/collectlib/collect.py", line 25, in <module>
    from pykafka import KafkaClient
  File "/usr/local/lib/python2.7/dist-packages/pykafka/__init__.py", line 3, in <module>
    from .cluster import Cluster
  File "/usr/local/lib/python2.7/dist-packages/pykafka/cluster.py", line 36, in <module>
    from .topic import Topic
  File "/usr/local/lib/python2.7/dist-packages/pykafka/topic.py", line 23, in <module>
    from .balancedconsumer import BalancedConsumer
  File "/usr/local/lib/python2.7/dist-packages/pykafka/balancedconsumer.py", line 31, in <module>
    from kazoo.handlers.gevent import SequentialGeventHandler
  File "/usr/local/lib/python2.7/dist-packages/kazoo/handlers/gevent.py", line 32, in <module>
    class SequentialGeventHandler(object):
  File "/usr/local/lib/python2.7/dist-packages/kazoo/handlers/gevent.py", line 63, in SequentialGeventHandler
    class timeout_exception(gevent.event.Timeout):
AttributeError: 'module' object has no attribute 'Timeout'

It looks like GEVENT has ballooned from 1.6 MB to 4.2MB
Our (old) successful build using
Collecting gevent>=1.1.0 (from pykafka==2.5.0->-r /workspace/requirements.txt (line 3))
Downloading gevent-1.2.2-cp27-cp27mu-manylinux1_x86_64.whl (1.6MB)

And the new one that is crashing with the above error:
Collecting gevent>=1.1.0 (from pykafka==2.5.0->-r /workspace/requirements.txt (line 3))
Downloading https://files.pythonhosted.org/packages/4f/12/8d06eafbddf8e58cfd3869319e087d9f5d2eb052e0374b87f6b153042b1c/gevent-1.3.0-cp27-cp27mu-manylinux1_x86_64.whl (4.2MB)

We have taken to pinning the version of GEVENT to gevent==1.2.2 . This fixes our issue for now.

@eedwards-sk @DavidEllis008 thanks for the reports. Apparently this is due to Kazoo's reliance on a non-public gevent API, which has been fixed in its master branch. For the time until that change is released in a numbered version, I've pinned pykafka's gevent dependency here.

Just a side note: I have submitted a PR to kazoo last month and it has been merged. But it appears that they are not releasing a new version yet. https://github.com/python-zk/kazoo/pull/503

@emmett9001 A new kazoo release is ready. Can we use gevent 1.3 now? Thanks.
https://github.com/python-zk/kazoo/commit/66fa0dfbe1234ad0431f142c5c9c3381d88828cd

@carsonip pull requested here https://github.com/Parsely/pykafka/pull/818


If/else Regex in dask dataframe (str.contains) not working

I am having an issue passing columns through this regex logic. In pandas, this logic works, but using a dask dataframe, the if statement doesn't catch or change anything.
df = dd.read_csv('chicago_taxi.csv') print(df.dtypes)
Trip_Id                        object
Taxi_Id                        object
Trip_Start_Timestamp           object
Trip_End_Timestamp             object
Trip_Seconds                    int64
Trip_Miles                    float64
Pickup_Census_Tract           float64
Dropoff_Census_Tract          float64
Pickup_Community_Area         float64
Dropoff_Community_Area        float64
Fare                          float64
Tips                          float64
Tolls                           int64
Extras                        float64
Trip_Total                    float64
Payment_Type                   object
Company                        object
Pickup_Centroid_Latitude      float64
Pickup_Centroid_Longitude     float64
Pickup_Centroid_Location       object
Dropoff_Centroid_Latitude     float64
Dropoff_Centroid_Longitude    float64
Dropoff_Centroid_Location      object
Objects should be changed to date/time type or str based on this:
for column in df.columns:         if df[column].dtype == 'object':           if (df[column].str.contains(r'\d{4}-\d{2}-\d{2} \d{2}\:\d{2}\:\d{2}', regex = True).all()):             df[column] = dd.to_datetime(df[column])           else:               df[column] = df[column].astype('str')
However, this changes all objects to datetime64[ns]
Trip_Id                       datetime64[ns]
Taxi_Id                       datetime64[ns]
Trip_Start_Timestamp          datetime64[ns]
Trip_End_Timestamp            datetime64[ns]
Trip_Seconds                           int64
Trip_Miles                           float64
Pickup_Census_Tract                  float64
Dropoff_Census_Tract                 float64
Pickup_Community_Area                float64
Dropoff_Community_Area               float64
Fare                                 float64
Tips                                 float64
Tolls                                  int64
Extras                               float64
Trip_Total                           float64
Payment_Type                  datetime64[ns]
Company                       datetime64[ns]
Pickup_Centroid_Latitude             float64
Pickup_Centroid_Longitude            float64
Pickup_Centroid_Location      datetime64[ns]
Dropoff_Centroid_Latitude            float64
Dropoff_Centroid_Longitude           float64
Dropoff_Centroid_Location     datetime64[ns]

See #5743 .  You need to explicitly call .compute() after the all call if you want to use it within an if statement.  Beware though that this will incur the cost of reading through all the data each time though, which may be expensive.
You might consider doing this check for columns at once.

After including .compute(), I get the same output as first reading in the data in terms of the data types. Any ideas? Thanks for the response.

I'm not sure exactly what you're asking.  If you think that you've found a bug then I encourage you to produce a minimal reproducible example.  See https://blog.dask.org/2018/02/28/minimal-bug-reports

@esokoli can you provide a minimal example? If so, I'll reopen this and we can figure out where the bug is.


Use custom search expression

Problem
Currently, we use vscode.workspace.findFiles('**/*.md') to find all fiels that we are about to parse (parse.ts)
This finds files in the whole workspace which might not be desirable. My particular use case is that I've got two folders in my workspace:

permanent notes
reference notes

The permanent notes are about a particular topic and the reference notes are notes taken from a book or an article. permanent notes are almost always linking to reference notes (i.e. saying that I learnt that particular information in book XYZ).
The current parsing mechanism results in showing huge clusters of notes all linked by reference note (a book or an article) whilst I'm only interested in the connections between permanent notes.
Suggested solution
We could allow users to configure the findFiles expression. So instead of
parse.ts
const files = await vscode.workspace.findFiles(
    `**/*{${(getFileTypesSetting() as string[]).map((f) => `.${f}`).join(",")}}`
  );

we would use the configured value and only if that's missing, we would default to the current expression:
const searchExpression = getConfiguration("searchExpression");
const defaultExpression = `**/*{${(getFileTypesSetting() as string[]).map((f) => `.${f}`).join(",")}}`;
const files = await vscode.workspace.findFiles(searchExpression || defaultExpression);

This would be the most performant solution, but we could as well introduce some allow/deny list that would be used when we iterate through the findFiles() result:
for (const file of files) {
    const hiddenFile = path.basename(file.path).startsWith(".");
    if (!hiddenFile) {
      promises.push(fileCallback(graph, file.path));
    }
  }

How does this sound @tchayen ?

Definitely having a findFiles regex is ok for me (as we have similar one for ignoring files).
It is also important to make sure that then those two won't collide. Probably it makes it sense to skip the other if one is provided.
@ingalless do you have some thoughts about it?

I have a folder with old versions of my notes which is in my .gitignore - it would be nice to have an option to respect the .gitignore, as vscode does by default with e.g. the file picker. Having a custom regex would totally work as well, though!


[BUG] Maps not displaying in jupyter notebook

Context
I'm trying to plot a map, I have somethign like this
mh = Map(
    [
    cba_ctr, # this is a scatter layer
    building_layer, # this is a polygon layer
    ],
    view_state={"longitude": -63.616672, "latitude": -38.416097, "zoom": 10}
)
mh

and I get this but no map display
Map(layers=[ScatterplotLayer(get_fill_color=(0, 128, 0, 255), get_radius=10.0, table=pyarrow.Table
geometry: f…

OS: OSX
Lonboard Version: 0.9.3 (I do have geopandas 1.0 because I need it as a requirement for something else, not sure if that's a problem)

Steps to reproduce the bug
I see the same in the examples in the docs here in In[7] no map display
https://developmentseed.org/lonboard/latest/examples/internet-speeds/#fetch-data
Screenshot for reference:

It seems like the issue came from having a mixed installation of jupyter with conda and the rest of the packages with pip. Having everything installed with pip fixed the issue. Apologies for the spam.


Dependence on CPPUTEST_HOME and MakefileWorker.mk

To quote http://cpputest.github.io:

This is by far the easiest way to install it, via:
$ apt-get install cpputest

I get the include files and the library, but there is nothing that works as CPPUTEST_HOME or path to MakefileWorker.mk. Shell scripts included under /usr/share/cpputest create makefiles that depend on this variable and MakefileWorker.mk. The same is true for the book code in TDD for Embedded C. Because of this I think building CppUTest from source is the easiest.
Is it supposed to be like this, or could the install option be improved?

I was bit by this issue today as well. Ubuntu 15.04 Vivid. Trying to use the TDD for Embedded C book code downloaded from the pragprog website. I'm going to try to build from source since that seems to be the only way to get the book code to work.

Hi Matt
Sorry for not replying sooner.
I've put the book code on github and updated the build environment.
https://github.com/jwgrenning/tddec-code
Some files have moved, but the code is more up to date there  You might
try that.
Depending on your gcc, you may need to adjust the options in the
makefile.
James

James Grenning - Author of TDD for Embedded C - wingman-sw.com/tddec
wingman-sw.com
wingman-sw.com/blog
twitter.com/jwgrenning
facebook.com/wingman.sw
Cell: +1<PHONE_NUMBER>
Office: +1<PHONE_NUMBER>

On 1 Jun 2015, at 10:08, Matthew Beckler wrote:

I was bit by this issue today as well. Ubuntu 15.04 Vivid. Trying to
use the TDD for Embedded C book code downloaded from the pragprog
website. I'm going to try to build from source since that seems to be
the only way to get the book code to work.

Reply to this email directly or view it on GitHub:
https://github.com/cpputest/cpputest/issues/285#issuecomment-107566373

I added a Makefile that builds the examples with an installed CppUTest. Closing this for now.


Update Peer Dependencies

Summary
Resolves #1241
Peer Dependencies need to be updated to prevent the console errors from occurring.

Just curious. Is this something we just need to remember to update manually next time or is there some way to make lerna also update for us when publishing.

At this point in time, to see the newest updates within the site examples, we will also need to update the dependencies in terra-site even though we are not publishing the package


Dumb Question Adding new Device

Sorry for the Dumb question, ive just brought a new Eufy Motion Sensor, added in the Eufy App as normal, but how do i get it to show up in the Home App, Do i need to remove and add the bridge again ( ive tried restarting the bridge in HomeKit No luck)
Ive checked in the Home App under bridges and can see all my Eufy devices except this new one am i being stupid can someone point me in the right direction
Cheers
Chris

@saltysmith1 Should work if you restart homebridge.

@saltysmith1 Should work if you restart homebridge.

sorry  it was me being dumb i forgot to share the new device with my second account sorry will close this my bad sorry


(WIP) Issue #466 - Organization Profiles

Marked as WIP because there are more elements to come.

Assuming the changes look good, do you want to merge this now? Looking at the original issue, I think perhaps everything else is, or should be, covered by separate issues.
Things done:

Admin access level
Manage volunteer list - add/remove, promote/demote admin
Contact list (as part of #468)
Resources table (as part of #468)

Things not done:

Tasks/Requests: I could create a table view for this, but (a) looking at the recently added functionality, it seems not to link with Organizations yet, and (b) similarly to recent discussion in #468, I can't help think some kind of 'shared' table view with 'fixed' organization/disaster Id would be the most efficient way to achieve such functionality, without repetition. I think an issue was possibly going to be created for this at some point.
Information/Updates: This seems a distinct piece of work... I don't know if there's another issue for it.

If it looks good to you, I will review and merge (if you are done can you remove WIP in the PR title - that's our convention for 'ready to go')  Thanks!

Ok - ready for you to review and merge, thanks.

Reviewed and merging.  Looks great.
(Sorry for the delay in review, the holiday weekend and a couple other days off from the project slowed me down).
:shipit:


Handling secrets in ETOS

Description

We need to handle secrets being passed through ETOS securely
Motivation

We are today sending all datasets (from the ETOS client) and the provider information (from the environment provider) in clear-text no matter which information it is.
There must be a way to send credentials.
Exemplification

If we are starting delegation jobs in Jenkins we need to pass the credentials from the environment provider to the suite runner. This password is in clear-text and available to just about anyone. This would make it very easy to get access to the Jenkins instance.
Benefits

Security
Possible Drawbacks

More difficult to test (and harder to use if implemented poorly)

Moved to 1.6.0 due to lack of time for testing


delete files from S3 prior to select_all_records dag

Since the batch size and concurrent jobs configuration has an effect on the filenames of files written to S3, we would need to delete the files in S3 so that the transmission DAG doesn't send duplicate records that are spread across different files. Maybe we delete files in S3 at the beginning of the selection DAG to avoid this potential issue.

In the meantime we can run this:
aws s3 rm s3://folio-data-export-development/full-dump-marc-files --profile folio-dev --recursive


Webscan Fuzz Path: Return Fuzz Metadata

Signal Update

Start Time of Fuzz
End Time of Fuzz
Count of paths tried

Purpose

Enable creation of a Multiple HTTP RR Pair object

Question
I don't see the value of returning a list of all the paths tried. This creates  bloated signal with data that isn't used in the processor. The only reason I can see to do this is to be able to surface in the UX the paths tried to the user but I see this as a p2 and something we should focus on when we have an 'events' primitive (or something like it) that can store this data in a more correct manner. Lmk if you agree
Note 1
Initially I was thinking of adding rate limit detection logic to this tool. I realized this would overly complicate the processor + CLI and break our paradigm of keeping tools scoped to one function. I will create a separate subcommand that creates 'alot' of requests and returns rate limit specific data
Note 2
I am feeling a lot of pain trying to communicate the outcome of an 'event' via ontology objects. I think we need to reprioritize creating an 'events' primitive. RFC will be sent on Monday

Isn't it important to know if a path gets a hit? e.g. /foo/bar/secrets.txt

Isn't it important to know if a path gets a hit? e.g. /foo/bar/secrets.txt
Yes all that logic is still there. I didn't remove any of the 'positive' hit logic just simply added some meta data about the engagment to the signal


DSA 2.2.9 Searching & Sorting Algorithms : Merge Sort - Video

Description
Description
Implement and explain Merge sort Algorithm
Task

[ ] Video

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Mention the type of contribution you want to make.
Kindly refer to the Issue Guidelines.
Do not use the assign command for this issue. Follow the above procedure.
In case you see that the issue has already been assigned, try to request a different task within the same issue.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be the same as the issue.
This issue is only for 'GWOC' contributors of the 'DSA' Domain.

Domain
DSA
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Domain
DSA
Type of Contribution
Audio
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Domain
DSA
Type of Contribution
Video
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Hey @goelesha, I would like to work on this issue. Can you please assign me this issue.
Name: Hassan Rahim
Batch: DSA Batch-2
Type: Documentation

Hey @goelesha, I would like to work on this issue. Can you please assign me this issue.
Name: Hassan Rahim
Batch: DSA Batch-2
Type: Documentation

Hey @goelesha, I would like to work on this issue. Can you please assign me this issue.
Name: Hassan Rahim
Batch: DSA Batch-2
Type: Documentation

Hey @goelesha, I would like to work on this issue. Can you please assign me this issue.
Name: Hassan Rahim
Batch: DSA Batch-2
Type: Documentation

@HassanRahim26 Pls read the title of the issue carefully. This issue is for a video on merge sort.

@goelesha, is there any issue related to Merge Sort which you have opened in which, we have to contribute in Documentation form.

@HassanRahim26 It is already assigned

Hey @goelesha, I would love to contribute to this issue. Can you please assign me this issue.
Name: Uzma Firoz Khan
Batch: DSA Batch-10
Type: Video

Also,I just selected documentation in the form submitted during enrolment . Is it okay if I switch to video?

@uzma024 Assigning the issue to you for video. Make sure to submit a PR within 7 days.
I can't really comment about the things you have selected during enrollment or how exactly contributions will be counted. You can confirm with the GWOC team.

Yeah I've confirmed. Thanks for assigning.

Please do assign this to me.

@goelesha I've made the video and upload it on google drive with some resources. I am not able to upload video on YouTube. Should add the g drive link instead, for the PR?


Report save according to nameing scheme

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

Problem statement
Is there a way to automatically save a report according to its naming scheme?
Suggested solution
Currently reports are stored internally according a naming scheme. But when generating the report is is saved according the name given in the admin panel. Can we somehow save the report with the report number SO_123
Describe alternatives you've considered
We already know the order name use that to save it as pdf??
Examples of other systems
No response
Do you want to develop this?

[ ] I want to develop this.

Yes, this is possible - https://docs.inventree.org/en/latest/report/report/#filename-pattern

@SchrodingersGat ,
thanks for the response but it seems not working for me.
i entered following in the system panel:

but that also results in the sales report being saved as:
S59_I{(ref_04d}}.pdf
did i miss something?

That's completely the wrong setting. As specified in the link above you need to adjust the "filename pattern" for each specific report in the admin interface.


Retread with Spring Framework 5, Spring Boot 2, Cloud Finchley and Reactive examples

The next iteration of this workshop should catch up with recent advances and offerings of the subject-mentioned ecosystem projects.

All examples and content updated to Spring Boot 2.1 and Spring Cloud Greenwich


Register 0.1.14

@JuliaRegistrator register
Bop version number for Nemo in Project.toml

Registration pull request created: JuliaRegistries/General/98403
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.14 -m "<description of version>" a3a915e82f5609717b491d86ec5524127a3fdeec
git push origin v0.1.14


Minifying ability request

Would be great if Web2Executable add an option to use Google Closure Compiler or other minifying tool on the JS, CSS, JSON and HTML files before to pack the project.

Thanks! That's a awesome suggestion!

I'm not strongly against it, but don't you think it's more the responsibility of gulp or grunt, to make project ready for deployment?

@saitonakamura You raise a good point. I agree with you that it's the responsibility of an external tool. I've tried to implement this, but it never quite works out right and is very difficult. I think I'll recommend your suggestion if other issues are raised concerning this same topic and close this issue. Thank you for your input :)

I suggest using some external command or script. You could create a way to execute this command/script before and after generating the executable. But only on a copy of the project.
I for example do a copy of the entire project to a temporary folder, run a script to do some cleaning, and then I use this folder to generate the executable.

@williamd1k0 I totally missed this post. That's a good way of doing things, and it makes sense to only do it on a copy of the folder in order not to mangle the project. I'll keep that in mind and maybe implement it later if I have some spare time.


Dataset enhancements

failure information is provided in different formats.

List of failures
Indication of the begging of the measurement
Just a Time in production field.

It would be handy to have these methods for splitting into cycles, computing the RUL column based on a timestamp column of the dataset or just a cycle column.
Also it would be handy to incorporate into the dataset classes ways of automatically handling different devices based on some identifier column.

Closed by #1


Angular 5 :(

Contributions would be highly appreciated, thanks in advance!
What to say? It throws errors when compiling and the tests don't run when installing angular 5...
At the moment I'm not developing a frontend and I'm not up to date what has changed... I don't know if angular 5 has any advantages - it's just breaking my code.

small update: it's not throwing when compiling. it's throwing in browser because of the pipe resolver is different now...

next error:
ERROR Error: StaticInjectorError[Injector]:
  StaticInjectorError[Injector]:
    NullInjectorError: No provider for Injector!
    at _NullInjector.get (webpack-internal:///../../../core/esm5/core.js:1118)
    at resolveToken (webpack-internal:///../../../core/esm5/core.js:1406)
    at tryResolveToken (webpack-internal:///../../../core/esm5/core.js:1348)
    at StaticInjector.get (webpack-internal:///../../../core/esm5/core.js:1219)
    at resolveToken (webpack-internal:///../../../core/esm5/core.js:1406)
    at tryResolveToken (webpack-internal:///../../../core/esm5/core.js:1348)
    at StaticInjector.get (webpack-internal:///../../../core/esm5/core.js:1219)
    at resolveNgModuleDep (webpack-internal:///../../../core/esm5/core.js:10780)
    at _createClass (webpack-internal:///../../../core/esm5/core.js:10821)
    at _createProviderInstance$1 (webpack-internal:///../../../core/esm5/core.js:10791)
View_AppComponent_Host_0 @ ng:///AppModule/AppComponent_Host.ngfactory.js:5

puh :sweat_smile: thats a bug of linking the project.. the node_modules exists and is used from webpack then the Injector exists two times and the Injector only knows one of them...

@mouragz can you please try<EMAIL_ADDRESS>?

on angular-translator-demo it works: https://angular-translator-demo.my-first-domain.de/

@tflori @BorntraegerMarc thank you so much it's working fine now 💯


Hyperlinks may have duplicate values

This can unnecessarily increase the file size.

It seems to be a misunderstanding on my part.


The microspeech model expects 1.5s but our input files are only 1s long

The microspeech Runefile expects to receive 24,000 samples of audio at 16kHz, but yes_01d22d03_nohash_0.wav and friends are only 16,000 samples long.
This isn't a problem when you compile the Rune in release mode (rune build Runefile), but when compiled in debug mode (rune build Runefile --debug) we trigger this assertion.
[2021-03-25T18:30:19.671Z INFO ] panicked at 'assertion failed: `(left == right)`
    left: `32000`,
   right: `48000`', /home/michael/Documents/hotg-ai/rune/runic-types/src/wasm32/mod.rs:92:9
Error: Call failed

Caused by:
    0: Unable to call the _call function
    1: RuntimeError: unreachable
           at core::core_arch::wasm32::unreachable::hb8a7ba5af00cd3dd (<module>[1099]:0x3d931)
           at rust_begin_unwind (<module>[1051]:0x3c101)
           at core::panicking::panic_fmt::hfa15f5472ef5e557 (<module>[1428]:0x4aed4)
           at core::panicking::assert_failed_inner::h1ff1547b4e20ab23 (<module>[1442]:0x4baf6)
           at core::panicking::assert_failed::h4a336faee37010c7 (<module>[968]:0x3786c)
           at runic_types::wasm32::copy_capability_data_to_buffer::h3df68d48e80f298c (<module>[225]:0x97da)
           at <runic_types::wasm32::sound::Sound<_> as runic_types::pipelines::Source>::generate::h4d22008f54108f0a (<module>[125]:0x578a)
           at microspeech::_manifest::{{closure}}::h31e7eddd059d1b5c (<module>[107]:0x4300)
           at <alloc::boxed::Box<F,A> as core::ops::function::FnMut<Args>>::call_mut::he6db486207a4a9a2 (<module>[55]:0x26c0)
           at _call (<module>[127]:0x5e9a)
    2: unreachable

However, if you update the capability and proc blocks in the Runefile to work with a I16[16000] (so our debug assertion is happy), the model now thinks our "yes" example is "silence" and tests start failing. I'm guessing all those trailing zeroes make a difference once they go through the FFT.
@meelislootus do you have any idea what's going on here?

@meelislootus fixed this in #152.


Refactor Ruby code to reflect Style Guide; Add Rspec test

@creativisionist This is a great job! I liked your thinking about including tests even though it wasn't required. Take a look at my comments and submit a second revision. There shouldn't be too many changes, but do note my comments on access levels (private methods and attrs).


For the wasme build command, support http_proxy, https_proxy and no_proxy environment vars

Hi,
The "wasme build" command will fail if these http_proxy, https_proxy and no_proxy environment variables are not empty. It is recommended that this command support them. That's, the build command looks as follows:
docker run --rm -v /data/home/jiaweixu/tmp/new-filter:/src/workspace -v /tmp:/build_output -w /src/workspace -e BUILD_BASE=. -e BAZEL_OUTPUT=filter.wasm -e TARGET=:filter.wasm -e BUILD_TOOL=bazel -e http_proxy=XXX -e https_proxy=YYY -e no_proxy=ZZZ quay.io/solo-io/ee-builder:0.0.20

Refer to the runBazelBuild function in https://github.com/solo-io/wasme/blob/master/pkg/cmd/build/cpp.go.

the similar problem for building filters in AssemblyScript.


feat: speed up tipset validation

Summary of changes
Changes introduced in this pull request:

Speed up tipset validation by running validations in parallel.

Numbers to be added

branch
validation time(300 epochs)
ratio

main
2011s
100%

pr

Reference issue to close (if applicable)

Closes
Other information and links

Closing as we don't want to parallelize this


Report noid in indexing error

Makes resources that failed to reindex easier to find.
fixes #710

Coverage remained the same at 100.0% when pulling 0990ced4b1966432d147106f032f2781d37570d4 on 710-noid-in-error into 4aba5d15df698492c7c65ff417c7e0366ed298fa on master.


Search library also in split APKs.

The library may be placed in a split APK. This happens for example when using
the dynamic delivery.
Fixes #44.

Note that appInfo.splitSourceDirs may be null on some devices, the documentation does not mention it.

Will this be merged soon?

any update?

The travis build failed because of ">" character inside comment. The comment was there already.

@michalsrb thanks for the PR. Sorry I just saw this. We will look at this by the end of this week or beginning of next one the latest.

@emarc-m Did you have a chance to look at this?

could you please fix the existing tests and add new tests for the new behavior.

The ApkLibraryInstallerTest was failing because apparently the android.util.Pair intentionally behaves badly in unit tests. (stackoverflow)
So I replaced it with custom private class and the test passes now.

is there documentation that we can link in here the describes the designed behavior of multi APK apps?

Here is documentation that describes a bit how Google Play splits the APKs:
https://developer.android.com/guide/app-bundle/configure
I don't know if there is something better.

How does it look in production for you?

It works well. I am getting small amount of failures, but I have been getting those before as well. I suspect those may be people who install APKs from 3rd party sources with wrong ABI.

Does anyone know how long it might take until this PR will be merged?

@michalsrb your PR is so waited by lots of developers
Could you please fix these 2 tiny tips from @emarc-m so he can accept the PR ?

I made the small changes. I don't know how to mock the Build.VERSION.SDK_INT to make the unit test.

I merged this PR and I'm cutting a new version.
I suggest for the unit testing portion that we create something like an SDK manager class that has a meshing like minSdkVersion() that returns Build.VERSION.SDK_INT. Then we can mock the entire class for testing purpose.
Unit tests should be in a separate PR to this.

Awesome, thanks! So is there any nightly builds of Relinker or when should we expect a new release?


Adds settings for createMedium processing

Being able to change the medium sizes would be great. This way we can just add the settings in the database and if not it falls back to the old values.
I don't yet know where to change the size detection in the frontend though.

wrong/old/outdated Lychee repo nice ez gg wp


User-specified shards-only clusters shard.internal_replication is true

Applying following manifest
apiVersion: "clickhouse.altinity.com/v1"
kind: "ClickHouseInstallation"
metadata:
  name: uat
spec:
  configuration:
    clusters:
      - name: cdp
        templates:
          podTemplate: clickhouse:20.4
        layout:
          shardsCount: 7
    settings:
      logger/level: debug
      query_log/flush_interval_milliseconds: 30000
      timezone: Asia/Shanghai
      max_table_size_to_drop: 0
      max_partition_size_to_drop: 0
    profiles:
      default/max_query_size:<PHONE_NUMBER>
      default/distributed_aggregation_memory_efficient: 1
      default/max_bytes_before_external_group_by:<PHONE_NUMBER>
      default/max_memory_usage:<PHONE_NUMBER>0
      default/max_memory_usage_for_all_queries:<PHONE_NUMBER>0
      default/joined_subquery_requires_alias: 0
      default/log_queries: 1
      default/log_query_threads: 0
    users:
      default/networks/host_regexp: '(chi-uat-[^.]+\d+-\d+|clickhouse\-uat|ck\-nodeport.*)\.uat\.svc\.cluster\.local$'
      cdp_user/networks/ip:
        - "::/0"
    zookeeper:
      nodes:
        - host: zookeeper-0.zookeepers
          port: 2181
  templates:
    podTemplates:
      - name: clickhouse:20.4
        spec:
          containers:
            - name: clickhouse
              image: yandex/clickhouse-server:20.4
              volumeMounts:
                - name: data-storage-vc-template
                  mountPath: /var/lib/clickhouse
                - name: log-storage-vc-template
                  mountPath: /var/log/clickhouse-server
              resources:
                requests:
                  memory: 28Gi
                  cpu: 12
                limits:
                  memory: 28Gi
                  cpu: 15
          nodeSelector:
            env: stg
          tolerations:
            - effect: NoSchedule
              key: stg
    volumeClaimTemplates:
      - name: data-storage-vc-template
        reclaimPolicy: Retain
        spec:
          storageClassName: csi-rbd-sc
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 2000Gi
      - name: log-storage-vc-template
        reclaimPolicy: Retain
        spec:
          storageClassName: csi-rbd-sc
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 10Gi

generates /etc/clickhouse-server/config.d/remote_servers.xml:
<yandex>
    <remote_servers>
        <!--  Autogenerated clusters -->
        <all-replicated>
            <shard>
                <internal_replication>true</internal_replication>
                <replica>
                    <host>chi-uat-cdp-0-0</host>
                    <port>9000</port>
                </replica>
                <replica>
                    <host>chi-uat-cdp-1-0</host>
                    <port>9000</port>
                </replica>
                <replica>
                    <host>chi-uat-cdp-2-0</host>
                    <port>9000</port>
                </replica>
                <replica>
                    <host>chi-uat-cdp-3-0</host>
                    <port>9000</port>
                </replica>
                <replica>
                    <host>chi-uat-cdp-4-0</host>
                    <port>9000</port>
                </replica>
                <replica>
                    <host>chi-uat-cdp-5-0</host>
                    <port>9000</port>
                </replica>
                <replica>
                    <host>chi-uat-cdp-6-0</host>
                    <port>9000</port>
                </replica>
            </shard>
        </all-replicated>
        <all-sharded>
            <shard>
                <internal_replication>false</internal_replication>
                <replica>
                    <host>chi-uat-cdp-0-0</host>
                    <port>9000</port>
                </replica>
            </shard>
            <shard>
                <internal_replication>false</internal_replication>
                <replica>
                    <host>chi-uat-cdp-1-0</host>
                    <port>9000</port>
                </replica>
            </shard>
            <shard>
                <internal_replication>false</internal_replication>
                <replica>
                    <host>chi-uat-cdp-2-0</host>
                    <port>9000</port>
                </replica>
            </shard>
            <shard>
                <internal_replication>false</internal_replication>
                <replica>
                    <host>chi-uat-cdp-3-0</host>
                    <port>9000</port>
                </replica>
            </shard>
            <shard>
                <internal_replication>false</internal_replication>
                <replica>
                    <host>chi-uat-cdp-4-0</host>
                    <port>9000</port>
                </replica>
            </shard>
            <shard>
                <internal_replication>false</internal_replication>
                <replica>
                    <host>chi-uat-cdp-5-0</host>
                    <port>9000</port>
                </replica>
            </shard>
            <shard>
                <internal_replication>false</internal_replication>
                <replica>
                    <host>chi-uat-cdp-6-0</host>
                    <port>9000</port>
                </replica>
            </shard>
        </all-sharded>
    </remote_servers>
</yandex>

The query
alter table cdp_mop_user_data on cluster cdp DROP PARTITION ID '20200604'

gets error:
DB::Exception: Received from <IP_ADDRESS>:30900. DB::Exception: There was an error on [chi-uat-cdp-1-0:9000]: An error occurred before execution: Code: 371, e.displayText() = DB::Exception: Table `cdp_mop_user_data` isn't replicated, but shard #2 is replicated according to its cluster definition (version <IP_ADDRESS> (official build)).

I expect user-specified shards-only clusters shard.internal_replication be false.
operator version: 0.9.9

This is a good point. internal_replication should be false, if there is a single replica. We will fix that.

As a workaround, you can use 'internalReplication' shard property, but that would require to define all shards separately. We will move it to the cluster level as well.

fix merged into
https://github.com/Altinity/clickhouse-operator/tree/0.10.0


Documentation: missing the type of Parser.parse() return value ( Synchronous API )

I cannot find anywhere in the documentation what type has the returned value from csv.parse().

The parse method return plain text.
It returns the CSV resulting from your json.
You need to elaborate a bit more on your question so I can try to help 🙂


Improved type-hints for stage and source decorators

Description

Improved type hints for both the input parameters and the return types

Closes  #1812
By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

/merge


How to set the viewportSize when using Slimer.js?

I got this working perfectly , but i need to get a screenshot of higher resolution.
i tried this
var driver = require('node-phantom-simple');
driver.create({ path: 'node_modules/slimerjs/src/slimerjs' }, function (err, browser) {
  browser.viewportSize = { width:1920, height:1080 }; // didn't work
  return browser.createPage(function (err, page) {
    page.viewportSize = { width:1920, height:1080 }; // also didn't work

    // render page as screenshot here

    browser.exit();
  })
});

please help.

Try the following:
var driver = require('node-phantom-simple');
driver.create({ path: 'node_modules/slimerjs/src/slimerjs' }, function (err, browser) {
  return browser.createPage(function (err, page) {
    page.set('viewportSize', { width:1920, height:1080 }, function(err) {
      // Viewport has been set.
    });

    // render page as screenshot here

    browser.exit();
  });
});

@Reewr  Thanks buddy, that did it :+1:


Support module files with multiple H2 for grouping cmdlets

Summary of the new feature / enhancement
Some modules support multiple feature areas. The module markdown file can group the cmdlets by feature area where each feature area is represented by an H2 with H3 entries for each cmdlet in that group. The H2 may have an optional markdown content before the first H3.
Proposed technical implementation details (optional)
Example markdown:
## Feature 1 cmdlets

Optional collection of paragraphs (or other non-Header markdown).

### [cmdlet1-name](cmdlet1-name.md)

Synopsis of cmdlet1-name

### [cmdlet2-name](cmdlet2-name.md)

Synopsis of cmdlet2-name

## Feature 2 cmdlets

### [cmdlet3-name](cmdlet3-name.md)

Synopsis of cmdlet3-name
...

Requirements

Need to be able to import module markdown in this format
Need to be able to re-export the imported module markdown (e.g. for conversion from v1 to v2 format)
New-MarkdownCommandHelp -WithModulePage should output a flat module markdown file

Creating or updating an existing module markdown file with groupings is out of scope for this release.

Need to be able to convert a module markdown file that has multiple H2 into Yaml

Fixed in https://github.com/PowerShell/platyPS/commit/27d5ffe4090f146b64c7d91453d6683c68c8ee53


[Feature]: Suite test for the project.

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?
None
Problem Description
We do not have test cases for the key functions. And I am working on writing the test cases for the k8sgpt-operator project now.
Solution Description
I am happy to add the suit test cases in this repo and keep the same style with ginkgo/v2 and gomega.
The suit-test solution should be simple and useful, and make sure it has a high code coverage (60%).
Furthermore, we can add Coverage to the repo, and make sure every PR has a code coverage result.
Benefits
This is useful for the code quality and it also makes sure the code coverage in a high level.
Potential Drawbacks
No response
Additional Information
By the way, I cannot join k8sGPT Slack Channel. So, this was not discussed.

What's the issue you're having with slack @Aisuko ?

Maybe I need to get an invitation from the administrator?


Allow custom headers to be set on query for the echo server replies

Fixes #191
You can specify multiple headers to be set/returned by the echo server
(including multiple for the same header key)

Example:
$ curl -v "http://localhost:8080/?header=foo:bar1&header=foo:bar2&header=blah:xYz"
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8080 (#0)
> GET /?header=foo:bar1&header=foo:bar2&header=blah:xYz HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Blah: xYz
< Foo: bar1
< Foo: bar2
< Date: Tue, 27 Mar 2018 00:19:26 GMT
< Content-Length: 0
<
* Connection #0 to host localhost left intact

I am wondering if I should make those propabilities too ? (ie Foo:Bar:2 would put Foo: Bar in 2% of replies - there would be an issue for multi header on whether the dice applies independently for each or not)

I am wondering if I should make those propabilities too ? (ie Foo:Bar:2 would put Foo: Bar in 2% of replies

I think that is a cool sub feature, but is not required to address this issue. I would open a new issue for the sub feature and see if anyone weighs in and/or contributes code.

/lgtm

will refactor in #224 though I am a bit concerned about potential break in api


Are the latest versions weave-2.8.8 tested in ubuntu 22.04 ?

Hi,
We upgraded to ubuntu 22 and with weave 2.8.1 all connections come up only in sleeve mode .
Is latest version of weave 2.8.8 tested with ubuntu 22.04 ?
thanks
Megarajan

No, but it has been tested with Debian 12 'bookworm', which is roughly what Ubuntu 22.04 is based on. Did you try adjusting the MTU like I suggested in the other issue?

yes, thanks for confirming . I tried adjusting the weave mtu, didnt seem to help, but upgrading to the next version we dont see the same issue.
We can close this issue.


Handshake Reply Failed

I tried to use multiple (new Postmate) instances but sometimes I'm getting a Handshake Reply Failed error message.
Does postmate supports multiple instances / multiple iframes?
Is there any way to have just one Postmate (parent instance) with multiple child instances?

I am getting the exact same issue. I am starting multiple child iframes with the same URL and occasionally I am getting this error from the child.

@HyperCharlie, I have moved to another solution: https://github.com/Grabber/framelet


Date match bug

See https://github.com/jamesagnew/hapi-fhir/tree/date-match-bug for a failing test that demonstrates the error.
The source of the bug is the timezone shift calculation in DateRangeParam.getUpperBoundAsInstant()
Recommended fix:
Add two new columns to ResourceIndexedSearchParamDate that store the low and high date (with no time) as an integer in the format 20190921.  When the search is for a date without a time, use this column for the search instead of the date column.

Just encountered this as well just now.
I do not know why this was implemented in this way. I agree that the date range should account for time, but rather then trying to play with timezone shifts, it's better to just unwrap the date into low-high via appending 00:00:00.0000000 and 23:59:59.9999999 accordingly.

@jamesagnew  I'm willing to submit a PR if you think this is valid.

Wouldn't that approach suffer from the same issue? You'd have to pick a timezone to apply that 00:00 and 23:59 to..

I would use the same time zone that is used to compute the date of creation of the resource. That way what we display on the response is in sync with the query.
Without knowing the users timezone we will net be able to determine the correct time that they would need, but at least we would be consistent with what is in the creation date.
Right now when I request resources for 21-02-2020, the current implementation unwraps that into 20-02-2020 12:30:00 - 21-02-2020 13:30:00 for the server and client in the same timezone.
I would propose to unwrap it to 21-02-2020 00:00:00 - 21-02-2020 23:59:59 using the server timezone, if no timezone is provided.

You mean like you'd just use the underlying OS timezone and just choose a
24-hour period that aligns with that timezone?
I'm not 100% sure but I feel like that's already what we're doing....
On Fri, Feb 21, 2020 at 12:28 PM Roman Doboni<EMAIL_ADDRESS>wrote:

I would use the same time zone that is used to compute the date of
creation of the resource. That way what we display on the response is in
sync with the query.
Without knowing the users timezone we will net be able to determine the
correct time that they would need, but at least we would be consistent with
what is in the creation date.
Right now when I request resources for 21-02-2020, the current
implementation unwraps that into 20-02-2020 12:30:00 - 21-02-2020 13:30:00
for the server and client in the same timezone.
I would propose to unwrap it to 21-02-2020 00:00:00 - 21-02-2020 23:59:59
using the server timezone, if no timezone is provided.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamesagnew/hapi-fhir/issues/1499?email_source=notifications&email_token=AA2N7HMZR3KHCMSTAXDQS3DREAFMNA5CNFSM4IY57BCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMTOWKA#issuecomment-589753128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2N7HPPBATPA7CTOWBTKA3REAFMNANCNFSM4IY57BCA
.

We are doing that, true, but in a weird way. What we do is: Take a date, and make it a time by just taking the midnight. Then to get the time range we create two times based on that, one is -12 hours, other is +12 hours. The problem is that if the resource was created after midday on that date, it will not be included in the search.
Example:

We have a resource a resource that was created at 21-02-2020 17:00:00
A search is triggered with the date param set to 21-02-2020
21-02-2020 is unwrapped to 21-02-2020 00:00:00
21-02-2020 00:00:00 -> from  20-02-2020 12:30:00  to 21-02-2020 13:30:00
The resource from 1 will not be included.


Keaton enable target table type change 3

Associated Bodo testing PR: https://github.com/Bodo-inc/Bodo/pull/4480

This PR had its destination updated because merged the tmp branch into 1.30.


[Proposal] Non-exhaustive enums

As discussed in Enums and Source Compatibility, with additional orphaned thread. Initial implementation at apple/swift#11961. Thanks to everyone who gave pre-review feedback!

LGTM!

:+1: :-1:

Exhaustive enums is one of my favorite features of Swift and I don't think it would be a good idea to allow anything but that. From the proposal introduction:

Currently, adding a new case to an enum is a source-breaking change, which is very inconvenient for library authors.

Adding a case should be a source-breaking change IMO since it forces consumers to consider the new behavior. If DateComponentsFormatter.UnitsStyle changes and I'm programming exhaustively, I want a compile error for each instance of code to check. If I only care about a specific case then I would have added a default case myself.

This proposal aims to distinguish between enums that are exhaustive (meaning they will never get any new cases)

I don't agree with this definition. Exhaustive means that at the time of me writing some code, there are no additional cases to check (ie a finite number of cases). This has nothing to do with the number of cases growing in the future, via an update to the library/API.


false positive bug

Hi there! I'm still so new at Flow that I honestly have no idea how to describe this bug, but here's a reproduction
/* @flow */

type Element = {};
type Document = {getElementById(string): Element | null};

declare var document: Document;

type InitOptions = {
  messagesNode?: Element | void
}

function init({
  messagesNode = document.getElementById('react-messages')
}: InitOptions) {
  // blah blah
  return messagesNode
}

function workingInit(options: InitOptions) {
  const {
    messagesNode = document.getElementById('react-messages')
  } = options
  // blah blah
  return messagesNode
}

For some reason, moving the destructuring from the param list to the function body works. I'm pretty sure that this is a bug.

Ah, looks like this might be related: https://github.com/facebook/flow/issues/183
Feel free to close if you'd like

This is definitely a complete duplicate of #183 so I think you should close this issue and we'll focus our efforts on the original one.


updated build config, successful build, but new artifacts not in domain

Hi. I recently updated my build config to use Gatsby + Cypress testing, but now am unable to see the uploaded artifacts in my app domain. It seems as if none of the build artifacts are actually being uploaded in the deployment phase, yet in the logs it says they successfully were.
Build settings:
version: 0.1
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - yarn run build
  artifacts:
    baseDirectory: public
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
test:
  phases:
    preTest:
      commands:
        - yarn install
        - yarn add mocha mochawesome mochawesome-merge mochawesome-report-generator
    test:
      commands:
        - npx start-test 'yarn start' 8000 'npx cypress run --reporter mochawesome --reporter-options "reportDir=cypress/report/mochawesome-report,overwrite=false,html=false,json=true,timestamp=mmddyyyy_HHMMss"'
    postTest:
      commands:
        - npx mochawesome-merge cypress/report/mochawesome-report/mochawesome*.json > cypress/report/mochawesome.json
  artifacts:
    baseDirectory: cypress
    configFilePath: '**/mochawesome.json'
    files:
      - '**/*.png'
      - '**/*.mp4'

Log is attached
log (11).txt

After further researching this, It seems the branch preview link within the AWS console is not correctly pointing to the app correctly.
For example, If I click on the link within the console I get a blank page, but if I go to "https://master.appnumber.amplifyapp.com/page-2" it correctly appears.
I am able to go back to "https://master.appnumber.amplifyapp.com/" from this page and it correctly appears but it does not work when I click on the aws console link. The page does not also appear when I manually enter "https://master.appnumber.amplifyapp.com/" into the browser. Only from "https://master.appnumber.amplifyapp.com/page-2" will it show.

@zoosissoos
Can you provide us the AppID and region you are hosting your Amplify app in?

Not to be rude, but is there a way I can privately send you these things?

No worries, please use<EMAIL_ADDRESS>to send us the information.

Sent the information to the email provided.

Was there ever a resolution to this? I seem to be running into a similar issue but can't seem to break the cache in any way.

@hsspain Yeah, running into the same @liamegan. Is this a pervasive issue?

@Gowiem @liamegan Can you provide your region and App ID? We will take a look.

Sent.

This issue has been resolved and a redeployment of any affected apps should clear up the improper routing.  Please let us know if there are any further issues.

I was able to find a resolution to this through AWS support:
====================================================================
The issue seems to be that running cypress overwrites the production build. In the yml build config, you must make a new directory:
Hi,
I really appreciate your patience.
After deep diving the weird behavior of current build and test with Cypress, I was able to identity the root cause and resolve it.
Below is what happened from your previous build yaml file:

During Build Phase,  'yarn run build'  will build and place production code in 'public' folder

Later on, from the  'Pretest' phase, when following command is executed, it will actual run  'gatsby develop' as configured from your 'package.json' and eventually override 'public' folder. As a result, the final build artifact for your website was modified during Cypress test which cause  the blank home page

yarn start & npx wait-on http://<IP_ADDRESS>:8000

In order to resolve the issue, you can rename the 'build' folder to other name such as 'dist' and set this 'dist' folder for build artifact as below. By doing so, Cypress test will not override the production build folder (dist folder)
1.Changing name of public folder
build:
commands:
- gatsby clean
- yarn run build
- mv public dist # changing name of public folder

Changing build folder to 'dist' instead of 'public'

artifacts:
baseDirectory: dist #New folder to avoid being overridden by cypress
files:
- '**/*'
Below is my build yaml in my replication environment which gets my app built successfully with proper output from homepage.
version: 0.1
backend:
phases:
build:
commands:
- '# Execute Amplify CLI with the helper script'
- envCache --set stackInfo ""
frontend:
phases:
preBuild:
commands:
- yarn install
build:
commands:
- gatsby clean
- yarn run build
- mv public dist # changing name
artifacts:
baseDirectory: dist
files:
- '/*'
cache:
paths:
- node_modules//*
test:
phases:
preTest:
commands:
- yarn install
- yarn add wait-on
- yarn add mocha mochawesome mochawesome-merge mochawesome-report-generator
- "yarn start & npx wait-on http://<IP_ADDRESS>:8000 "
test:
commands:
- 'npx cypress run --reporter mochawesome --reporter-options "reportDir=cypress/report/mochawesome-report,overwrite=false,html=false,json=true,timestamp=mmddyyyy_HHMMss"'
postTest:
commands:
- npx mochawesome-merge@4 cypress/report/mochawesome-report/.json > cypress/report/mochawesome.json
artifacts:
baseDirectory: cypress
configFilePath: "/mochawesome.json"
files:
- "/.png"
- "**/*.mp4"

So I was able to find a resolution to this through AWS support. It seems that running cypress was overwriting the folder containing the artifacts needed, so that the development was overwriting production. I was provided with a yml that fixed my problem.
version: 0.1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - envCache --set stackInfo ""
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - gatsby clean
        - yarn run build
        - mv public dist # changing name
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
test:
  phases:
    preTest:
      commands:
        - yarn install
        - yarn add wait-on
        - yarn add mocha mochawesome mochawesome-merge mochawesome-report-generator
        - "yarn start & npx wait-on http://<IP_ADDRESS>:8000 "
    test:
      commands:
        - 'npx cypress run --reporter mochawesome --reporter-options "reportDir=cypress/report/mochawesome-report,overwrite=false,html=false,json=true,timestamp=mmddyyyy_HHMMss"'
    postTest:
      commands:
        - npx mochawesome-merge@4 cypress/report/mochawesome-report/*.json > cypress/report/mochawesome.json
  artifacts:
    baseDirectory: cypress
    configFilePath: "**/mochawesome.json"
    files:
        - "**/*.png"
        - "**/*.mp4"


Cypress/E2E: Fix apiAdminLogin return object

Summary

Fixed apiAdminLogin return per https://github.com/mattermost/mattermost-webapp/pull/5945#pullrequestreview-452374708
Applied similar changes to channel_members_spec

Ticket Link
None - master only

I thought the other changes were already done from the other PR. Why is it still here?

@saturninoabril The original was for team_members_spec. The new one is for channel_members_spec since I had to modify the apiAdminLogin on both, I cleaned up channel_members_spec as well

@saturninoabril Or is there another PR that you're referring to?


App crash on entering test amount on Test transaction page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any workspace
Connect bank manually
Select “Manually enter account details” and enter Routing number 011401533 and Account number<PHONE_NUMBER>331111
Company Info - enter random info but complete all fields. You will fail once and get asked to double check information. Select “Save & Continue” again
Personal Info - use any test data. For last 4 SSN use 3333.
Beneficial Owners:

Toggle terms and conditions
Toggle confirmation that the information provided is true and accurate

Enter amount in test transaction page

Expected Result:
App doesn’t crash
Actual Result:
App crash with console error - amount.trim is not a function at ValidationStep.filterInput
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.2.65-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/216878275-e6fd2efd-03fb-4186-97ae-5790657c0f57.mov
https://user-images.githubusercontent.com/43996225/216878284-6773ab94-59de-4413-bd4e-38d606b545fd.mp4
Expensify/Expensify Issue URL:
Issue reported by: @rushatgabhane
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675457749071149
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Hm, looks like amount might not always be a String, doing a toString() before trim() should do the trick!

PR linked, working on tests

PR merged!

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.65-2 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/14850

If no regressions arise, payment will be issued on 2023-02-13. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@robertjchen] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@robertjchen] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@robertjchen] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@robertjchen] Propose regression test steps to ensure the same bug will not reach production again.
[ ] [@mateocole] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.66-0 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/14850

If no regressions arise, payment will be issued on 2023-02-14. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@robertjchen] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@robertjchen] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@robertjchen] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@robertjchen] Propose regression test steps to ensure the same bug will not reach production again.
[ ] [@mateocole] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Internal fix, removed above labels ^

re: BugZero checklist
This code existed 20 months ago in https://github.com/Expensify/App/pull/3587 so it probably wasn't the cause, the next place to look at would be TextInput, BaseTextInput, and Form (which calls the validation) but nothing really stands out other than some recent styling changes. 🤔
The base react-native component returns a pure string, so somewhere along the line some type inference happens and we get a numeric type.
Either way, we'll probably have to do some git bisects to find the cause- given the limited scope, I don't think we should sink too much time into it beyond this. We can create a dedicated issue to hunt this down if it happens again- going to close this out for now.

Ah, I forgot- re-opened!

here is a job to apply for https://www.upwork.com/jobs/~018c21815161da68ce

sry forgot to tag you @rushatgabhane

Looks like this is all set!

@rushatgabhane all paid, apologies for the confusion i sent you a separate offer and withdrew it, but paid the contract in the link above!


4 | Median of Two Sorted Arrays | Java

4 | Median of Two Sorted Arrays | Java -
What will change -
Add Java solution to the LeetCode problem: 4. Median of Two Sorted Arrays
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[ ] Improving Code
[ ] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[ ] Python
[ ] C++
[x] Java

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/Ftbj4a
Happy Coding,

I can work on this issue. @dsibilio would it be possible to assign this to me?

This issue should already be solved by PR #30
You can go ahead and create clones of this issue for a different programming language 👍

Hey @dsibilio, I'd love to help.
Can you please assign this issue to me?
Thanks

[x] Assigning to @dsibilio


Study does not render - NSCLC-Radiomics / LUNG1-001

Bug Report
Describe the Bug
When I open a non-empty study, nothing shows up in the left panel, while there are no errors in the console.
https://idc-sandbox-000.firebaseapp.com/projects/idc-dev-etl/locations/us-central1/datasets/idc-tcia/dicomStores/idc-tcia/study/<IP_ADDRESS>.4.1.40744.29.239341353911714368772597187099978969331

If I click on "Segmentations", I get a cryptic error message:

What steps can we follow to reproduce the bug?
open https://idc-sandbox-000.firebaseapp.com/projects/idc-dev-etl/locations/us-central1/datasets/idc-tcia/dicomStores/idc-tcia/study/<IP_ADDRESS>.4.1.40744.29.239341353911714368772597187099978969331 and do the steps described above.

I don't have access to the idc-dev-etl project - is that one that you are able to share?

Also do you know anything about the study?  Does it load in Slicer?

The study should be good - it is from Hugo, Dennis already used the version hosted by google in his use case, SEGs were generated with dcmqi. But I did not download the study or investigate in detail.
I asked Bill to add you to that project.

If I click 'd', I get the following in the console:

@pieper what is again the command i need to type in the console to download a study? I am again having troubles finding the ticket or PR where this was mentioned. Can we add this to the documentation somewhere?

Found the instructions
ohif.app.commandsManager.runCommand("downloadAndZip", {listOfUIDs: [window.location.href.split("/").pop()]})

So the underlying problem seems to be that the study does not contain the image series. Will investigate that. I think it would be helpful to have a user-readable message about this.

It appears that TCIA assigned SEG and RTSTRUCT to a study different from where CT is.
I submitted the issue below to the TCIA helpdesk.

there is an issue with at least some of the UIDs for the
NSCLC-Radiomics collection.
Subject LUNG1-001 has 3 series: CT, RTSTRUCT and SEG.
For whatever reason, CT is assigned to a different study than RTSTRUCT
and SEG, but the suffix of the StudyInstanceUID is the same:
CT is in study <IP_ADDRESS>.4.1.327<IP_ADDRESS>341353911714368772597187099978969331
RTSTRUCT and SEG are in
<IP_ADDRESS>.4.1.40744.29.239341353911714368772597187099978969331.
This is not just an inconvenience and bad practice, but also it
appears that the StudyInstanceUID is inconsistent from how series were
organized for this collection in the past.
I checked the previous version of the collection, which is still
available from the Google copy, and in that collection RTSTRUCT is in
the same study as the CT image.
Can you explain what is happening? Is it intentional that
StudyInstanceUID was changed, and RTSTRUCT and SEG are assigned to a
study different from the CT series?
For your convenience, here's a zip file for LUNG1-001, both the
current and previous version:
https://app.box.com/s/3v73ot5pq7kza140yoi10qhqia4j7pqt

@pieper we now have OHIF 4.2.3 in the IDC webapp, but the command to download the study is not working:

Should something be done by @G-White-ISB to enable it?

I don't think there's any configuration required - @dannyrb ?
Does the webapp's ohif include this commit https://github.com/OHIF/Viewers/commit/63fd65690cba450721870a6222e0fb3ad71bb291

Actually it looks like the ohif.app.commandsManager object is there, but it's not finding the command, so there must be something else going on, but I'm not sure about that context stuff.

So the underlying problem seems to be that the study does not contain the image series. Will investigate that. I think it would be helpful to have a user-readable message about this.

Yeah this looks like the issue. We should have a notification pop up and a clean failure in the side panel when no source data is present.
@rodrigolabs you can test this locally by adding just a SEG from TCIA to a study in a local PACs.
We should use the UINotificationService for this, similar to the out-of-plane segmentation resolved here: https://github.com/OHIF/Viewers/pull/1708.

Response from TCIA:

Tracy Nolan commented:
Hi Andrey,
I have a response for you from the team that worked with the PI about this:
Hello,
The reason the Study UIDs for the RTSTRUCTs and SEGs are different from the CTs is because Leonard Wee created the SEGs and RTSTRUCTs from the original data rather than pulling it from TCIA.
Leonard's data did not have hashed UIDs for the CTs.
When Leonard created the RTSTRUCTs and SEGs they were based on the original UID values (not TCIA hashed values).
This issue was discussed. Bill Bennett, and Kirk Smith agreed, that hashing the UIDs for the SEGs and RTSTRUCTs would likely break linkages. We consulted with Larry and he stated that this was not an issue with the DICOM standard (different study UIDs).
We would have preferred to have the RTSTRUCTs and SEGs created from the TCIA data but it was not and so we processed the data received.
Please let us know further questions, comments, or concerns you have for this unusual  collection update.
-tracy

I think it would be helpful to have a user-readable message about this.

@fedorov Just clarifying: is a user notification when the source series is missing good to work on for IDC priority?
Thanks

Yes, I think so. This issue already has "priority" assigned. Or are you saying that's a separate issue?

Thanks for the quick reply, I just wanted to double check, as this initially started as a conversation about a particular study not rendering, which has been largely resolved.
I'll close this ticket and open a new ticket with just the isolated UI issue, and add it as priority.

Feel free to reopen this issue if any discussion needs to continue about hosting this particular study on the IDC platform.


Deserialization of seperated sequences

In some formats, it's common for a sequence to be interrupted. Take for example the following XML:
<interface>
    <request>sync</request>
    <request>get_registry</request>
    <event>error</event>
    <enum name="error">
        <entry name="invalid_object"/>
        <entry name="invalid_method"/>
        <entry name="no_memory"/>
    </enum>
    <event>delete_id</event>
</interface>

The structure that most closely resembles this is:
#[derive(Debug, Deserialize)]
struct Interface {
    #[serde(rename = "request")] request: Vec<Request>,
    #[serde(rename = "event")] events: Vec<Event>,
    #[serde(rename = "enum")] enums: Vec<Enum>,
}

This is impossible for serde to parse though. Serde expects all array elements to be given in a sequence. (After all, Vistitor::visit_seq expects an iterator.)
Is there a way around this? Will this be fixed in serde or is it considered to be an edge-case that doesn't need to be supported?

I determined the error occurs here. There should be an option for types like Vec to allow taking additional values.
What would be the best way to design this? Maybe add a new function to Deserialize?
fn combine(self, new_values: Self) -> Self;

Whoops, pressed the wrong button there.

I believe this is already supported by Serde. The toml crate has no trouble supporting interleaved sequences (playground). Please file an issue against the xml crate you are using and they may be able to improve how they handle this case. Thanks!

@dtolnay I am having some trouble figuring out how exactly the TOML parser works, but it appears it works around the problem by first parsing the entire file into a DOM-like structure. That would also confirm why it doesn't allow to parse a stream of data, but only complete strings.

I made a commit to prove that in fact this case is not handled by serde.
https://github.com/Binero/serde/commit/9055a0399b59a00c99dd23d63d60b1e764f3d9d6

It is up to the format whether to buffer and/or read ahead to combine separated sequences of the same field. The toml format does this because that is what makes sense in toml. The serde_test crate does not. JSON also does not, because implicitly handling {"a":[0,1],"b":2,"a":[3,4]} as a concatenated array is not typically how JSON works (though a custom Deserialize impl can handle it that way if it wants).


File does not exist: emails.csv

emails.csv exists in the folder but is not recognized--not sure how to debug! Any help?

Your file looks to be in the correct location. I'm not sure what the issue could be, sorry!
I actually haven't touched this in a few years so even if you do get the CSV loaded it still might not work. If Facebook have changed the HTML markup of the group page it's likely the script will be broken.

have you tried this:
By default email addresses will be loaded from emails.csv in the package directory but you can override this by passing a new file name with the -f parameter. Emails should be on a new line and in the first column. There can be other columns in the CSV file but the email address has to be in the first column. Please also ensure your CSV has no headers.
use the -f parameter
it is 2020 and FB hasn't changed the HTML markup.


flickering web interface

@baimingze
The web app has a lot of flickering issues, when the use navigate between different windows, from the browser to the home page and from the help to the main page. Specially when the user arrive to the main page this effect is worst.

done. thank  @noedelta for the hint on "ng-cloak":).


Expose BaseUrl and BaseFileUrl settings

Did we reach a conclusion as to whether to implement this by just making the properties public, or by adding ctor parameters?

I'm fine with making them instance properties with public setters.

I've changed my mind - we shouldn't expose this as an API.
For anyone requiring such functionality, there is a workaround, see https://github.com/TelegramBots/Telegram.Bot/pull/857#issuecomment-657108726


Android - Update default collection name in heartbeat tool

Update the default collection name for the hearbeat tool to __dittotools_devices to make it a hidden collection and avoid potential collosions with customer-defined collections.

https://github.com/getditto/DittoAndroidTools/pull/46


Space automatically moves when app opens another app

Previously it wasn't, but after disabling System Integrity Protection it started to behave like a title.
For example,

Open Google Chrome in space 1, terminal in space 2, Slack app in space 3. (I'm in space 3 now)
Click URL in Slack.
Link appears in default browser: Chrome. (Moved to space 1)
If I confirm, at this point Slack has moved to space 2 and the terminal has moved to space 3.

I think that the windows in the same space move together, so the spaces are swapped.
Is this the default behavior?
I tried the following, but the behavior did not change.

Run yabai without skhd
Delete all yabai settings and run brew services restart yabai

My environment

macOS 10.15.3
yabai 2.2.2

This is a macOS thing and has nothing to do with yabai, see https://github.com/koekeishiya/yabai/wiki/Tips-and-tricks#fix-spaces-reordering-automatically for how to resolve this.

@koekeishiya
Thanks! That help resolved this.


Some Issues are not covered

Great documentation! I just wanted to mention a blog because the public is facing some issues this documentation is not covering.
One is the status code is returning 0 and another is the email is never received due to authenticated sender issues.
Some of those issues are also covered in this blog:
https://hectorhpflores72.wixsite.com/dreamscreate/post/sending-emails-using-php-sendgrid

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

ID: 97d85a3b-f782-a1cc-27ea-b05125bd9359
Version Independent ID: 1c4980e4-29a2-76f1-96a0-3bac3d8c834a
Content: How to use the SendGrid email service (PHP)
Content Source: articles/store-sendgrid-php-how-to-send-email.md
Service: multiple
GitHub Login: @thinkingserious
Microsoft Alias: erikre

@hecflores Thanks for the feedback. We are investigating into the issue and will update you shortly.

@hecflores Thanks once again for sharing the link for documentation enhancement. We will have this reviewed by the content owners and update as appropriate.

@Erikre and @SyntaxC4 Could you please check this request and update the documentation as needed?

@hecflores Thank you for linking to a blog post, however we are currently evaluating topics to find their appropriate owners, and if not found we are going to retire the content. If we find an owner for this content, we'll ask if they would like to add the link provided.
#please-close


Swap out Commonmark editor's syntax highlighting system

Closes #21.
Describe your changes
An exploration of using Lezer grammars (which power CodeMirror) to do syntax highlighting for the Commonmark editor. This change is entirely powered by the experimental b-kelly/prosemirror-lezer plugin along with the @lezer/markdown grammar.
While it is technically possible to swap out all rich-text syntax highlighting (or potentially even markdown parsing) for this approach, this is explicitly not in the plans. While hljs is not the first pick of syntax highlighting for a live editor, it does a "good enough" job and matches the desired rendered output for the Stack Exchange network.
If this approach pans out, the next steps are the enable incremental parsing in the upstream plugin, ensure that all the different syntax items are highlighted as we like and to extend the grammar to highlight our custom markdown syntax.
These changes add approx 18k after gzip (pushing us up to 144k total). That feels like a bit of a jump to me, but there may not be a better alternative. I'll do a little looking around and see if we can't bend markdown-it to do what we're looking for here.
PR Checklist

[x] All new/changed functionality includes unit and (optionally) e2e tests as appropriate
[x] All new/changed functions have /** ... */ docs
[x] I've added the bug/enhancement and other labels as appropriate
[x] Check impact of added libraries to gzipped bundle size

@KyleMit There is no phase 2, this is it 😛. See the second paragraph:

While it is technically possible to [...]

Are you testing the syntax highlighting in rich text mode? This is only replacing the syntax highlighting in markdown mode.


Tick rate inbetween 0 and 1

Is your feature request related to a problem? Please describe.
Allow us to execute our behaviors with a tick rate of less then 1 second
Describe the solution you'd like
Allow this to be something like 0.001 as a minimum

Describe alternatives you've considered
Nothing yet
Additional context
I am trying to recreate the structure found here... https://www.youtube.com/watch?v=YHUQY2Kea9U

Tick rate is measured in frames. 1 means every frame, 2 means every 2 frames. Having a value smaller than 1 therefore does not make sense.
What is the exact problem you are trying to solve here?

interesting my logic bust have a bug in it then.
my player was only changing directions every second or so.


Anki Keeps Insisting New Update Available After Install

OS: MacOS Ventura 13.5
Anki version 2.1.65
After the latest update, every time I check for updates in Anki, this add-on pops up as having an available update (latest 8/15/2023 update). Installing the updates does nothing it appears, and I am prompted to install the update again once I check for updates. On latest public Anki 65, MacOS.

Issue resolved.


Add invalid argument exception

Hello there,
Let's say I have the following class:
class MyClientWrapper {
    private $httpClient;

    public function callSomething(){
          $response = $this->httpClient->get('/');
          return GuzzleHttp\json_decode($response->getBody());
    }
}

when I call the function above I have to do something like this:
try{
   $mywrapper->callSomething();
} catch (\InvalidArgumentException | GuzzleException $e){
    ....
}

This has the defect that I if another part of my code throws an InvalidArgumentException inside this class I can not separate it from the the GuzzleHttp InvalidArgumentException.

Looks good 👍

Looks good as always @gmponos ! Thanks!

Hello @gmponos, i create a fork of this repo and release this marge request into the new version(6.4.0).
Namespace compatibility is 100%, and you can use my changes if you patch composer.json in your projects

replace "guzzlehttp/guzzle": "^6.3" to "someblackmagic/guzzle": "^6.4"
add "guzzlehttp/guzzle": "6.3.*" into replace block

Fork link: https://github.com/SomeBlackMagic/guzzle/


Whats the  in the Rom image?

In the section "Create the PetaLinux Software Component" in Step 16:

/* linux */
 the_ROM_image:
 {
 	[fsbl_config] a53_x64
 	[bootloader] <fsbl_path>/fsbl.elf
 	[pmufw_image] <pmufw_path>/pmufw.elf
 	[destination_device=pl] <bitstream>
 	[destination_cpu=a53-0, exception_level=el-3, trustzone] <bl31_path>/bl31.elf
 	[destination_cpu=a53-0, exception_level=el-2] <u-boot_path>/u-boot.elf
 }

it is pretty clear what the paths are because they were copied in the folder before in step 15 - however I could not find a .bit file that would fit the description for  in [destination_device=pl] so I am wondering what it might be? boot.scr? image.ub?

Thank you!


Fix loss of gdextension on editor startup

Fixes #97900
Fixes #97962
Fixes #98056
Fixes #97735

The GDExtension files were not processed in EditorFileSystem::_first_scan_process_scripts following optimization in #95678.
Thanks to @NetroScript to pinpoint the problem and find the solution. This PR is based on it's suggested modifications. That's why I added him as Coauthor.
I think your approach to use ResourceLoader::get_recognized_extensions_for_type is the right one. It's sounds like a bug to me that the method returns .res and .tres for GDExtension. I'm not an expert of the GDExtensions but I'm pretty sure .res and .tres are not supported for GDExtensions. If you check into GDExtensionLibraryLoader::parse_gdextension_file, it only supports a ConfigFile format and not a resource file. It does not seems easy to modify ResourceLoader::get_recognized_extensions_for_type to not return .res and .tres for GDExtension and I'm worry about side effects so I think that excluding .res and .tres extensions in _first_scan_filesystem seems the right way to me.
Edited: Adding #97962 in the fixed issue list.
Edited: Adding #98056 in the fixed issue list.

This should also fix https://github.com/godotengine/godot/issues/97962

Thanks for the fast PR. When I checked it out I also found no way to exclude res and tres. As all resource loaders get iterated to find extensions the ResourceFormatLoaderBinary for example also is iterated, which returns true for all handled types (there in theory it would be possible to add an exclusion from my uneducated observations), which causes res to be added.

Exactly! We will see what reviewers think about that.

This also fixes gdextensions not loading on android: https://github.com/godotengine/godot/issues/98056

I think we should rename and attempt to modify ResourceLoader::get_recognized_extensions_for_type to not return .res and .tres for GDExtension
Or at least see that its too difficult

It's not exactly a bug. ResourceFormatLoaderText/Binary handle any type of Resource

I haven't tested it, but I don't think re-saving a .gdextension file as .tres/.res would result in a working GDExtension, because the GDExtension resource class doesn't keep all its data in registered properties. If there's a way to prevent re-saving as a .tres/.res we should probably do that - although, that's not in scope for this PR.

It's similar issue to #34080

As suggested by @fire, I modified code to prevent ResourceLoader::get_recognized_extensions_for_type returning res and tres extensions for GDExtension. I little if added in ResourceFormatLoaderBinary::get_recognized_extensions_for_type and ResourceFormatLoaderText::get_recognized_extensions_for_type did the trick.

Thanks!


tests/ztest/test/mock fails to complete on max10/nios2

Toolchain: ZEPHYR_GCC_VARIANT=zephyr
Commit ID cc5ae49133b48d4a7b3372f0bf22f942416debb7
***** Booting Zephyr OS 1.12.99 (delayed boot 3000ms) *****
Running test suite mock_framework_tests

===================================================================

starting test - parameter_tests

after 30s the test was canceled

@kumarvikash1 assign to some please..

@ajaykish , Can you please look into this test failure.

@nashif , somehow i am not able to assign to @ajaykish . Can you please assign to him.


Don't generate kubeclient at runtime in testing

Updates tests to use common Kube and Runtime clients generated at
startup time rather than having them re-generated in each test at
runtime.
Closes #2570

Signed-off-by: Noah Sapse<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky
[ ] Tests that remove the [FLAKE] tag are no longer flaky

/hold

Looks really good, nice job. Didn't intend for this to merge right away so I put a hold on it -- let's address the whitespacing concerns and rebase off latest and then I will re-lgtm and drop the hold

/hold cancel
/lgtm

Good to merge then?


Prototype: sitemap to index

Following up on https://github.com/hbz/oerindex/issues/2#issuecomment-583291640: Given a sitemap URL like https://www.hoou.de/sitemap.xml, a URL prefix like https://www.hoou.de/materials/, an Elasticsearch index location URL like http://localhost:9200, a Flux like:
open-http | decode-html | fix | encode-json
And a Fix like:
map(html.head.title.value, title)
map(html.body.div.div.div.div.div.div.div.p.value, description)

We want to:

[ ] Convert all resources listed in the given sitemap, if their url loc starts with the given prefix
[ ] Index the results in an Elasticsearch index in the given index location
[ ] Return a sample query against the used index

The long term idea is to do all of this in a single new UI. For this prototype, I suggest we provide the config parameters (sitemap, prefix, index, flux, fix) in some kind of config file and run the workflow from the command line. The Flux and the Fix can be tested in http://test.lobid.org/fix.

Basically using Flux as the config file for all the perameters would look something like this:
"https://www.hoou.de/sitemap.xml"
| list-sitemap(prefix="https://www.hoou.de/materials/")
| open-http
| decode-html
| fix("
  map(html.head.title.value, title)
  map(html.body.div.div.div.div.div.div.div.p.value, description)")
| encode-json
| index-elasticsearch("http://localhost:9200/")

This would require new list-sitemap and index-elasticsearch metafacture  modules.

We just discussed this as a fast way to a first index:

Set up a program to index resources from https://www.hoou.de/sitemap.xml
Hard-code config into the program (final config should happen in Flux as described above)
Create JSON containing the url, title, description, and license, index in Elasticsearch


Endpoints controller is logging too much

Pods not having an IP yet or pods that don't have a port aren't v(0)
log items, since the former is usually temporary and the latter has
nothing actionable for an admit.
Make both V(4) as per our guidelines

LGTM


Integration test

Summary
TODO: What does this PR do? (Replace with summary!)
Other Information
TODO (if relevant)
PR Checklist
Please run through before submitting for final review:

[ ] The PR title is descriptive of what changed.
[ ] The description sections above are filled out.
[ ] The CI pipeline is passing
[ ] Added the ready-for-review label to the PR.

Codecov Report

Merging #9 (203ec9f) into main (b0dc5b3) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   61.01%   61.01%
=======================================
  Files           3        3
  Lines         118      118
  Branches       18       18
=======================================
  Hits           72       72
  Misses         43       43
  Partials        3        3

Impacted Files
Coverage Δ

plugin_scripts/deploy.py
60.36% <100.00%> (ø)

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 b0dc5b3...203ec9f. Read the comment docs.


Add KeepParentDirectories flag

When zipping something like this the paths were mapping like:
web/static -> static
configs/os_agnostic/deployment -> deployment
I want something like this
web/static -> web/static
configs/os_agnostic/deployment -> configs/os_agnostic/deployment

Any thoughts on this?

Can you be more specific about what you are doing, what the actual behavior is, and what the expected behavior is?

Background
I wrote a go server that has html files stored in a folder web/html. The server uses this path to find the html files that it serves.
When I zip these files and copy them to a linux server in the cloud and unzip them the path is now just html (The parent folder web no longer exists). Now when my server tries to serve files from web/html it thinks they don't exist since they're really in html folder.
I hope that's more clear.
Actual Behavior
web/html -> html
Expected (with KeepParentDirectories flag)
web/html -> web/html

Also, note I originally had a bash script that was using mac terminal zip and unzip.
When I converted this script to Go, using Archiver package it wasn't working anymore since zip's output is different than Archiver's with the same parameters hence why I'm suggesting adding this flag.
Perhaps I'm missing something and one of the other flags do this but it doesn't appear to be so.

I almost understand, but if you could provide a few lines of code (or the exact commands you're using, if the CLI) to demonstrate what you mean, that would be best.

Expected behavior using (zip and unzip)

Actual behavior using (arc archive and unzip)

Awesome, thank you!

So can we merge it in? What's the next step

I just need to find some time to review it. Sorry, it's on me.

v4, introduced in #302, gives you this flexibility now, so I think this is resolved/irrelevant in the new version.


OAuth2ClientProperties was moved and conflicts with Spring Boot provided class

Trying to upgrade to 2.3.0 I get this error:
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ resource-server ---
[WARNING] Rule 2: org.apache.maven.plugins.enforcer.BanDuplicateClasses failed with message:
Duplicate classes found:

  Found in:
    org.springframework.boot:spring-boot-autoconfigure:jar:2.3.0.RELEASE:compile
    org.springframework.security.oauth.boot:spring-security-oauth2-autoconfigure:jar:2.3.0.RELEASE:compile
  Duplicate classes:
    org/springframework/boot/autoconfigure/security/oauth2/client/OAuth2ClientProperties.class

As far as I see, until 2.3.0, OAuth2ClientProperties was in a different package, org.springframework.boot.autoconfigure.security.oauth2, so it didn't conflict with the one provided by Spring Boot, but then it was moved in 6a312d2.
Any chance of reverting this change?
I'm stuck with the old OAuth2 classes since I have an Authorization Server built on it and the new Spring Security doesn't provide one.

ping

Sorry for the delay, @andrei-ivanov. This is still on my radar for the 2.3.1.RELEASE.

I think reverting is an option, @andrei-ivanov, but reverting will re-introduce the package cycle that moving it solved. Before reverting, then, I'd like to see if there's another home for OAuth2ClientProperties that still resolves the package cycle.
Would you be able to produce a minimal sample (in a separate GitHub project) that uses the Maven Enforcer Plugin? I could use that to test against an make sure whatever change is made doesn't cause further problems.

https://github.com/solven-eu/spring-security-oauth2-boot_251/
Hope it helps. We also hoped this for 2.3.1.RELEASE

In which release will this be integrated ? Thanks
Le lun. 15 juin 2020 à 20:49, Josh Cummings<EMAIL_ADDRESS>a
écrit :

Closed #251
https://github.com/spring-projects/spring-security-oauth2-boot/issues/251
via f69180b
https://github.com/spring-projects/spring-security-oauth2-boot/commit/f69180b36bcec40c2f5ad60fe5f1c28a26b91fb1
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/spring-projects/spring-security-oauth2-boot/issues/251#event-3445718992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQFCF2WNRNDH77XIQN2BKLRWZULNANCNFSM4NN4S6GA
.

This is targeted for the 2.3.1 release. You can check this in the future on the right-hand side of the issue under the Milestones heading.


Community Operator Stable Channel 3.8 not working

Hi,
v3.8.10 is the only image in the repo but the operator is only using tags without the v prefix.

Stable Version 3.7 is working.

Can you please fix the Stable Channel for 3.8 by creating an additional image with the tag 3.8.10?

Hi! The image is built, please let us know if there are more issues.
We have issues with buildx, it occasionally reports success when the image is not built.

Thank you, it's working now


Fix for server error on release page when a user deleted their account

Fixes #2596 using a fake user.

Thanks!


Publish Code Coverage Results - Specify Working Directory - Feature Request

We are generating unit test source code coverage information from gcovr into a Cobertura style xml file (coverage.xml). The unit tests are built and run with ceedling and the gcov plugin generates the code coverage information with gcovr. On Azure DevOps, I'm using the Publish Code Coverage Results task to parse and display the coverage information. Our project directory is structured as follows:

project

source
test

static_analysis
unit_test

The unit_test directory contains project.yml, which is ceedling's project file. Ceedling must be run from the unit_test directory, which then runs gcovr with the unit_test directory as its root. The resulting coverage.xml has paths like, filename="../../source/feature.c". When running the Publish Code Coverage Results task on coverage.xml, ReportGenerator.exe is able to correctly parse the coverage; however, ReportGenerator.exe reports warnings saying every source file is missing. I see the warnings no matter which directory coverage.xml is copied to. Example warning: File '.\..\..\source\feature.c' does not exist (any more).
I have a workaround python script that changes all filename="../../source/feature.c" to filename="source/feature.c" and outputs to cobertura.xml. I can then put the new cobertura.xml into any directory, call it with the Publish Code Coverage Results task, and ReportGenerator.exe correctly finds all files and generates html with coverage info without warnings or errors.
My feature request is to be able specify a working directory for the Publish Code Coverage Results task or a root directory for coverage.xml.
Thank you.

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

ID: c6ac4ff4-9839-6a6d-8d20-a25084d221ef
Version Independent ID: bd09f139-8e69-8ea1-6671-b7bba8e17c23
Content: Publish Code Coverage Results task - Azure Pipelines
Content Source: docs/pipelines/tasks/test/publish-code-coverage-results.md
Product: devops
Technology: devops-cicd
GitHub Login: @PBoraMSFT
Microsoft Alias: pbora

@aschlicht To make sure it gets in front of the right people, please submit your feature request here.