Unfair comparison with SimpleBaseline

Nice pioneer~
But it is not fair to compare TransPose-R with the original SimpleBaseline-Res, as the original SimpleBaseline use a weaker augmentation strategy and a shorter training schedule.  This will lead to a large gap of 1.5 AP.
I look forward to a fair comparison between them for reference.

Thanks for your interest!
We use the same data augmentation strategy (following the HRNet code) for all our models. The long training schedule is a necessary setting for training our transformer-based models. Thank your suggestion. We would consider controlling the data augmentation strategy to be the same when comparing with SimpleBaseline.

Thanks for your interest!
We use the same data augmentation strategy (following the HRNet code) for all our models. The long training schedule is a necessary setting for training our transformer-based models. Thank your suggestion. We would consider controlling the data augmentation strategy to be the same when comparing with SimpleBaseline.

emmm, under this situation, an ablation study is appealing and necessary. This make me curious that do the transformer-based models perform very poor when using the aug-schedule configuration in the original SimpleBaseline?

emmm, under this situation, an ablation study is appealing and necessary. This make me curious that do the transformer-based models perform very poor when using the aug-schedule configuration in the original SimpleBaseline?

Hi, @HuangJunJie2017 . We did not train our models using the aug-schedule configuration of the original SimpleBaseline.
We provide the convergence curves and log of the mAP for TransPose-R-A4. The curves are as below:

We also use the same data augmentation strategy of TransPose-R,
DATASET:
  COLOR_RGB: true
  DATASET: 'coco'
  DATA_FORMAT: jpg
  FLIP: true
  NUM_JOINTS_HALF_BODY: 8
  PROB_HALF_BODY: 0.3
  ROOT: 'data/coco/'
  ROT_FACTOR: 45
  SCALE_FACTOR: 0.35
  TEST_SET: 'val2017'
  TRAIN_SET: 'train2017'

and a longer training schedule (203 epochs), to train the original SimpleBaseline-Res50+DarkPose, it now brings 0.4 AP gain (72.0->72.4) on coco val datset with the same detected boxes (56.4AP).

Arch
AP
Ap .5
AP .75
AP (M)
AP (L)
AR
AR .5
AR .75
AR (M)
AR (L)

pose_resnet
0.724
0.894
0.796
0.685
0.795
0.779
0.932
0.841
0.734
0.844

Hi, @HuangJunJie2017 . We did not train our models using the aug-schedule configuration of the original SimpleBaseline.
We provide the convergence curves and log of the mAP for TransPose-R-A4. The curves are as below:

We also use the same data augmentation strategy of TransPose-R,
DATASET:
  COLOR_RGB: true
  DATASET: 'coco'
  DATA_FORMAT: jpg
  FLIP: true
  NUM_JOINTS_HALF_BODY: 8
  PROB_HALF_BODY: 0.3
  ROOT: 'data/coco/'
  ROT_FACTOR: 45
  SCALE_FACTOR: 0.35
  TEST_SET: 'val2017'
  TRAIN_SET: 'train2017'

and a longer training schedule (203 epochs), to train the original SimpleBaseline-Res50+DarkPose, it now brings 0.4 AP gain (72.0->72.4) on coco val datset with the same detected boxes (56.4AP).

Arch
AP
Ap .5
AP .75
AP (M)
AP (L)
AR
AR .5
AR .75
AR (M)
AR (L)

pose_resnet
0.724
0.894
0.796
0.685
0.795
0.779
0.932
0.841
0.734
0.844

Hi, @HuangJunJie2017 . We did not train our models using the aug-schedule configuration of the original SimpleBaseline.
We provide the convergence curves and log of the mAP for TransPose-R-A4. The curves are as below:

We also use the same data augmentation strategy of TransPose-R,
DATASET:
  COLOR_RGB: true
  DATASET: 'coco'
  DATA_FORMAT: jpg
  FLIP: true
  NUM_JOINTS_HALF_BODY: 8
  PROB_HALF_BODY: 0.3
  ROOT: 'data/coco/'
  ROT_FACTOR: 45
  SCALE_FACTOR: 0.35
  TEST_SET: 'val2017'
  TRAIN_SET: 'train2017'

and a longer training schedule (203 epochs), to train the original SimpleBaseline-Res50+DarkPose, it now brings 0.4 AP gain (72.0->72.4) on coco val datset with the same detected boxes (56.4AP).

Arch
AP
Ap .5
AP .75
AP (M)
AP (L)
AR
AR .5
AR .75
AR (M)
AR (L)

pose_resnet
0.724
0.894
0.796
0.685
0.795
0.779
0.932
0.841
0.734
0.844

Hi, @HuangJunJie2017 . We did not train our models using the aug-schedule configuration of the original SimpleBaseline.
We provide the convergence curves and log of the mAP for TransPose-R-A4. The curves are as below:

We also use the same data augmentation strategy of TransPose-R,
DATASET:
  COLOR_RGB: true
  DATASET: 'coco'
  DATA_FORMAT: jpg
  FLIP: true
  NUM_JOINTS_HALF_BODY: 8
  PROB_HALF_BODY: 0.3
  ROOT: 'data/coco/'
  ROT_FACTOR: 45
  SCALE_FACTOR: 0.35
  TEST_SET: 'val2017'
  TRAIN_SET: 'train2017'

and a longer training schedule (203 epochs), to train the original SimpleBaseline-Res50+DarkPose, it now brings 0.4 AP gain (72.0->72.4) on coco val datset with the same detected boxes (56.4AP).

Arch
AP
Ap .5
AP .75
AP (M)
AP (L)
AR
AR .5
AR .75
AR (M)
AR (L)

pose_resnet
0.724
0.894
0.796
0.685
0.795
0.779
0.932
0.841
0.734
0.844

emmm, i have not try SimpleBaseline-Res50+darkpose+hrnetaugschedule. But i have tried another similar configuration SimpleBaseline-Res50+UDP+hrnetaugschedule. This configuration scores 73.4 AP on coco val datset with the same detected boxes (56.4AP).  72.0 for SimpleBaseline-Res50+darkpose+hrnetaugschedule is too low. There may be some problem in your experiment which may has negative impact on both  SimpleBaseline and  TransPose? TransPose can perform better?

emmm, i have not try SimpleBaseline-Res50+darkpose+hrnetaugschedule. But i have tried another similar configuration SimpleBaseline-Res50+UDP+hrnetaugschedule. This configuration scores 73.4 AP on coco val datset with the same detected boxes (56.4AP).  72.0 for SimpleBaseline-Res50+darkpose+hrnetaugschedule is too low. There may be some problem in your experiment which may has negative impact on both  SimpleBaseline and  TransPose? TransPose can perform better?

We run the official DarkPose code on our machine. Here we provide the history log files.
orignal_config_baseline_res50_256x192_d256x3_adam_lr1e-3_2020-11-10-13-01_train.log
orignal_config_baseline_res50_256x192_d256x3_adam_lr1e-3_2020-11-11-20-52_valid.log

We run the official DarkPose code on our machine. Here we provide the history log files.
orignal_config_baseline_res50_256x192_d256x3_adam_lr1e-3_2020-11-10-13-01_train.log
orignal_config_baseline_res50_256x192_d256x3_adam_lr1e-3_2020-11-11-20-52_valid.log

emm, it it seem that you don't train SimpleBaseline-Res50+darkpose+hrnetaugschedule this with 210 epoch, but 140 epoch instead. This make this configuration perform poor (72.0) ~, if you train this with 210 epoch, SimpleBaseline-Res50+darkpose+hrnetaugschedule will score more than 73.0 AP coco val datset with the same detected boxes (56.4AP).

emm, it it seem that you don't train SimpleBaseline-Res50+darkpose+hrnetaugschedule this with 210 epoch, but 140 epoch instead. This make this configuration perform poor (72.0) ~, if you train this with 210 epoch, SimpleBaseline-Res50+darkpose+hrnetaugschedule will score more than 73.0 AP coco val datset with the same detected boxes (56.4AP).

Yes, a longer scheduler or stronger augmentation indeed increases the AP. But, the original SimpleBaseline-Res50 and SimpleBaseline-Res50+DarkPose are trained with 140 epochs. Due to we use the data augmentation of HRNet for TransPose-R, so we trained SimpleBaseline-Res50+DarkPose with stronger data augmentation for a fair comparison. In addition, the current result I reported (204 epochs) is 72.4 AP now. Maybe a better result will be achieved by addining training steps.

Yes, a longer scheduler or stronger augmentation indeed increases the AP. But, the original SimpleBaseline-Res50 and SimpleBaseline-Res50+DarkPose are trained with 140 epochs. Due to we use the data augmentation of HRNet for TransPose-R, so we trained SimpleBaseline-Res50+DarkPose with stronger data augmentation for a fair comparison. In addition, the current result I reported (204 epochs) is 72.4 AP now. Maybe a better result will be achieved by addining training steps.

Point taken, the comparison between SimpleBaseline and TransPose-R is unfair, but the comparison between TransPose-R and TransPose-H is fair.

Point taken, the comparison between SimpleBaseline and TransPose-R is unfair, but the comparison between TransPose-R and TransPose-H is fair.


Unique case isn't unique in ibex_alu.sv

On the head of master (7dafdf64), run the following command:
cd dv/uvm/core_ibex
make WAVES=1 VERBOSE=1 ISS=spike COV=1 SEED=26187 TEST=riscv_arithmetic_basic_test

Once this has finished, have a look at one of the simulation logs. For example, out/seed-26187/rtl_sim/riscv_arithmetic_basic_test.0/sim.log (attached). You'll see VCS warning about incorrect unique case:
Warning-[RT-MTOCMUCS] More than one condition match in statement
/src/lr/ibex/rtl/ibex_alu.sv, 78
  More than one condition matches are found in 'unique case' statement inside
  core_ibex_tb_top.dut.u_ibex_core.ex_block_i.alu_i, at time 32370000ps.

  Line number 79 and 80 are overlapping.

Rather upsettingly, this doesn't actually cause the test to fail. But it does suggest a problem with the RTL.

I think I also saw this a while ago, looked in the waves and it wasn't true (the cases were unique). It is one of those unique case (1'b1) constructs though, which we probably should move towards removing.

I've just pulled up the waves (which turned out to have been generated) and I don't think the two signals are true at the same time:

I notice that this time stamp is the first time that they are true on adjacent clock cycles. Is it possible that this is something to do with simulation ordering? I guess that the signals will both appear true for a delta cycle if the always_comb block that sets adder_op_b_negate on line 52 gets scheduled after the always_comb that sets mult_sel_o in ibex_decoder.sv.

I did not check the waves, but looking at the source it is obvious that this should not happen. Whenever multdiv_sel_i is set, the ALU operator is set to ALU_ADD thus adder_op_be_negate is 1'b0. This goes ultimately back to the decoder:
https://github.com/lowRISC/ibex/blob/b72d263eac25589fa1688f98d45deb2e3b147645/rtl/ibex_decoder.sv#L925-L928

Ah, thanks for posting the waves @rswarbrick ;-)

Your explanation sounds reasonable. Thinking about removing those unique case(1'b1) statements as suggested by @tomroberts-lowrisc , what should we replace it with ideally? Ternary statements lead to priority encoders which is not always good.

If we get rid of unique case(1'b1) style constructs what's a good construct to replace the unique case(1'b1) with? You don't want to use ternary statements, i.e.
assign adder_in_b =      multdiv_sel_i ? multdiv_operand_b_i :
                     adder_op_b_negate ? operand_b_neg       :
                                         {operand_b_i, 1'b0};

is no good as there's no need for the priority selection (can never see multdiv_sel_i and addr_op_b_negate asserted at the same time).
You could use casez with wildcards and flip the case around so the constant bit is in the case labels:
always_comb begin
  unique casez({multdiv_sel_i, adder_op_b_negate})
    2'b1?:    adder_in_b = multdiv_operand_b_i;
    2'b?1:    adder_in_b = operand_b_neg;
    default : adder_in_b = {operand_b_i, 1'b0};
  endcase
end

But that looks pretty awful (2'b1? and 2'?1 overlap even though we know if practice they don't).
You could do the same as above without the wildcards but then you're back to something that deals with the both asserted case so you (may) have logic you don't need:
always_comb begin
  unique case({multdiv_sel_i, adder_op_b_negate})
    2'b10:    adder_in_b = multdiv_operand_b_i;
    2'b01:    adder_in_b = operand_b_neg;
    default : adder_in_b = {operand_b_i, 1'b0};
  endcase
end

Perhaps we want a onehot mux macro or module?

Great minds think alike?
Yep agreed, ternary is not the right thing. I've used the concatenated pattern thing in the past but agree it's pretty ugly. Maybe a onehot mux module, or just manually writing the AND/OR logic if it's simple as in this case.

Searching for the error message found this workaround: add -xlrm uniq_prior_final to VCS's option list. It seems this defers unique case checks until signals have stabilised.
I have no idea why this wouldn't be the default option, but maybe that's all we need?

Reading a bit further, the 2012 VCS user manual contains the following:

Unique/Priority Case/IF Final Semantic Enhancements
The behavior of the compliance checking keywords unique and
priority for case and for if...elseif...else selection
statements as defined in the IEEE 1800-2009 LRM section named
“Conditional if-else statement” in some cases can cause spurious
warnings when used inside a module's continuous assignment or always
block. By default, VCS will evaluate compliance with unique or
priority on every update to the selection statement input.
To force unique and priority to evaluate compliance only on the
stable and final value of the selection input at the end of a
simulation timestep, VCS now provides a compile time switch -xlrm uniq_prior_final.
This can be useful, for example, when always_comb might trigger
several times within a simulation time slot while its input values are
getting stabilized. The case statements can get executed several
times during same time slot if it is valid for combinational blocks.
While going through intermediate transitions, the case statement
might get values that violate the unique or priority property and
cause VCS to report multiple runtime warnings. When it is undesirable
to receive intermediate warnings, compile time option
‘-xlrm uniq_prior_final’ can be used to evaluate compliance for only the
final stable value of the input.

Shall I just prepare a patch to tell VCS to be less enthusiastic? :-)

I think that'll solve this issue, at some point we should ponder whether we like the unique case(1'b1) style construct or not. I'll open a style-guide issue.

Shall I just prepare a patch to tell VCS to be less enthusiastic? :-)

Sounds good to me, especially since there is no quick/easy solution to avoid the unique case(1'b1)
.
I would prefer not to write manual AND/OR logic as I consider this more error prone to extensions. Having a generic onehot mux module sounds like a good idea. This would allow us also to replace all other muxes that are currently using ternaries without the need for priority encoding.

I'd note the issue of unique case (1'b1) has already been discussed https://github.com/lowRISC/style-guides/issues/8 where it was concluded this is a construct we are happy to allow.


Check graphic hash

replaced by #2162

It wasn't really necessary to open a new PR; just force push on this one.


I am no longer working on Knative full time

And release is a full time job.
/assign @evankanderson @dprotaso

Sorry to see you go, Victor!

Nobody can approve! :)


[FALSE-POSITIVE]

Domains or links
Please list any domains and links listed here which you believe are a false positive.
https://clover.co.jp
More Information
How did you discover your web site or domain was listed here?

Website was hacked　→　Yes, now we are safe.
Incorrectly marked as Phishing on Phishtank or OpenPhish?

Have you requested removal from other sources?
Please include all relevant links to your existing removals / whitelistings.
Our site was temporarily defaced, but the threat has now been completely removed and we are completely safe.
For this reason, please remove the designation as soon as possible. Our operations have been disrupted.
Additional context
Add any other context about the problem here.
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file

https://github.com/mitchellkrogza/phishing/blob/main/falsepositive.list
Please include the same above information to help speed up the whitelisting process.

The evidence of cleanliness of our site is;
https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3Aclover.co.jp&run=toolpage
https://sitecheck.sucuri.net/results/https/clover.co.jp
https://transparencyreport.google.com/safe-browsing/search?url=https:%2F%2Fclover.co.jp
https://check.spamhaus.org/not_listed/?searchterm=clover.co.jp
please delist our domain [clover.co.jp]

Already whitelisted. Closing.


"Fix" Spotlight IndexError bug

Description
This PR applies a short-term workaround to the Spotlight IndexError we've been running into and was able to reproduce (see #140). The reason, it turns out, is a bug in the Spotlight source code that gets triggered if the IMF model's batch size (256, by default) divides the total number of interactions passed to it with a remainder of 1, i.e., num_interactions % batch_size == 1.
The "fix" is as follows: during a job run, if the job sees that num_interactions % batch_size == 1, it removes 1 interaction from the interactions dataset to make the remainder no longer 1, thus avoiding the error. The interaction to remove is selected randomly among a subset of interactions involving the most frequently interacted/viewed article, i.e., the article having the most rows in the dataset, so as to minimize the effect on model performance. (The rationale is thus: Suppose articles A gets viewed by 20,000 different readers and article B by 10 different ones. The influence of 1 view of B to how the IMF model calculates B's embeddings is much greater than that of 1 view of A to how the model calculates A's embeddings; therefore, removing A's view yields a smaller effect on performance than removing B's view.)
We can remove this workaround once Spotlight's author fixes the aforementioned bug, although that seems to be unlikely given how inactive the Spotlight repo looks.
Finally, we'll also keep the diagnostic code added in #140 for now, should a similar error still appears. If everything looks good after a month or so, we can remove that code.
Testing
All tests passed. I also added a new test, test_article_recommendations_spotlight_batchsize() that attempts to fit the model given num_interactions % batch_size == 1. If the "fix" works as expected, no IndexError gets raised and the code passes the test.

Closing this since there's an improved workaround, thanks to Mark's suggestion: https://github.com/LocalAtBrown/article-rec-training-job/pull/144.

Reopen since the #144 workaround might be more difficult and time-consuming to thoroughly evaluate performance.


Add the Book class

What does this PR do?
This PR is raised to implement the following features: 👍 :

In this project, we created a console app that will help us to keep a record of different types of things you own: books, music albums, movies, and games. Everything will be based on the UML class diagram presented below. The data will be stored in JSON files but we also prepared a database with the structure of a table analogical to your program's class structure. 🪄🎈

[ ] Created the Book class with its properties and methods.😊
[ ] Created BookController class in which I persist data and load it through store_books and load_books methods.
[ ] Added list_books and add_book methods in main.rb.💯
[ ] Added an instance variable @books in main.rb in which I load the books from the books.json file.👌
[ ] Called store_books in main.rb after exiting the app to persist data.

Description of the task to be completed 👎

[ ] Created BookController class in which I persist data and load it through store_books and load_books methods.
[ ] Added list_books and add_book methods in main.rb.👍
[ ] Added an instance variable @books in main.rb in which I load the books from the books.json file.👌
[ ] Run a program using the command line.💯

How should it be tested
Clone the repository
git clone https://github.com/osamaashraf6/Ruby-Capstone-Project

Navigate to the folder
cd Ruby-Capstone-Project

Checkout the branch
git checkout book-class

Thanks for reviewing my PR 😊
Don't forget to give a ⭐ to support me 😃

don't forget to pull dev first then merge it please


Create project challenge-platform-app

Fixes #229
Changelog

Create the project apps/challenge-platform-app

Steps

Create the appnx g @nrwl/angular:application challenge-platform-app --dry-run
nx g @nrwl/angular:application challenge-platform-app

Start the appnx serve challenge-platform-app

Update a few project files using the files in web-app as reference.
Fix an unused-var error in challenge-platform-app-e2e.


Unsupported OS: linux

Hi, not sure if a bug or current limitation, but when running Decentraland.AppImage on Linux it outputs the following warning on the terminal: Unsupported OS: linux, and that is all it does.
Can't remember the exact release when this started to happen, but was around the Pride Month event

Took a look into the code, and to allow the launcher to run on Linux seems fairly easy. It fails when the function getAppBasePath returns a relative path.
Adding linux on the line https://github.com/decentraland/explorer-desktop-launcher/blob/7a27ede36b816ef3f070893cca8a1328d51941b8/electron/helpers.ts#L64
Adding
else if (process.platform === 'linux') {
    return `/some/absolute/path`
}

at https://github.com/decentraland/explorer-desktop-launcher/blob/7a27ede36b816ef3f070893cca8a1328d51941b8/electron/helpers.ts#L73
Not sure what is the intended path for linux. Something like /home/${process.env.USER}/.config/${applicationFolderName}/ ?

Hey @EibrielInv feel free to open a PR if you find out how this should be configured, I think no one on the explorer team works with Linux and adding support for it hasn't been that much of a priority.
You can also try and use app.getPath('userData') to see if that also works


[Feature Request] Implement Shared Credential Management for Enhanced Service and API Authentication

Reason for Suggestion
To streamline the authentication process across various services and APIs, particularly within Microsoft ecosystems, where this issue is notably severe.
Content of the Proposal
Expand the existing variable management system in Langflow to include shared credential management. This would enable the system to retain authentication information for each service and API, reducing the need for repeated authentication processes and enhancing overall security and usability.
Technical Considerations

Develop a secure storage system for credentials that can be accessed by necessary services without compromising security.
Integrate with Microsoft services using appropriate APIs that support shared credentials.
Implement robust encryption mechanisms to protect stored credentials.

Potential Use Cases

Users can interact seamlessly with multiple Microsoft services without needing to re-authenticate for each service.
Reduces the administrative burden of managing multiple credentials and enhances security by minimizing exposure to credential theft.

Even though currently, double-clicking on an available handle displays it in the side menu, many users are more familiar with drag-and-drop actions. It would be beneficial to add this action to the drag functionality as well.

When disconnecting an already connected component, the current method involves selecting the connected handle and releasing it into the air. It might be better to add a hover effect to these handles to make them easier to select and display a more visible button.
Adding a highlight to the line currently being edited when hovered over would also be a great feature. This would enhance the visibility and usability of the editing process.

We primarily use N8N, but honestly, Langflow seems to have more sophisticated design elements, such as the component groups.


[Optional] Allow the user to request the uncompressed image to CuratorBot

If we end up adding the original URL of each shot message as described in #27 we could, in theory, retrieve the image URL momentarily (so we get a trimmed URL) so that the user can download it without being part of the Discord server.
Since it's a download on-demand I guess it'd fall within Discord's new guidelines, but I wouldn't discard the possibility of this being discontinued in the future. Altho I doubt many people would abuse this for Discord to do something about it.
Blocked by

[x] #27

As discussed on https://github.com/framedsc/HallOfFramed/issues/26#issuecomment-1823595715, we won't be compressing the images, so we will be uploading the original images, meaning there is no need to do this for now.
If things change in the future and we need to start compressing the shots we might go back to this.


Raspberry pi 1 B crash on reboot after install [

latest release version confirmed.

"Please confirm you will submit an issue."
uh? that's why i'm here, right?

[x] I confirm that this is an issue rather than a question.

we get it, questions will be closed.
Bug report
Raspberry pi 1 B crash on reboot after install
following this tutorial:
https://www.youtube.com/watch?v=urOEHzbV48A
using the official raspberry os install method:
https://www.raspberrypi.org/documentation/installation/installing-images/
and using "raspberrypi os other" "raspberry pi os lite 32bit"
Steps to reproduce
install raspberry pi os other lite 32bit
sudo apt-get update
sudo apt-get upgrade
cat /proc/cpuinfo [to find your arm architecture]
https://github.com/hyperion-project/hyperion.ng/releases
download hyperion:
wget https://github.com/hyperion-project/hyperion.ng/releases/download/2.0.0-alpha.6/Hyperion-2.0.0-alpha.6-Linux-armv6l.deb
install hyperion
sudo dpkg -i Hyperion-2.0.0-alpha.6-Linux-armv6l.deb
before reboot open "ipaddress":8090  after reboot works perfectly
REBOOT
open "ipaddress":8090  after reboot FAILs to load
What is expected?
website loads properly.
What is actually happening?
hyperion website fails to load.
System

how about a cmd line version. Ironically my issue is literally getting to the web interface.... dont feel like re-installing again.
Phil Harris:
Same issue here on a RPi 3 Model B ... Hyperion installs but no web interface on either port 8090 or 8091. About to try using the non-lite version of Pi OS (OK ... tried that and no web interface either) and then I'll give it a go on an RPi4...

Same issue with RPi 4 1GB and RPi 3 B+.

@Tom-Neverwinter  @heytcass  Can you run hyperion manually(hyperiond -d) and paste the output here ? Sounds like a major issue but we don't see it in master.

pi@hyperion:~ $ hyperiond -d [hyperiond MAIN] <INFO> Set user data path to '/home/pi/.hyperion' [hyperiond DAEMON] <DEBUG> <PythonInit.cpp:45:PythonInit()> Initializing Python interpreter [hyperiond SettingsManager] <DEBUG> <SettingsManager.cpp:108:SettingsManager()> Settings database initialized [hyperiond EFFECTFILES] <INFO> 39 effects loaded from directory :/effects/ [hyperiond EFFECTFILES] <INFO> 22 effect schemas loaded from directory :/effects/schema/ [hyperiond EFFECTFILES] <INFO> 0 effects loaded from directory /home/pi/.hyperion/custom-effects [hyperiond SettingsManager] <DEBUG> <SettingsManager.cpp:108:SettingsManager()> Settings database initialized [hyperiond BLACKBORDER] <DEBUG> <BlackBorderProcessor.cpp:65:handleSettingsUpdate()> Set mode to: default [hyperiond ComponentRegister] <DEBUG> <ComponentRegister.cpp:36:setNewComponentState()> Blackborder detector: enabled [hyperiond DAEMON] <INFO> set screen capture device to 'dispmanx' [hyperiond DISPMANXGRABBER] <DEBUG> <Grabber.cpp:34:setVideoMode()> Set videomode to 0 [hyperiond DISPMANXGRABBER] <INFO> Display opened with resolution: 4x1053347956 [hyperiond DISPMANXGRABBER] <DEBUG> <Grabber.cpp:83:setWidthHeight()> Set new width: 80, height: 45 for capture [hyperiond DAEMON] <INFO> DISPMANX frame grabber created [hyperiond V4L2:auto] <DEBUG> <Grabber.cpp:34:setVideoMode()> Set videomode to 0 [hyperiond LEDDEVICE] <INFO> LedDevice 'file' found. [hyperiond ComponentRegister] <DEBUG> <ComponentRegister.cpp:36:setNewComponentState()> Smoothing: enabled [hyperiond FLATBUFCONNECTION] <INFO> Connecting to Hyperion: <IP_ADDRESS>:19401 [hyperiond EFFECTENGINE] <INFO> Run effect "Rainbow swirl fast" on channel 0 [hyperiond EFFECTENGINE] <DEBUG> <EffectEngine.cpp:183:runEffectScript()> Start the effect: name [Rainbow swirl fast], smoothCfg [2] [hyperiond HYPERION] <DEBUG> <PriorityMuxer.cpp:158:registerInput()> Register new input 'System/EFFECT' with priority 0 as inactive [hyperiond HYPERION] <INFO> Initial foreground effect 'Rainbow swirl fast' started [hyperiond EFFECTENGINE] <INFO> Run effect "Warm mood blobs" on channel 254 [hyperiond EFFECTENGINE] <DEBUG> <EffectEngine.cpp:183:runEffectScript()> Start the effect: name [Warm mood blobs], smoothCfg [2] [hyperiond HYPERION] <DEBUG> <PriorityMuxer.cpp:158:registerInput()> Register new input 'System/EFFECT' with priority 254 as inactive [hyperiond HYPERION] <INFO> Inital background effect 'Warm mood blobs' started [hyperiond HYPERION] <DEBUG> <PriorityMuxer.cpp:158:registerInput()> Register new input 'System/GRABBER' with priority 250 as inactive [hyperiond ComponentRegister] <DEBUG> <ComponentRegister.cpp:36:setNewComponentState()> Framegrabber: enabled [hyperiond BOBLIGHT] <DEBUG> <BoblightServer.cpp:28:BoblightServer()> Instance created [hyperiond ComponentRegister] <DEBUG> <ComponentRegister.cpp:36:setNewComponentState()> LED device: enabled [hyperiond HYPERION] <DEBUG> <PriorityMuxer.cpp:198:setInput()> Priority 254 is now active [hyperiond HYPERION] <DEBUG> <PriorityMuxer.cpp:333:setCurrentTime()> Set visible priority to 0 [hyperiond HYPERION] <DEBUG> <PriorityMuxer.cpp:238:setInputImage()> Priority 0 is now active Killed
"Killed" happened on its own with no input from me. Also made sure I tried loading frontend before it was killed, still nothing.

@heytcass Thanks for the logs. Unfortunately right now they don't seem to tell anything. My suggestion would be waiting a bit until Alpha7 is released(pretty soon I assume) and to see if we can reproduce it. Even if it is not resolved with Alpha7, it will hopefully tell us more about the reason of the problem you experience.
PS: I also can provide a release from latest master if you are eager to try before release.

Hi Guys,
OK so confirmed with both a Pi Model 3 B+ and a 2GB Pi 4 using PiOS Lite, PiOS Full and PiOS 64bit...
@m-seker - Are we the first people to have this issue or have you seen it from anywhere else? If it's just us then there must be something that we're doing that is different or causing the issue, no?
Cheers
Bassfiend / Phil Harris

@Bassfiend Makes me wonder if there has been something updated recently that broke something since we're all running apt update and upgrade now.

@m-seker I wouldn't mind giving the master build a go, maybe it can help clear something up before Alpha 7 comes out?

@heytcass  Perfect. You can try the following :
https://wetransfer.com/downloads/ccbd91ea3628703225bb634d40362c9a20200722131828/69ba2e0b42783ce6b115cd405e0cb19e20200722131909/9cf55f
It should hopefully print more detailed logs. Size of the file is a bit on the bigger size(116MB) since it includes debug symbols. I may ask you to run hyperion with gdb unless we find something useful in the logs.

Btw looking again, it doesn't look like a crash. We should probably have seen SIGABRT or SIGSEGV. Killed means someone is killing it, unless we are sending SIGKILL from within Hyperion, which is not the case.

@Bassfiend Makes me wonder if there has been something updated recently that broke something since we're all running apt update and upgrade now.

@heytcass - OK - I'll try it without an upgrade pass...
Hmmm ... installed clean OS but DIDN'T do the update pass and i get the web config page coming up so it seems to be linked to the latest Pi update.

I was able to get the web interface to load with an apt update/upgrade pass, until I rebooted, and that killed the page. So the issue seems to be with the reboot.

Ah ha! Seems to be a memory issue. This is on my RPi 4 1GB. Ran dmesg immediately after a reboot, on a fresh PiOS Lite image, where Hyperion is the only thing running.
pi@raspberrypi:~ $ dmesg | grep hyperion
[   70.224839] [    558]  1000   558   240328   173278  1761280    24379             0 hyperiond
[   70.224857] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=hyperiond,pid=558,uid=1000
[   70.224900] Out of memory: Killed process 558 (hyperiond) total-vm:961312kB, anon-rss:693112kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:1720kB oom_score_adj:0
[   70.299315] oom_reaper: reaped process 558 (hyperiond), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
[  123.297533] [    576]  1000   576   266728   203026  1982464    22495             0 hyperiond
[  123.297545] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=hyperiond,pid=576,uid=1000
[  123.297665] Out of memory: Killed process 576 (hyperiond) total-vm:1066912kB, anon-rss:812104kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:1936kB oom_score_adj:0
[  123.435979] oom_reaper: reaped process 576 (hyperiond), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
[  157.848691] [    587]  1000   587   227920   162093  1646592    22467             0 hyperiond
[  157.848715] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=hyperiond,pid=587,uid=1000
[  157.848801] Out of memory: Killed process 587 (hyperiond) total-vm:911680kB, anon-rss:648372kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:1608kB oom_score_adj:0
[  157.984240] oom_reaper: reaped process 587 (hyperiond), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
[  192.571557] hyperiond invoked oom-killer: gfp_mask=0x400dc2(GFP_KERNEL_ACCOUNT|__GFP_HIGHMEM|__GFP_ZERO), order=0, oom_score_adj=0
[  192.571567] CPU: 1 PID: 601 Comm: hyperiond Tainted: G         C        5.4.51-v7l+ #1326
[  192.572083] [    601]  1000   601   215281   149231  1540096    22047             0 hyperiond
[  192.572126] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=hyperiond,pid=601,uid=1000
[  192.572174] Out of memory: Killed process 601 (hyperiond) total-vm:861124kB, anon-rss:596672kB, file-rss:252kB, shmem-rss:0kB, UID:1000 pgtables:1504kB oom_score_adj:0
[  192.648442] oom_reaper: reaped process 601 (hyperiond), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

@Bassfiend Can you do the same on your 2GB model?
cc: @m-seker

@heytcass - Will do ... just going to run the following through:
For each of 3B+, 4 2GB and 4 4GB....

Fresh "Lite" install
Install Hyperion
Reboot
Confirm web interface still exists
Update
Confirm web interface still exists
Reboot
Confirm web interface still exists

I checked my Pi4 2GB, hyperion uses around 1.3Gb, so we figured the root cause, now time to figure out how we can decrease it.

@m-seker Interesting. Especially because according to @Bassfiend 's comment here it didn't work on his 2Gb model. I am also very curious about how Dr Zzs ever got it working on his Pi 3 in the video linked in the original post.
Also a shame that I have a big Amazon delivery today with a splitter, LEDs, etc that I'm going to have to explain to my wife, without being able to use it as a justification immediately. 😂 Also would rather not burn my 8GB Pi just for running Hyperion. Hmmm...

Odd that it runs fine, surviving reboots UNTIL you do an apt-get update / apt-get upgrade / reboot pass though...
I've checked this so far on my 3B+ and rebooting the Pi is fine UNTIL you do the update then on the next reboot it stops working!
If you've found the cause then is it worth me testing further?
@heytcass - I get no results from "dmesg | grep hyperion"...

@Bassfiend Even after the reboot?

@heytcass - I reckon there's something very recent slipped into the OS update which wasn't there a couple of days ago when he did the recording.
@heytcass - Yup - even after the reboot...

Just rebooted 3B+ again before running update ...
pi@raspberrypi:~ $ dmesg | grep hyperion
[    3.453717] systemd[1]: Created slice system-hyperiond.slice.
pi@raspberrypi:~ $

@heytcass No worries just stall your wife while we are investigating it :D

@heytcass - I reckon that's @m-seker offering to buy dinner... ;-)

Right - now the 2GB Pi4...
Fresh "Lite" install
wget https://github.com/hyperion-project/hyperion.ng/releases/download/2.0.0-alpha.6/Hyperion-2.0.0-alpha.6-Linux-armv7l.deb
sudo dpkg -i Hyperion-2.0.0-alpha.6-Linux-armv7l.deb
Web interface up and running.
dmesg | grep hyperion
pi@raspberrypi:~ $ dmesg | grep hyperion
pi@raspberrypi:~ $
run sudo reboot
Web interface still working.
pi@raspberrypi:~ $ dmesg | grep hyperion
[ 3.453717] systemd[1]: Created slice system-hyperiond.slice.
pi@raspberrypi:~ $
run sudo apt-get update / sudo apt-get upgrade
Web interface still working
sudo reboot
No more web interface
login as: pi
<EMAIL_ADDRESS>password:
Linux raspberrypi 5.4.51-v7l+ #1326 SMP Fri Jul 17 10:51:18 BST 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jul 22 16:27:07 2020 from <IP_ADDRESS>
SSH is enabled and the default password for the 'pi' user has not been changed.
This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.
pi@raspberrypi:~ $ dmesg | grep hyperion
pi@raspberrypi:~ $
So on the Pi4 2GB I'm no longer seeing anything from hyperion with the dmesg | grep hyperion command...

@Bassfiend can you try with the binary I uploaded above ?

@Bassfiend can you try with the binary I uploaded above ?

I'll try - I'm a Windows boy though so I haven't a bloody clue how to find anything in the filesystem of a Pi!

@Bassfiend In the last release there were problems with the V4L2 grabber. (new BCM2835 ISP Device) As a result, the WebUI was no longer accessible. But these have already been fixed.
More information here: https://github.com/hyperion-project/hyperion.ng/issues/819

@Bassfiend In the last release there were problems with the V4L2 grabber. (new BCM2835 ISP Device) As a result, the WebUI was no longer accessible. But these have already been fixed.
More information here: #819

Erm - thanks - don't think this is anything to do with what we're seeing here though...
Phil

@Bassfiend
Hyperion scans the system for cameras to make them available in the WebUI. In the last release there was no new BCM2835 ISP driver. The RPi upgrade only came afterwards. Hyperion was stuck in a loop, making the WebUI unreachable. Just test the @ m-seker build. thank you

@Bassfiend
Hyperion scans the system for cameras to make them available in the WebUI. In the last release there was no new BCM2835 ISP driver. The RPi upgrade only came afterwards. Hyperion was stuck in a loop, making the WebUI unreachable. Just test the @m-seker build. thank you

So when you say "last release" do you mean of Hyperion or of the PiOS update / upgrade package?
I'll try to use the file @m-seker linked to but I am not a Linux person I'm afraid so finding my way round the Linux filesystem is like bumbling around a maze in the dark - I have it copied to my root though and I'll try installing it in a minute as soon as I have finished confirming the same on a 4GB Pi4...
P

@m-seker @Paulchen-Panther @Bassfiend Working on flashing the new build now.

@Bassfiend No panic. The new Alpha 7 is not long in coming

@Bassfiend No panic. The new Alpha 7 is not long in coming

Thanks - I'll try to use the file if I can work it out ... be good to get it quashed before the next public upload. :-)

@Bassfiend
Hyperion scans the system for cameras to make them available in the WebUI. In the last release there was no new BCM2835 ISP driver. The RPi upgrade only came afterwards. Hyperion was stuck in a loop, making the WebUI unreachable. Just test the @m-seker build. thank you

So when you say "last release" do you mean of Hyperion or of the PiOS update / upgrade package?
I'll try to use the file @m-seker linked to but I am not a Linux person I'm afraid so finding my way round the Linux filesystem is like bumbling around a maze in the dark - I have it copied to my root though and I'll try installing it in a minute as soon as I have finished confirming the same on a 4GB Pi4...
P

You don't need to install it. Just extract the archive and run the binary inside bin/

./hyperiond: error while loading shared libraries: libcec.so.4: cannot open shared object file: No such file or directory

sudo apt-get install libcec-dev

Ah. The "-dev" is what I was missing. Thanks.

./hyperiond: error while loading shared libraries: libGLdispatch.so.0: cannot open shared object file: No such file or directory
Is it looking for an X server? Is the fact that I'm on PiOS Lite an issue?

Hyperion Server OS:

Distribution: Raspbian GNU/Linux 10 (buster)
Arch:         arm
Kernel:       linux (5.4.51-v7+ (WS: 32))

have no issues.... will test with a 1b too

I’d best leave it till the Alpha pops up as I don’t know enough command line Linux not to be a liability going forward ... meddle not in the affairs of dragons if thou art crunchy and taste good with ketchup. 😜

Don't know why I didn't think of this until now, but here is the list of things getting upgraded with apt:

pi@hyperion:~ $ apt list --upgradable
Listing... Done
ca-certificates/stable 20200601~deb10u1 all [upgradable from: 20190110]
firmware-atheros/testing 1:20190114-1+rpt7 all [upgradable from: 1:20190114-1+rpt6]
firmware-brcm80211/testing 1:20190114-1+rpt7 all [upgradable from: 1:20190114-1+rpt6]
firmware-libertas/testing 1:20190114-1+rpt7 all [upgradable from: 1:20190114-1+rpt6]
firmware-misc-nonfree/testing 1:20190114-1+rpt7 all [upgradable from: 1:20190114-1+rpt6]
firmware-realtek/testing 1:20190114-1+rpt7 all [upgradable from: 1:20190114-1+rpt6]
libgnutls30/stable 3.6.7-4+deb10u4 armhf [upgradable from: 3.6.7-4+deb10u3]
libraspberrypi-bin/testing 1.20200717-1 armhf [upgradable from: 1.20200512-2]
libraspberrypi-dev/testing 1.20200717-1 armhf [upgradable from: 1.20200512-2]
libraspberrypi-doc/testing 1.20200717-1 armhf [upgradable from: 1.20200512-2]
libraspberrypi0/testing 1.20200717-1 armhf [upgradable from: 1.20200512-2]
raspberrypi-bootloader/testing 1.20200717-1 armhf [upgradable from: 1.20200512-2]
raspberrypi-kernel/testing 1.20200717-1 armhf [upgradable from: 1.20200512-2]
raspi-config/testing 20200707 all [upgradable from: 20200515]
rpi-eeprom-images/testing 7.8-1 all [upgradable from: 7.0-1]
rpi-eeprom/testing 7.8-1 all [upgradable from: 7.0-1]

Anything suspicious in there?

@heytcass
Please test this (armv6hf) artefact:  https://github.com/hyperion-project/hyperion.ng/actions/runs/177653687

Same issue here on a fresh raspbian install on a Pi 3 B+ seems to run out of memory in all instances for me 😢 I did an apt-get upgrade before installing hyperion too.
@Paulchen-Panther just tried the armv7 artifact from that build and it looks like it solved it for me, it's no longer crashing and can get into the web ui!

2020-07-22T20:33:49.388 hyperiond DAEMON       :  The dispmanx framegrabber can not be instantiated, because it has been left out from the build

Are you sure you took an arm packet?

Yeah, I downloaded armv7hf.zip & unpacked to Hyperion-2.0.0-alpha.6-PR#894-Linux-armv7l

Ok. I'm just looking at what it is.

Hyperion mostly seems to be working, but it's the first time I've set it up & used it. Looks like my video 2 USB grabber is working & hyperion is picking up the video stream.
Only issue I've got is that the entertainment area is configured & apparently streaming but the lights are unresponsive 😢 Guessing it might be an unrelated issue but just an FYI

Oh actually ignore the entertainment issue, looks like they are working, just really dim.

Problem for deactivated DispmanX Grabber found. Fix is comming

Has this been resolved? I just saw an update on the latest release. Just wondering as I'm still running using the build you linked to & not a proper release.

Has this been resolved?

Yes. Please use official alpha 7 release to test

@Paulchen-Panther schliessen?

@Paulchen-Panther schliessen?

Ja


Upload config not working

We try to use thi interface and the upload config seems to not working correctly

Show me apache error logs, please

[Tue May 08 10:42:36.161348 2018] [cgi:error] [pid 1479] [client <IP_ADDRESS>:33212] AH01215: dos2unix: converting file /var/www/haproxy-wi/configs/hap_config/<IP_ADDRESS>-2018-05-08.08:42:36.cfg to Unix format ..., referer: http://haprox-wi.example.com:8080/app/config.py?serv=<IP_ADDRESS>&open=open
[Tue May 08 10:46:10.895952 2018] [cgi:error] [pid 14632] [client <IP_ADDRESS>:33382] AH01215: dos2unix: converting file /var/www/haproxy-wi/configs/hap_config/<IP_ADDRESS>-2018-05-08.08:17:42.cfg to Unix format ..., referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:46:11.904054 2018] [cgi:error] [pid 14632] [client <IP_ADDRESS>:33382] AH01215: Traceback (most recent call last):, referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:46:11.904133 2018] [cgi:error] [pid 14632] [client <IP_ADDRESS>:33382] AH01215:   File "/var/www/haproxy-wi/app/configver.py", line 65, in , referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:46:11.904198 2018] [cgi:error] [pid 14632] [client <IP_ADDRESS>:33382] AH01215:     stderr, error = funct.upload_and_restart(serv, configver, just_save=save), referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:46:11.904240 2018] [cgi:error] [pid 14632] [client <IP_ADDRESS>:33382] AH01215: ValueError: too many values to unpack (expected 2), referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:48:19.598643 2018] [cgi:error] [pid 1154] [client <IP_ADDRESS>:33436] AH01215: dos2unix: converting file /var/www/haproxy-wi/configs/hap_config/<IP_ADDRESS>-2018-05-08.08:17:42.cfg to Unix format ..., referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:48:20.294090 2018] [cgi:error] [pid 1154] [client <IP_ADDRESS>:33436] AH01215: Traceback (most recent call last):, referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:48:20.294171 2018] [cgi:error] [pid 1154] [client <IP_ADDRESS>:33436] AH01215:   File "/var/www/haproxy-wi/app/configver.py", line 65, in , referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:48:20.294218 2018] [cgi:error] [pid 1154] [client <IP_ADDRESS>:33436] AH01215:     stderr, error = funct.upload_and_restart(serv, configver, just_save=save), referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg
[Tue May 08 10:48:20.294265 2018] [cgi:error] [pid 1154] [client <IP_ADDRESS>:33436] AH01215: ValueError: too many values to unpack (expected 2), referer: http://haprox-wi.example.com:8080/app/configver.py?serv=<IP_ADDRESS>&open=open&configver=<IP_ADDRESS>-2018-05-08.08:17:42.cfg

Overwrite this file with the original in the folder app/
configver.zip

Disable firewall configure in config file
Отправлено из Mail.Ru для Android вторник, 08 мая 2018г., 15:24 +06:00 от Luxiter<EMAIL_ADDRESS>:

now on upload i've this error
Some errors:
b'\x1b[91mFirewallD is not running\x1b[00m\n'
firewalld is mandatory ?
—
You are receiving this because you commented.
Reply to this email directly,  view it on GitHub , or  mute the thread .

Some errors:
b"[ALERT] 127/113247 (1793) : parsing [/tmp//2018-05-08.09:32:47.cfg:42] : 'server <IP_ADDRESS>:80' : could not resolve address 'check'.\n[ALERT] 127/113247 (1793) : Failed to initialize server(s) addr.\n"
but the port 80 is active
tcp        0      0 <IP_ADDRESS>:8085            <IP_ADDRESS>:*               LISTEN      873/haproxy
tcp6       0      0 :::80                   :::*                    LISTEN      1762/httpd
tcp6       0      0 :::8080                 :::*                    LISTEN      1762/httpd
tcp6       0      0 <IP_ADDRESS>:80      <IP_ADDRESS>:50036     TIME_WAIT   -
tcp6       0      0 <IP_ADDRESS>:80      <IP_ADDRESS>:50038     TIME_WAIT   -

This error return haproxy, becouse in your config have error
Отправлено из Mail.Ru для Android вторник, 08 мая 2018г., 15:37 +06:00 от Luxiter<EMAIL_ADDRESS>:

Some errors:
b"[ALERT] 127/113247 (1793) : parsing [/tmp//2018-05-08.09:32:47.cfg:42] : 'server <IP_ADDRESS>:80' : could not resolve address 'check'.\n[ALERT] 127/113247 (1793) : Failed to initialize server(s) addr.\n"
but the port 80 is active
tcp        0      0 <IP_ADDRESS>:8085            <IP_ADDRESS>:*               LISTEN      873/haproxy
tcp6       0      0 :::80                   :::*                    LISTEN      1762/httpd
tcp6       0      0 :::8080                 :::*                    LISTEN      1762/httpd
tcp6       0      0 <IP_ADDRESS>:80      <IP_ADDRESS>:50036     TIME_WAIT   -
tcp6       0      0 <IP_ADDRESS>:80      <IP_ADDRESS>:50038     TIME_WAIT   -
—
You are receiving this because you commented.
Reply to this email directly,  view it on GitHub , or  mute the thread .

ok now working fine


[WIP] ONNX export: Random uniform, Random normal

Description
ONNX export plus test for Random Uniform and Random Normal.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-label-bot add [ONNX, pr-work-in-progress]

@mxnet-label-bot update [ONNX, pr-awaiting-review]


feat: support new sepolia testnet [APE-1487]

What I did

fixes: #
How I did it
How to verify it
Checklist

[x] Passes all linting checks (pre-commit and CI jobs)
[x] New test cases have been added and are passing
[ ] Documentation has been updated
[x] PR title follows Conventional Commit standard (will be automatically included in the changelog)

related: https://github.com/ApeWorX/ape-etherscan/pull/105

related: https://github.com/ApeWorX/ape-infura/pull/66


Try out other English embedding models

Description:

Problem:
We are currently using fasttext, which is good for OOV words, but it's a bit slow and old (2015-2020). There might be better models available.

Solution:
Check out the leaderboard: https://huggingface.co/spaces/mteb/leaderboard and try out models that aren't too large.

Prerequisites:
[List any requirements or dependencies needed before starting.]

Tasks:

Try out newer embedding models and evaluate them.

Additional context
Add any other context or screenshots about the feature request here.

https://www.sbert.net/docs/sentence_transformer/pretrained_models.html#semantic-search
FastText has many languages support, preferably we find a model that has more than 5 languages support. We can offer some accuracy if the speed increases.

https://huggingface.co/BAAI/bge-m3

FastText: Word vectors for 157 languages

https://huggingface.co/intfloat/multilingual-e5-small: all scores are between 0.7 and 1.0 which means we need to find a method to scale it back to something more useful for us


ADS pops-up Firewall rule dialog when adding Azure account

Azure Data Studio Version: release/1.17

Steps to Reproduce:

Add a Azure Account

Expected: No OS pop-ups
Actual: Windows asks for Firewall permissions.

@aaomidi could you please take a look at this?  I don't recall seeing this before and assume it's related to the localhost redirect.  Perhaps we're opening an externally visible port vs. on the loopback IP?  If we're using loopback (non-externally visible port) we should see this OS pop-up I think.

@kburtram this was a mistake on my part, should be fixed now.

Fix is merged into release branch.


feat(targets): Accept overrides from callers to askFor methods

Need to test interactions with generated gulp tasks from https://github.com/thaiat/generator-sublime before merging.

Looks like This does not collide with generated tasks. Waiting for :shipit: to merge.

@thaiat Can you take a look again? some of the complication for dealing with the opts.target came from the fact that I was trying to use logic that would work for both an array and a string, so I just ended up using [].concat() to make sure I got an array.

ok you can merge


Improve logging - individual filters

Ping. Any other feedback?

🆙 📅 @pranavkm, I addressed your feedback (check last 2 commits)

🚢 :it:

c8cabde1f16980e8596f31b697786b049bd9d997


Newrelic 9.10.0 breaks our CI - caused by a collision with the 'bootstrap' gem

Description
On a dependabot PR for the new version of the agent, all GitHub Action CI steps fail with the following error:
New Relic entrypoint at /home/runner/work/human-essentials/human-essentials/vendor/bundle/ruby/3.2.0/gems/newrelic_rpm-9.10.0/lib/bootstrap.rb encountered an issue:
	/home/runner/work/human-essentials/human-essentials/vendor/bundle/ruby/3.2.0/gems/newrelic_rpm-9.10.0/lib/bootstrap.rb is meant to be required via the RUBYOPT env var

No previous versions caused these errors.
Sample run: https://github.com/rubyforgood/human-essentials/actions/runs/9297054369/job/25667726353
Expected Behavior
No crashes!
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):

Hi @dorner,
Sorry to hear that the new agent version is causing this problem. That bootstrap.rb file is new in v9.10.0 and is meant only to be used with some experimental new use cases. And conversely it is designed to be invisible to all existing use cases (shouldn't be read or required by anything) and in fact will complain as you've seen if it was loaded in an unexpected way.
We didn't expect your use case to load bootstrap.rb, but somehow it was loaded.
From looking at your failed run, it looks like that job only does 2 things:

bundle exec rake db:create
bundle exec rake db:schema:load

Using a Rails v7.1 based app, I bundled the New Relic Ruby agent v9.10 and performed those commands and didn't see the same problem. I tried both with a non-existent database that needed to be created and against an existing database.
Is it possible that your app is engaging some other code when those rake tasks are performed? Are you aware of anything that might be globbing up all .rb files and calling load or require on them?
We will keep investigating regardless, but if you could provide us with some reproduction steps that would be helpful. Perhaps the steps could start with rails new and go from there.
If we need to, we can rework bootstrap.rb to not perform exit, but we'd like to first better understand how you reached that line.

Is it possible that there is some conflict with the bootstrap gem? We have that in our Gemfile. I'm wondering if a require "bootstrap" is somehow getting confused and grabbing your file.
I don't see any instance of load or require that seems to be working on individual files inside gems.
Btw this is an open source / non-profit application, so you are free to clone it yourself! https://github.com/rubyforgood/human-essentials/

Ah, thanks, @dorner. Having bootstrap listed in Gemfile does indeed seem necessary to reproduce the problem. We can repro now.
My hypothesis: the New Relic gem's lib/ dir and the bootstrap gem's lib/ dir are both in the Ruby lib path and when require 'bootstrap' is performed, Ruby is finding our lib/bootstrap.rb file first and hitting our file's exit.
We'll work on a fix that could involve renaming bootstrap.rb, relocating it to anywhere but the root of lib, silently returning instead of calling warn and exit, or a combination of these.
For now, I consider v9.10 to have broken compatibility with the bootstrap gem. Users of the bootstrap gem will need to pin the New Relic Ruby agent v9.9 until we can publish a fix.
Thanks very much for reporting this and for your patience with us. And thanks so much for your Ruby for Good efforts.

@dorner I have created PR #2676 to fix the issue. It will need to be reviewed and approved by the other project maintainers before it can make its way into a new release.
If you would like to test the fix prior to it making its way out into a published gem release, you can reference this repo's "bootstrap" branch like so:
# Gemfile

gem 'newrelic_rpm',
  github: 'newrelic/newrelic-ruby-agent',
  branch: 'bootstrap'

You are of course welcome to simply stay on agent v9.9.0 if you'd prefer.
Either way, we'll be sure to post an update here once the fix makes its way out to RubyGems.
Thanks again for the bug report!

@fallwith
Just FYI.
My project faced with the same situation as dorner's, and it solved with your "bootstrap" branch.
Thank you for quick fix!
Also, Thank you for reporting this, dorner. 👏

Amazing, thanks so much for the prompt response and fix!

The fix has been merged. We'll post another update here once a new release has been pushed to RubyGems.org.

@dorner @juno @marlo-longley Version v9.10.1 of the New Relic Ruby agent has now been released to RubyGems.org. All bootstrap users should now able to upgrade past v9.9.0 by going with v9.10.1. Thanks again!

Awesome!

cc @sidane, @aseroff, @thestelz v9.10.1 is now available with the fix


new TimberPost();  - Custom post type

hi, how can i get Custom post type?
something like that : $twigcontent['post'] = new TimberPost();

Hi there! Sorry to hear you're having issues (but glad you're giving Timber a try!) We try to keep GitHub clear for just bugs with the Timber code itself. For questions like this, please post to the StackOverflow channel:
http://stackoverflow.com/questions/tagged/timber
... I'll try to follow-up there if there's an answer I can provide

but this is bug, i cant do this!

@lupik2 if it's a bug please fill out the complete Bug Reporting template you see when creating a new issue. That's the only way I can work to verify what you're experiencing


bug: Not found WasmEdge-plugin-wasmedge_rustls-0.14.0-darwin_arm64.tar.gz

Summary
INFO    - Downloading Plugin: wasmedge_rustls
ERROR   - Download error from urllib: HTTP Error 404: Not Found
ERROR   - URL: https://github.com/WasmEdge/WasmEdge/releases/download/0.14.0/WasmEdge-plugin-wasmedge_rustls-0.14.0-darwin_arm64.tar.gz
Reproduction steps
run
curl -sSf https://raw.githubusercontent.com/WasmEdge/WasmEdge/master/utils/install.sh | bash -s -- --plugin wasi_nn-ggml wasmedge_rustls

got
INFO    - Downloading Plugin: wasmedge_rustls
ERROR   - Download error from urllib: HTTP Error 404: Not Found
ERROR   - URL: https://github.com/WasmEdge/WasmEdge/releases/download/0.14.0/WasmEdge-plugin-wasmedge_rustls-0.14.0-darwin_arm64.tar.gz

workaround: remove wasmedge_rustls
curl -sSf https://raw.githubusercontent.com/WasmEdge/WasmEdge/master/utils/install.sh | bash -s -- --plugin wasi_nn-ggml

Screenshots

Any logs you want to share for showing the specific issue
No response
Model Information
any
Operating system information
macOS 14.5
ARCH
arm64
CPU Information
m3 max
Memory Size
64GB
GPU Information
metal
VRAM Size
64GB

We made some changes to how TLS works in 0.14. I think you can stick with 0.13 at this moment.
curl -sSf https://raw.githubusercontent.com/WasmEdge/WasmEdge/master/utils/install.sh | bash -s -- -v 0.13.5 --plugin wasi_nn-ggml wasmedge_rustls

Also, where did you get the install command? We'd like to update it to use 0.13.5 for now. Thanks.

I'm now using
bash <(curl -sSfL 'https://raw.githubusercontent.com/LlamaEdge/LlamaEdge/main/run-llm.sh')

and get
[+] Installing WasmEdge with wasi-nn_ggml plugin ...

Info: Detected Darwin-arm64

Info: WasmEdge Installation at /Users/katopz/.wasmedge

Info: Fetching WasmEdge-0.13.5

/tmp/wasmedge.30301 ~/git/rag-api-server
~/git/rag-api-server
Info: Fetching WasmEdge-GGML-Plugin

Info: Detected CUDA version:

Info: CUDA version from nvcc:

Info: CUDA version from nvidia-smi:

Info: Use default GGML plugin

/tmp/wasmedge.30301 ~/git/rag-api-server
~/git/rag-api-server
Info: Fetching WasmEdge-Rustls-Plugin

/tmp/wasmedge.30301 ~/git/rag-api-server
~/git/rag-api-server
Installation of wasmedge-0.13.5 successful
WasmEdge binaries accessible

    The WasmEdge Runtime is installed in /Users/katopz/.wasmedge/bin/wasmedge.

[+] Using cached model gemma-2b-it-Q5_K_M.gguf
[+] Downloading the latest llama-api-server.wasm ...

[+] Downloading Chatbot web app ...

[+] Will run the following command to start the server:

    wasmedge --dir .:. --nn-preload default:GGML:AUTO:gemma-2b-it-Q5_K_M.gguf llama-api-server.wasm -p gemma-instruct -c 4096 --model-name gemma-2b-it --socket-addr <IP_ADDRESS>:8080 --log-prompts --log-stat

    Chatbot web app can be accessed at http://<IP_ADDRESS>:8080 after the server is started

*********************************** LlamaEdge API Server ********************************

[2024-05-28 16:36:49.162] [error] instantiation failed: module name conflict, Code: 0x60
[2024-05-28 16:36:49.162] [error]     At AST node: module

[INFO] LlamaEdge version: 0.11.2
[INFO] Model names: gemma-2b-it
[INFO] Context size: 4096
[INFO] Batch size: 512
[INFO] Prompt template: gemma-instruct
[INFO] Number of tokens to predict: 1024
[INFO] Number of layers to run on the GPU: 100
[INFO] Temperature for sampling: 1
[INFO] Top-p sampling (1.0 = disabled): 1
[INFO] Penalize repeat sequence of tokens: 1.1
[INFO] Presence penalty (0.0 = disabled): 0
[INFO] Frequency penalty (0.0 = disabled): 0
[INFO] Enable prompt log: true
[INFO] Enable plugin log: true
[INFO] Socket address: <IP_ADDRESS>:8080
[2024-05-28 16:36:49.231] [info] [WASI-NN] GGML backend: LLAMA_COMMIT 95fb0aef
[2024-05-28 16:36:49.231] [info] [WASI-NN] GGML backend: LLAMA_BUILD_NUMBER 2963
[2024-05-28 16:36:49.245] [error] [WASI-NN] llama.cpp: llama_model_load: error loading model: tensor 'blk.10.ffn_down.weight' data is not within the file bounds, model is corrupted or incomplete
[2024-05-28 16:36:49.245] [error] [WASI-NN] llama.cpp: llama_load_model_from_file: failed to load model
[2024-05-28 16:36:49.245] [error] [WASI-NN] GGML backend: Error: unable to init model.

@apepkuss
Could you check if the gemma-2b series needs to be regenerated with the b2963 llama.cpp?
This error is due to the gguf model is not compatible with the newer one.

@katopz Could you please manually download the model and check if the downloaded file is correct? I found that we have a CI using the same model and the same plugin version, but it works fine. Ref: https://github.com/second-state/WasmEdge-WASINN-examples/actions/runs/9265541716/job/25487794530#step:7:4

@katopz Could you please manually download the model and check if the downloaded file is correct? I found that we have a CI using the same model and the same plugin version, but it works fine. Ref: https://github.com/second-state/WasmEdge-WASINN-examples/actions/runs/9265541716/job/25487794530#step:7:4

Working now with some error at the top, Thanks.
*********************************** LlamaEdge API Server ********************************

[2024-05-28 17:40:48.542] [error] instantiation failed: module name conflict, Code: 0x60
[2024-05-28 17:40:48.542] [error]     At AST node: module

[INFO] LlamaEdge version: 0.11.2
[INFO] Model names: gemma-2b-it

Will close issue for now.


Uploaded Scripts for Atom Count Frequency Tests

Description
Provide a brief description of the PR's purpose here.
Todos
Notable points that this PR has either accomplished or will accomplish.

[ ] TODO 1

Questions

[ ] Question1

Status

[ ] Ready to go

@iBessonob
This looks good overall although there is an issue with the atom count. When going from smiles to oemol you need to make sure you are adding explicit hydrogens.
Here is an example of a function you should use for going to smiles to oemol. It should affect the number of atoms -
def smiles2oemol(smiles):
    mol = OEMol()
    OESmilesToMol(mol, smiles)
    # Initialize Omega
    omega = oeomega.OEOmega()
    omega.SetMaxConfs(1)
    omega.SetIncludeInput(True)
    omega.SetCanonOrder(True)
    omega.SetSampleHydrogens(True)  # Word to the wise: skipping this step can lead to significantly different charges!
    omega.SetStrictStereo(True)
    omega.SetStrictAtomTypes(True)
    omega.SetIncludeInput(False) # don't include input
    status = omega(mol)
    ofs = oechem.oemolostream("test.mol2")
    oechem.OEWriteMolecule(ofs, mol)
    return mol
smiles2oemol('CNC')```

@danieljcabrera Can you review this PR as well and give any feedback when you are available

@iBessonob
This looks good overall although there is an issue with the atom count. When going from smiles to oemol you need to make sure you are adding explicit hydrogens.
Here is an example of a function you should use for going to smiles to oemol. It should affect the number of atoms -
def smiles2oemol(smiles):
    mol = OEMol()
    OESmilesToMol(mol, smiles)
    # Initialize Omega
    omega = oeomega.OEOmega()
    omega.SetMaxConfs(1)
    omega.SetIncludeInput(True)
    omega.SetCanonOrder(True)
    omega.SetSampleHydrogens(True)  # Word to the wise: skipping this step can lead to significantly different charges!
    omega.SetStrictStereo(True)
    omega.SetStrictAtomTypes(True)
    omega.SetIncludeInput(False) # don't include input
    status = omega(mol)
    ofs = oechem.oemolostream("test.mol2")
    oechem.OEWriteMolecule(ofs, mol)
    return mol
smiles2oemol('CNC')

@danieljcabrera can you review this PR as well and give any feedback

Everything looks good! The only change that needs to be made is the one Jessica mentioned. I would also change the last line to return mol, status. This allows you to check if the molecule was able to convert to the OEMol form. The molecules that aren't able to conform (status is False) won't provide accurate data so you should skip them. You can see how I did it here too https://github.com/dance-pipeline/dance/pull/11/commits/ddeb0dac46e36b7845e87f89f61243efce451299#diff-b806512fc85b83c5974046c36c9e72fee2804bf270db5981d605a5bc03a79f04

@iBessonob Let me know if you would like me to take a look at this PR. Also, are you familiar with using git from command line? It seems you're mainly uploading files to GitHub. I 100% recommend using git from the command line.

@iBessonob Let me know if you would like me to take a look at this PR. Also, are you familiar with using git from command line? It seems you're mainly uploading files to GitHub. I 100% recommend using git from the command line.

Thanks! Of course! I do have some git command line experience but I'm trying to save space on my macOS. I transferred my work back onto my normal laptop and git pushed to my branch from there with new changes.


HTML is sent as text/plain

When sikka block me on my website, the captcha page is sent as text/plain. It's happend on chromuim (Version 41.0.2272.76 Ubuntu 15.04 (64-bit)) and on chrome

same here did you manage to solve this?

No, I think that you should remove it... Why ?
It block googlebot, and in my case the title was: I am a Human - ful*a*h*.net because google had detected duplicate content with an other website,
I think that these solution are better but not complete;

zeroasterisk:throttle ; A secure means of limiting interactions (emails, etc)
browser-policy ; Configure security policies enforced by the browser

same here, not usable in Chrome after installing sikka.


docs: updated the docs to reflect the correct default values

fixes #52
updated the docs to reflect the correct default values

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


19-06-2017 : Facing suddenly indexerror: list index out of range even after upgrading to fbchat 0.9.3

Hi I m facing this issue even after upgrading to 0.9.3
I m providing ph no in place of FRIEND'S NAME in client.getUsers("FRIEND'S NAME") . It was working fine till day before yesterday. From yesterday morning, was showing this problem
https://www.facebook.com/?seq=0&__req=3
Login of<EMAIL_ADDRESS>successful.
Traceback (most recent call last):
File "facechat.py", line 62, in
friend = friends[0]
IndexError: list index out of range
What is the issue ? Did facebook change anything again? Thanks

I'm guessing Facebook changed something, can you try it on v. 1.0.1?

Closing, after no response from @gerstaro


Not working for typescript

Actually the problem is not with typescript - the problem is with rollup.
<EMAIL_ADDRESS>contains
module.exports = index;

which should be imported as import * as memoizeOne
while<EMAIL_ADDRESS>contains
export default index;

which should be imported as import memoizeOne
Result - the code for nodejs (~jest) require one behaviour, while the code for webpack(uses esm bundle) requires another.
It is not a problem for js/flow, as long babel is doing some around magic default imports, but typescript is quite strict about it.
The cjs bundle should match esm bundle.
(and fixing this would introduce a breaking change)

@TrySound thoughts?

As you mentioned @theKashey we are using rollup to generate the bundles. It sounds like there is an issue with the cjs bundle. Is there an option we can change for the rollup build...?

This is the old issue with typescript itself and default exports. My solution is getting rid from default exports in the next major release. They are quite useless.
I'm not alone.
https://github.com/jaredpalmer/formik/pull/973#issuecomment-428012717

@theKashey cjs bundle is matched to esm bundle by the way, it's typescript fault.

I've added the following function as a workaround which I call at the start of my tests:
export function ensureMemoizeOneInitialized()
{
    if (typeof memoize === "undefined")
    {
        /* tslint:disable:no-var-requires */
        (memoize as any) = require("memoize-one");
    }
}

I would be keen to find a way forward in our generated code. Ideally it would work with TS out of the box. Any thoughts @TrySound?

This is the best and not only for typescript
https://basarat.gitbooks.io/typescript/docs/tips/defaultIsBad.html

Actually there is esModuleInterop flag which fixes this behaviour in typescript similar to "magical" (it's not) babel way.

It should be default since v3 but "TS has such big ecosystem".

Could you make a PR? 🤘
On Mon, 22 Oct 2018 at 6:27 pm, Bogdan Chadkin<EMAIL_ADDRESS>wrote:

It should be default since v3 but "TS has such big ecosystem".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alexreardon/memoize-one/issues/37#issuecomment-431758469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACFN7RU3hwk_4gHF4hKLyNKm9gx3Cr9rks5unXNKgaJpZM4XT298
.

To typescript? I'm not. Users should enable it and fix all modules in DefinitelyTyped.

Or do you mean named export?

Please don't use esModuleInterop or allowSyntheticDefaultImports, it will require target consumer to set it, and this is something you shall not ask for.
PS: And also affects imports, not exports.

@theKashey That's the point. It should be default. Ecosystem is broken now. It's just doesn't work for many packages.

To typescript? I'm not. Users should enable it and fix all modules in DefinitelyTyped.
@TrySound I misunderstood you. I thought we could add a simple rollup plugin and be done with this issue

It sounds like you have some insight into this @theKashey, any thoughts on how to proceed?

Well another option is named only exports.

The best option I could provide, would be a :badjookeeee: option - rewrite memoize-one to TS, and provide .flow types in a separate, ie "revert" how it works today.
TS could generate "default" exports, understandable both by TS and JS.

@theKashey What is the point of esModuleInterop if it doesn't work with any typings at all? What for they provided broken configuration?

@theKashey It's not the best option. It's a hack for hacky ecosystem.

Flow is not opinionated and that's why it's so beautiful.

Technically -
Object.defineProperty(exports, "__esModule", {
  value: true
});

exports = memoizeOne;
exports.default = memoizeOne;

Can we add that to the cjs build?
On Wed, 24 Oct 2018 at 8:39 am, Anton Korzunov<EMAIL_ADDRESS>wrote:

Technically -
Object.defineProperty(exports, "__esModule", {
value: true
});
exports = memoizeOne;exports.default = memoizeOne;
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alexreardon/memoize-one/issues/37#issuecomment-432430437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACFN7bOnyuPoMRFOsLAqgVk_cHClZly_ks5un4yTgaJpZM4XT298
.

That could be a little problem.

Babel moved from this hack two major versions ago.

I'm running into this problem as well. Not sure if it's TypeScript per-se or Jest.
But the crux of it is that the CJS module needs to include a named export called "default". Pretty much like @theKashey showed.
I think that would fix it.

Just tried. Can't be done. (Seriously rollup?) Default exports were such a fuckup. :(
I think the only way out is to release a new major version that breaks the way CJS currently works and forces it to use require('memoize').default. I'll make a PR.

@hlolli you can use https://npmjs.org/package/@stoplight/memoize-one (based on #40)

Thanks for the replies. I tried the esModuleInterop (it works!) and it seemed to me, that I had to use it sooner or later, since import * as ...  is quite ugly. I'll make a bet still that this will not be the last of tickets relating this issue if this is needed :)

Is there a resolution for this in SSR apps?

@damiangreen esModuleInterop: true

eek, turning that on gives me about 30  TS2349 errors across my application, not really a solution @TrySound without big refactorings

Try allowSyntheticDefaultImports

I have  that enabled already :/

Well, 30 import statements is not so much to tweak.

actually i started trying to refactor my app, but it turns out it would require touching more than 30 imports  but its about a years worth of dev and i dont really want to to a full regression test just to import a library , not on a friday night anyway.

Another workaround is to create a new .js file with a named export:
export { default as memoizeOne } from 'memoize-one';

and import from there.

@sbaechler Why is it different from import memoizeOne from 'memoize-one';?

I have no idea. It is not any different, but it is working. I guess Typescript or Jest are using a different import resolution since it is importing a .js file and not a .ts file.

@sbaechler Do you use babel to transpile TS or ts-jest?

We are using Babel. The config is based on a fork of create-react-app 1. I noticed that this issue does not occur anymore on create-react-app 2 based projects.

Not sure if we're all experiencing the same issue, but here's how I solved mine.
Added this declaration for memoize-one in my project and removed @types/memoize-one
declare module 'memoize-one' {
  export type EqualityFn = (a: any, b: any, index: number) => boolean;

  declare function memoizeOne<T extends (...args: any[]) => any>(
    resultFn: T,
    isEqual?: EqualityFn
  ): T;

  export = memoizeOne;
}

The problem could be that the official types are for 4.1 and I'm using 5.0.
If anyone wants to publish this to DefinitelyTyped (or in the memoize-one codebase directly) be my guest.

@skidding this works a treat, thanks for posting

@TrySound should we add the definition of @skidding to the project?

Hi, first thanks for this neat utility and for caring about the TypeScripters 😃
If you plan to make the type definition file part of the project, here my two cents for version 5:
declare function memoizeOne<T extends (...args: any[]) => any>(
  resultFn: T,
  isEqual?: memoizeOne.EqualityFn<T>
): T;

declare namespace memoizeOne {
  type EqualityFn<T extends (...args: any[]) => any> = (
    newArgs: Parameters<T>,
    oldArgs: Parameters<T>
  ) => boolean;
}

export = memoizeOne;

So instead of naming just a and b to the parameters, they are named newArgs and oldArgs to give a little bit more context.
Using a generic type argument as well on EqualityFn to take advantage of the built-in Parameters<T> type and avoid the use of the permissive any type. This way you also leverage type inference while passing this parameter, so no need to type the arguments yourself.

@alexreardon I guess the issue will never end until we migrate to require('memoize-one').default solution. This can be done with output.exports: 'named' option.

And yeah, having builtin definitions will be good for ts users.

@TrySound if we add a TS definition would this allow TS users to have correct typing without needing to do anything else?

Yes, I think so with TS definition and output.exports: 'named'

If I change
export = memoizeOne;

to
export default memoizeOne;

everything works fine. However, If I change import from
import memoizeOne from "memoize-one";

to
import * as memoizeOne from "memoize-one";

the compilation of my React project fails.
Thus, I am forced to change index.d.ts file as I said (or downgrade memoize-one)

@alexreardon Another solution is dropping default export.
import { memoizeOne } from 'memoize-one';

@TrySound In case of writing { memoizeOne }, I get the following message:
Module '"../../../../node_modules/@types/memoize-one"' has no exported member 'memoizeOne'

@thomasmikava
It's proposal for the project.
Do you have esModuleInterop or allowSyntheticDefaultImports enabled?

@TrySound
No, I don't

They should be enabled to provide cjs/esm interop.

This was broken for me. I eventually fixed it but I consider that work to be more of a chain of unfortunate hacks than I consider it a fix.
I'm in a monorepo using memoize-one across a few projects. We have an electron project and a website. memoize-one did not work out of the box on the electron project. Out of roughly 15 other modules I am using, memoize-one is the only module which does not work out of the box. To fix the electron project, I isolated memoize-one in its own project in our monorepo with the following code:
import * as memoizeOne_ from "memoize-one";

export = <T extends (...args: any[]) => any>(resultFn: T, isEqual?: memoizeOne_.EqualityFn): T => {
    return (memoizeOne_ as any)(resultFn, isEqual);
};

This was working fine for awhile but broke when we started to use memoize-one on our website. Luckily, since I isolated memoize-one to its own project I could add "esModuleInterop": true to it without impacting the other projects. After this I updated my code:
import * as memoizeOne_ from "memoize-one";

export = <T extends (...args: any[]) => any>(resultFn: T, isEqual?: memoizeOne_.EqualityFn): T => {
    return (memoizeOne_ as any).default(resultFn, isEqual);
};

I'm not personally thrilled about this solution but I'm glad that I could at least isolate the impact of esModuleInterop to a single project.
I think memoize-one is a great tool and it could be even greater if it worked out of the box for typescript projects in a standard way without requiring esModuleInterop.

So! Working for TypeScript #72!!!

Not working in Jest/node environment in the same way it was not working before.
Cjs bundle is broken without esModuleInterop

PR welcome @theKashey 👍

There are two ways, please pick any to "fix" the issue, without breaking changes for cjs and non typescript users (ie node):

keep the current "default" export, and add memoizeOne as a named export next to it. However - that would bring some confusion.
keep everything as is. Define .default on memoizeOne itself, so cjs export would be both cjs and esm compatible. Hacky hack, but would work. (don't tell anybody I've proposed it)

Or just enable esModuleInterop and ask ts maintainers to do the same :)

I also stumbled over this typerscript code vs. jest testing problem. What I ended up doing is this:
import * as memoizeOneModule from "memoize-one";
const memoizeOne =
  typeof memoizeOneModule.default === "function"
    ? memoizeOneModule.default
    : memoizeOneModule;

I hope the typescript gods have mercy …

@theKashey i think having the named export is the least strange. Thoughts @TrySound ?
export default function memoizeOne(){...}
export { memoizeOne };

That's the only way to fix the situation without a breaking change.

Having only named export is ok
export function memoizeOne(){...}

and less confusing for commonjs users
import { memoizeOne } from 'memoize-one';
const { memoizeOne } = require('memoize-one');

vs
import memoizeOne from 'memoize-one';
const memoizeOne = require('memoize-one').default;

But that would be a breaking change. However, I definitely agree - that would be the best solution.

@alexreardon @theKashey @TrySound
Any activities?
Can we add named export and leave default export?
I can make pull-request.

@oonsamyi Why not enable interop on your side?

When I add esModuleInterop option to ts config several dozen typescript errors appear and part of unit tests fails. Typescript errors are not a problem for me. But the failure tests are a problem. I don't quite understand why tests fail with esModuleInterop option.
Now I turned off esModuleInterop option and added next hack to jest config:
// project/fixDefaultImports.ts
jest.mock('memoize-one', () => ({
  default: jest.requireActual('memoize-one'),
}));

// project/jest.config.js
module.exports = {
  setupFilesAfterEnv: ['<rootDir>/enzyme.config.js', '<rootDir>/fixDefaultImports.ts'],
  ...
}

But it is hack...
Summary, I would like to work with default typescript config.
Is this issue accurate only with typescript? What about jest + pure javascript?
Is it hard to add named export? I think it is easy, memoize-one will be worked out of the box with typescript default config and many people will be grateful :)
P.S. React resolves this problem next way:
https://github.com/facebook/react/blob/master/packages/react/index.js#L16
It is cool because no matter what is used in the environment of the project: CommonJS or ES6 modules, javascript or typescript, webpack or rollup. It works for all the ones.

Summary, I would like to work with default typescript config.

This is not an option with typescript. You loose safety without strictNullChecks.

Is it hard to add named export?

This is inconsistent design. There should be either default or named export.

React resolves this problem next way:

React does not distribute esm and does not export function as default/module.exports.

But it is hack...

This is too, but this is how ts behaves by default.
import * as memoizeOne from 'memoize-one';

I'd say babel as compiler will solve all your issues.

Why not enable interop on your side?

then classnames would be broken :)

I'm happy to add a named export if it is easier for people

@TrySound Okay, thanks for the feedback.
I will try to use esModuleInterop option.

@alexreardon Can I make a pull request?

Any news?

Let's go

Wasn't it solved in a new version?

It looks like still there is a problem.
I have installed: "memoize-one": "^5.1.1"
When I'm trying to use it like that:
import memoizeOne from 'memoize-one';

I've got an error:
{
  "errorType":"TypeError",
  "errorMessage":"memoize_one_1.default is not a function",
  "stack":[
    "TypeError: memoize_one_1.default is not a function", "......"]
}```

@mits87 Try to enable esModuleInterop in TS config

Actually I can't use the esModuleInterop option because I have a lot of libraries like:
import * as SQS from 'aws-sdk/clients/sqs';
and after enabled esModuleInterop flag I've got errors like:
Type originates at this import. A namespace-style import cannot be called or constructed, and will cause a failure at runtime. Consider using a default import or import require here instead.

Let's kill default import.
https://github.com/alexreardon/memoize-one/pull/86

Any news?
I have a strange problem. I was using memoize-one without esModuleInterop and it works great with import like this:
import * as memoizeOne from 'memoize-one'
but when i set  esModuleInterop to true and change import to import memoizeOne from 'memoize-one' app still works but jest start to fails with  TypeError: memoize_one_1.default is not a function.
If I set a breakpoint around the place where memoize-one is used I see that memoize_one_1 looks like this:
memoize_one_1 : {
  default: {
    {
      default: actual_function
    }
  }
}

App compiles with webpack and ts-loader, jest with ts-jest, typescript version is 3.7.5.
If this problem not relates to this library, sorry.
Any ideas why this happens will be appreciated.

@tamazlykar I faced this problem with webpack when some commonjs module imported esm version of library. Make sure you do not transpile modules by babel-loader.

i'm totally open to adding a minor release which allows people to use memoize-one as a named import
export const memoizeOne = memoizeOne;
export const memoize = memoizeOne;

Just to make peoples lives easier ^

👍 import { memoizeOne } from 'memoize-one'; - it will be better autoimportable.
Plus every time you import memoizeOne from 'memoize-one' eslint will complain about the named export and propose a change (actually that could break builds, but 😅 it is a good to have feature)

@alexreardon With the revert in v5.2.1 is this an issue again? I am still having the error in jest with ts: TypeError: memoize_one_1.default is not a function


Cannot find module '@azure/msal-common' and  '@azure/msal-angular' or its corresponding type declarations.

Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.0.0-alpha.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
3.0.0-alpha.0
Public or Confidential Client?
Public
Description
import { MsalService } from '@azure/msal-angular';
                            ^^^^^^^^^^^^^^^^^^
import { AuthenticationResult, InteractionRequiredAuthError } from '@azure/msal-common';
                                                                   ^^^^^^^^^^^^^^^^^^^^

we can not import the MsalService from @azure/msal-angular.
we noticed this error few hours ago. we are using angular 16.
we also tried following versions. and its same for all those versions.
    "@azure/msal-angular": "^3.0.0",
    "@azure/msal-browser": "^3.0.0",

 "@azure/msal-angular": "^3.0.0-alpha.2",
 "@azure/msal-browser": "^3.0.0-alpha.2"

 "@azure/msal-angular": "^3.0.0-beta.1",
 "@azure/msal-browser": "^3.0.0-beta.1"

Error Message
Cannot find module '@azure/msal-angular' or its corresponding type declarations.
Msal Logs

MSAL Configuration
{
auth: {
        clientId: clientId,
        authority: "B2C_1A_SIGNUP_SIGNIN",
        redirectUri: '/',
        navigateToLoginRequestUrl: false
    },
    cache: {
        cacheLocation: "LocalStoarage",
        storeAuthStateInCookie: false
    }
}

Relevant Code Snippets
import { MsalService } from '@azure/msal-angular';
import { AuthenticationResult, InteractionRequiredAuthError } from '@azure/msal-common';

Reproduction Steps

npm i @azure/msal-browser
npm i @azure/msal-angular
import { MsalService } from '@azure/msal-angular'; to the service.
import { AuthenticationResult, InteractionRequiredAuthError } from '@azure/msal-common';

Expected Behavior
Should be able to use MsalService from '@azure/msal-angular'
Identity Provider
Azure B2C Custom Policy
Browsers Affected (Select all that apply)
None (Server)
Regression
No response
Source
External (Customer)

same here! is there already a workaround?

    "@azure/msal-angular": "3.0.0-alpha.0",
    "@azure/msal-browser": "3.0.0-alpha.0",
    ```
    we updated the packages like this and installed the `npm i @azure/msal-common` seems to get rid of the error.

thanks! downgrade to 3.0.0-alpha.0 worked for me. Even without installing @azure/msal-common.

the content of the package seems borked<EMAIL_ADDRESS>

any permanent for this?
this is how its looks like in the node modules. with the version 3.0.0

It's broken, do not use version ^3.0.0 right now, this fix the issue for now:
"@azure/msal-angular": "3.0.0-beta.1",
"@azure/msal-browser": "3.0.0-beta.1",

Wow, they really shit the bed.. see also https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5410

Getting the same error on 3.0.0, beta version works fine. Looks like they published incorrectly

@HansakaSS Thanks for raising this issue. There has been an error in our release process and we are currently working on a fix. Thank you all for your patience.

Getting same error, but only for msal-angular 3.0.0

also mentioned here #6323

It's broken, do not use version ^3.0.0 right now, this fix the issue for now: "@azure/msal-angular": "3.0.0-beta.1", "@azure/msal-browser": "3.0.0-beta.1",

Yes, beta.1 seems to be working fine BUT when build runs on azure pipelines or docker, it still throws the same error!

Oh my.
It was working fine locally due to installing the exact version with npm install.
However, package.json indicated the package as "^3.0.0-beta.1" and not "3.0.0-beta.1" ... I removed the ^ and it worked!

I have tthe same problem, i tried to come backo to "  "@azure/msal-angular": "3.0.0-alpha.0",
"@azure/msal-browser": "3.0.0-alpha.0", but didn't work.
Another problem is that when I upload to production the MSAL package does not download.

A fix for this was released last week in versions 3.0.1 of msal-browser and 2.0.1 of msal-angular. Let us know if this is still an issue, thanks!

Can confirm that the bug in react version is still there
"@azure/msal-browser": "3.0.1",
"@azure/msal-react": "2.0.1",

another issue is that source-map-loader shows the warning message, we need to ignore the warning message by the following workaround.
fix: ignore webpack warnings by source-map-loader #11752

Not sure if we have to add those:
"@azure/msal-browser": "3.0.1",
"@azure/msal-angular": "2.0.1",
or those:
"@azure/msal-browser": "3.0.1",
"@azure/msal-angular": "3.0.1",
in our package.json .
Anyway, none of those works:
With 3.0.1 with 2.0.1 versions I get a peer dependency error (I guess the versions should match anyways).
With 3.0.1 versions I get a runtime error that was not there before:
""AADB2C90012: The scope '[a-custom-b2c-scope-here] openid profile offline_access' provided in request is not supported.
Correlation ID: f33ed4a2-4db0-43fa-a734-f7f27586b632
Timestamp: 2023-08-17 14:16:42Z"

I have the same error with AADB2C90012, but ony when authenticating against Azure B2C, not when autenticating against Azure AD

Any update on the error I have described? Indeed, this is happening on azure b2c.

Not sure if we have to add those: "@azure/msal-browser": "3.0.1", "@azure/msal-angular": "2.0.1",
or those: "@azure/msal-browser": "3.0.1", "@azure/msal-angular": "3.0.1",
in our package.json .
Anyway, none of those works: With 3.0.1 with 2.0.1 versions I get a peer dependency error (I guess the versions should match anyways). With 3.0.1 versions I get a runtime error that was not there before: ""AADB2C90012: The scope '[a-custom-b2c-scope-here] openid profile offline_access' provided in request is not supported. Correlation ID: f33ed4a2-4db0-43fa-a734-f7f27586b632 Timestamp: 2023-08-17 14:16:42Z"

Should work with newest version

@tnorling Yes it is indeed still a problem.
The contents of node_modules@azure/msal-angular only consist of LICENSE, readme.md and package.json.

Same here, any updates? Using the angular-standalone-sample.
{
  "name": "angular-standalone-sample",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "watch": "ng build --watch --configuration development",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "jest"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^16.1.5",
    "@angular/common": "^16.1.5",
    "@angular/compiler": "^16.1.5",
    "@angular/core": "^16.1.5",
    "@angular/forms": "^16.1.5",
    "@angular/material": "^16.1.5",
    "@angular/platform-browser": "^16.1.5",
    "@angular/platform-browser-dynamic": "^16.1.5",
    "@angular/router": "^16.1.5",
    "@azure/msal-angular": "^3.0.4",
    "@azure/msal-browser": "^3.1.0",
    "@azure/msal-node": "^2.1.0",
    "rxjs": "~7.8.0",
    "ts-node": "^10.9.1",
    "tslib": "^2.3.0",
    "zone.js": "~0.13.1"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^16.1.4",
    "@angular/cli": "~16.1.4",
    "@angular/compiler-cli": "^16.1.5",
    "@types/jasmine": "~4.3.0",
    "@types/jest": "^29.5.0",
    "e2e-test-utils": "^0.0.1",
    "jasmine-core": "~4.5.0",
    "jest": "^29.5.0",
    "karma": "~6.4.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.2.0",
    "karma-jasmine": "~5.1.0",
    "karma-jasmine-html-reporter": "~2.0.0",
    "ts-jest": "^29.1.0",
    "typescript": "~4.9.4"
  }
}

@azure/msal-angular is not even within node_modules.

    "@azure/msal-angular": "3.0.4",
    "@azure/msal-browser": "3.1.0",

we are using this version with node `v18.17.1`. i can confirm this is working fine.

s

Can confirm that the bug in react version is still there
"@azure/msal-browser": "3.0.1",
"@azure/msal-react": "2.0.1",

another issue is that source-map-loader shows the warning message, we need to ignore the warning message by the following workaround. fix: ignore webpack warnings by source-map-loader #11752

I can confirm that I am still finding this issue in react

This is really pathetic. It's feb 2024, and the error is still there.
"@azure/msal-browser": "^3.10.0",
"@azure/msal-react": "^2.0.12",

This is really pathetic. It's feb 2024, and the error is still there.
"@azure/msal-browser": "^3.10.0",
"@azure/msal-react": "^2.0.12",

The current workaround for this issue is using the beta version for msal browser:
"@azure/msal-browser": "3.0.0-beta.1",
"@azure/msal-common": "^14.5.0",
"@azure/msal-react": "2.0.8",

Samples provided in source code does now work.
https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-react-samples
2 kind of exceptions exists:

Conflicting peer dependencies when trying to use most bumped answer versions https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/6310#issuecomment-1953876010
Can't resolve @azure/msal-browser / @azure/msal-react when using source code examples

Tested with
Node: v18.19.1
npm: 10.2.4
Any hints how to make it work?

Its funny but I cloned whole repo once again and moved react-router-sample example to separate directory on my desktop and triggered npm i and its working 😠

    "@azure/msal-angular": "3.0.4",
    "@azure/msal-browser": "3.1.0",

we are using this version with node `v18.17.1`. i can confirm this is working fine.

Can confirm changing the versions to above works, finally:
Change: package.json ->
"@azure/msal-angular": "3.0.4",
"@azure/msal-browser": "3.1.0",
npm install
npm run build
npm run start
site is up and functioning.


Load plugins selectively by declared components only

Skip loading a plugin if its intended to be loaded only by particular Racetrack components (eg. only by Lifecycle, not image-builder), if it's declared in plugin's manifest.
It avoids doing this ugly trick https://github.com/TheRacetrack/plugin-kubernetes-infrastructure/blob/2dd9e2c2a5085cc7b921ab06ccf3603a2d74035c/src/plugin.py#L7C1-L7C1
add plugin's labels - textual keywords describing kind of the plugin, e.g. 'infrastructure', 'job-type'

Example plugin-manifest.yaml:
name: docker-infrastructure
version: 1.3.1
url: https://github.com/TheRacetrack/plugin-docker-infrastructure
components:
  - 'lifecycle'
labels:
  - 'infrastructure'

Instead of multi-value labels, let's use single enum type:
category: infrastructure|job-type|core


chore: Remove metadata.json (azure-gaming/game-dev-vmss) (auto-generated)

This PR was created by a script. Please review the changes and merge if they look good.

Offer with PublisherId: 'microsoft-azure-gaming', OfferId: 'game-dev-vm' cannot be purchased due to validation errors. For more information see details. Correlation Id: 'f454ee44-8016-474f-8124-6fe847be2bd7' Offer with PublisherId: 'microsoft-azure-gaming', OfferId: 'game-dev-vm' and PlanId: win10_unreal_4_27_2 was removed from the marketplace for new purchase. See similar offers here 'https://azuremarketplace.microsoft.com/en-us/marketplace/apps?page=1%26search=microsoft-azure-gaming game-dev-vm'. Correlation Id 'f454ee44-8016-474f-8124-6fe847be2bd7'.

/azp run