ng serve is not working after fresh install - 1.5.2

After successful  creation of new project while starting the project using ng serve command facing below issues.
Versions of @angular/compiler-cli and typescript could not be determined.
The most common reason for this is a broken npm install.
Please make sure your package.json contains both @angular/compiler-cli and typescript in
devDependencies, then delete node_modules and package-lock.json (if you have one) and
run npm install again.
If we try ng -v getting like below
E:\my-project>ng -v

/ \ _ __ __ _ _ | | _ _ _ / | | | |
/ △ \ | ' \ / | | | | |/ _ | '__| | | | | | |
/ __ | | | | (| | || | | (| | | | || | | |
// | ||, |,||,|| |||
|/
Angular CLI: 1.5.2
Node: 8.9.1
OS: win32 x64
Angular: 5.0.2
... animations, common, compiler, core, forms, http
... platform-browser, platform-browser-dynamic, router
@angular/cli: error
@angular/compiler-cli: error
@angular/language-service: error
typescript: error
webpack: error

I get the same issue

For the time being you can try npm start.
for one of the project ng serve didn't work but npm start was working just fine for me.

Have you tried deleting node_modules and running npm install? This can happen with a broken install.

I managed to clear this issue by using nvm and installing this version 6.9.0.
Before reinstalling @angular/cli
Then starting a new app.

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


ALL OTHER added to BY rules of metrics which apply ranking filter

ALL OTHER is added to BY rules of metrics which apply ranking filter so that metrics work correctly when sliced by other attributes

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/83/ : SUCCESS in 12s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/92/ : SUCCESS in 6s

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/93/ : SUCCESS in 6s

See https://gooddata.atlassian.net/browse/CAL-650

Sonar scan result

No issue found. Congratulations!

More detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-public-demos-gate-PR39
To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'.

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-merge-compliance-check/38/ : SUCCESS in 22s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-sonarqube-scan-zuul-gate/36/ : SUCCESS in 54s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-fossa-scanning-zuul-el7/36/ : SUCCESS in 59s (non-voting)


Nan 2.x

Now that Nan 2.x has been released this should probably be updated.

so .. do you think you could do this?

Potentially. I'll have a look later today :)

Started https://github.com/SomeoneWeird/goingnative/commit/187dc7eea408b279562647b2c5bd02b52ec13556 - will clean up and PR tomorrow

Adding to the list: https://github.com/nodejs/node/issues/2798.

@ChALkeR PR awaiting merge :)

@SomeoneWeird Ok, added the PR too =).

Landed in<EMAIL_ADDRESS>


Remove use of gnu-extension anonymous struct/union definitions.

Codecov Report

Merging #1651 into master will increase coverage by 0.11%.
The diff coverage is 89.28%.

@@            Coverage Diff             @@
##           master    #1651      +/-   ##
==========================================
+ Coverage    67.2%   67.32%   +0.11%
==========================================
  Files         167      167
  Lines       21116    21119       +3
  Branches     2589     2590       +1
==========================================
+ Hits        14192    14218      +26
+ Misses       6021     5995      -26
- Partials      903      906       +3

Impacted Files
Coverage Δ

src/core/thread/topology.hpp
89.02% <100%> (ø)
:arrow_up:

src/core/common/message.cpp
94.48% <78.37%> (-1.84%)
:arrow_down:

src/core/common/message.hpp
96.42% <97.29%> (+0.13%)
:arrow_up:

src/core/thread/network_data.cpp
87.26% <0%> (-0.75%)
:arrow_down:

src/core/thread/network_data_leader_ftd.cpp
68.54% <0%> (-0.24%)
:arrow_down:

src/core/thread/mle_router.cpp
77.3% <0%> (-0.17%)
:arrow_down:

src/core/thread/mle.cpp
81.56% <0%> (-0.08%)
:arrow_down:

src/ncp/ncp_base.cpp
29.05% <0%> (+0.24%)
:arrow_up:

src/core/thread/lowpan.cpp
93.9% <0%> (+0.35%)
:arrow_up:

src/core/thread/mesh_forwarder.cpp
78.7% <0%> (+0.36%)
:arrow_up:

... and 8 more

Continue to review full report at Codecov.

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


[announce]Max key lenght limit of KV data type

The SSDB document says "Max key length" is 200 bytes - http://ssdb.io/docs/limit.html no matter what type of data that key is.
But I recently found out that the max key length limit does not applied to KV data type, it was a implementation mistake, it should followed the document.
So, the max key length limit of KV data type will be implemented. This is a incompatible change.
If you ever store any key with length larger that 200 bytes in SSDB with older version, you will not be able to access to that key with later versions.

ok, i understand


when i upgrade node 22 from 16, i can't use “@use ‘’ as *" replace @import

Version
5.0.8
Environment info
this my config in vue.config.js
css: {
    loaderOptions: {
      scss: {
        additionalData: `@use <EMAIL_ADDRESS>as *;`
      },
    },
    extract: { ignoreOrder: true },
  },

my _stlye.css file :
@use "**/reset" as *;
@use "**/utilities" as *;
@use "**/colors" as *;
@use "**/mixins" as *;
i use @use replace @import, project can't run now, my console shows the following
HookWebpackError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
SassError: Undefined mixin.
   ╷
11 │   @include size(100%, 100%);
   │   ^^^^^^^^^^^^^^^^^^^^^^^^^
SassError: Undefined $green_300.
         $green_300

I found that I can't use any parameters and methods
Steps to reproduce
@use replace @import from project when node upgrade to 22
What is expected?
It works fine
What is actually happening?
project can't run and console show all parameter, method undefined but i can find parameter from file introduced by @use

I use @use "" as * to replace the import of all scss files in the project

@use is only used in a specific scope. I reference @used after the SASS file, and it works normally.But I don't know why I wrote '@use ** as *' in vue.config.js. It only works in the Vue file and not in the SASS file.


AMBARI-26073 : Initial setup for Router

What changes were proposed in this pull request?
Raising the base PR to install router. This PR includes/ takes care of installation/start/stop script, configuration script and kerberos management.
How was this patch tested?
I setup a cluster with the proposed changes and tested the Router functionality

/piper build pr

@JiaLiangC , @virajjasani , please help review this PR

Can we change the router configuration without having to restart the entire HDFS cluster? The cost of restarting the cluster is significant, whereas the cost of restarting the router is minimal.

You are correct, we should not restart the HDFS cluster with any config change for Router. I have tried to make sure of that in my code. I have added some comment in my code

https://github.com/apache/ambari/pull/3804/files#r1708682170
https://github.com/apache/ambari/pull/3804/files#r1708685015
Please review these. I tested with these and the restart was not required.

@AnanyaSingh2121   Hi，i found router install faild, web page error message:
Caught an exception while executing custom service command: <class 'ambari_agent.AgentException.AgentException'>: 'Script /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/router.py does not exist'; 'Script /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/router.py does not exist'
The HDFS metainfo.xml  specify  router.py，but i don`t find router.py file in script dir. I think should it specify dfsrouter.py ?

@AnanyaSingh2121 Hi，i found router install faild, web page error message: Caught an exception while executing custom service command: <class 'ambari_agent.AgentException.AgentException'>: 'Script /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/router.py does not exist'; 'Script /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/router.py does not exist'
The HDFS metainfo.xml specify router.py，but i don`t find router.py file in script dir. I think should it specify dfsrouter.py ?

yes @xijunmu , one change is missed. I will raise a PR to rectify. Thank you!


Feature/#3 email notifications for recent activity

Fixes #3

[ ] Migrate
[ ] Setup a Site
[ ] Setup Gmail credentials
[ ] collectstatic


Compile cache files show up as inside app.asar

Prerequisites
Note: Impossible to test under safe mode as by definition this requires external packages.

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Files from packages that are compiled are showing up as being inside the app.asar when searching for them in the Developer Tools. The real locations only open the compiled version.
Steps to Reproduce

Have a third-party package installed.
Open Developer Tools
Attempt to open a file from the search (since virtually no files show up in the Sources list...)

Note: I was seeing even stranger behavior than this, with breakpoints on package files setting themselves on internal Atom files. I deleted the compile-cache folder which leads me to the current better, but still very broken behavior.
Expected behavior: [What you expect to happen]
The file you select from the search opens the original source file, with the source map making breakpoints work.
Actual behavior: [What actually happens]
File "in" app.asar is the real file, with the source map showing which parts of the file aren't in the in-use code.
File at the real location is the compiled version of the file, when you open this it tells you there is a source map active.
Note that it is only possible to get to the real version of a package file if it has a unique name. If you try to search for a file name used in many packages (like main.js) then it seems to pick whichever shows up first in the list of real results.
Reproduces how often: [What percentage of the time does it reproduce?]
100% of the time.
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
> atom --version
Atom    : 1.16.0-beta0
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0
> apm --version
apm  1.16.1
npm  3.10.5
node 6.9.5 x64
python 2.7.12
git 2.12.0.windows.1
visual studio 2015

This appears to be fixed on a build based off of merging 842b3f0f3cb39562914f7f5e6bd071acad9c1e3b into 25dcf2ed81e920fbdeb0f1cf7684269e75f41289.

Confirming this as fixed in v1.17.0-beta3.


'File cannot be opened because it does not exist or it is used by another process' and you're sure both file exist and it's not used by another process it means SQL on-demand can't access the file.

Not 100% sure but, would almost say there could be some caching issue or something else causing this error aside from lack of permission.
Using the default AAD pass through credentials was not working, when I'm  admin on this subscription. Tried adding my account to the ADLSG2 (though redundant IM), etc
Nothing seemed to work, always got this error. Then just recreated the external data source (no credentials). Started working.
in case it helps someone.
thx

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

ID: 24ee637b-9227-d549-9481-bbdc404cfa17
Version Independent ID: c2f0070e-2c40-813b-f6f6-97e088a0b06c
Content: SQL on-demand (preview) self-help - Azure Synapse Analytics
Content Source: articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md
Service: synapse-analytics
Sub-service: sql
GitHub Login: @azaricstefan
Microsoft Alias: v-stazar

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

Hi @rquintino did you use database scoped credentials when you created first data source (maybe you used SAS/Managed Identity which didn't had rights)?
When you don't specify DB scoped credential then AAD pass-through is used by default.

Hello @rquintino ,
I did tried out the scenario and in my case also I am the owner of the subscription , What i found that to read the data from
blob/adlgen2 I had to give myself the blob storage reader permission , this is called out here . Once I gave the permission it took 3-5 mins for me to have access to the blob , I was trying to run a copy command against a file in the storage account .
We are going ahead and closing the issue for now . You can always reopen this if you think thats appropiate .


fix: Do not run git secrets if no file changed

Description

We shouldn't call git secrets with empty file list.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

/bot run checks

/bot run checks


Radio Buttons are pixelated in Firefox on Windows

Looks like setting the size of radio buttons this large is causing strange rendering for Firefox on windows machines.
We may just be able to reduce the size of the radio button elements to eliminate this pixelation.

Closing this.


Add FOR/ENDFOR to b:match_words: MatchIt/MatchUp

Hm. I can close this but it says closed without being merged. I do see the changes in 306af42 so idk why Github doesn't think this was merged.

Merged offline.


WebConstants.SPRING_PROCESS_SAVED_REQUEST

WebConstants.SPRING_PROCESS_SAVED_REQUEST don't exist

https://github.com/shimingxy/MaxKey/blob/239573cd0594894c1cb08e51a91c3964df125a72/maxkey-web-manage/src/main/java/org/maxkey/web/endpoint/LoginEndpoint.java#L100

5/23  fixed，已经修复


SFT微调Phi-2报错：RuntimeError: mat1 and mat2 must have the same dtype, but got Float and Half

Reminder

[X] I have read the README and searched the existing issues.

 Use --hub_token instead.
warnings.warn(
[INFO|trainer.py:571] 2024-01-24 09:41:50,595 >> Using auto half precision backend
[INFO|trainer.py:1721] 2024-01-24 09:41:50,916 >> ***** Running training *****
[INFO|trainer.py:1722] 2024-01-24 09:41:50,916 >>   Num examples = 168,446
[INFO|trainer.py:1723] 2024-01-24 09:41:50,916 >>   Num Epochs = 3
[INFO|trainer.py:1724] 2024-01-24 09:41:50,916 >>   Instantaneous batch size per device = 4
[INFO|trainer.py:1727] 2024-01-24 09:41:50,916 >>   Total train batch size (w. parallel, distributed & accumulation) = 16
[INFO|trainer.py:1728] 2024-01-24 09:41:50,916 >>   Gradient Accumulation steps = 4
[INFO|trainer.py:1729] 2024-01-24 09:41:50,916 >>   Total optimization steps = 31,584
[INFO|trainer.py:1730] 2024-01-24 09:41:50,917 >>   Number of trainable parameters = 157,324,800
0% 0/31584 [00:00<?, ?it/s]Traceback (most recent call last):
File "/content/LLaMA-Factory/src/train_bash.py", line 14, in
main()
File "/content/LLaMA-Factory/src/train_bash.py", line 5, in main
run_exp()
File "/content/LLaMA-Factory/src/llmtuner/train/tuner.py", line 31, in run_exp
run_sft(model_args, data_args, training_args, finetuning_args, generating_args, callbacks)
File "/content/LLaMA-Factory/src/llmtuner/train/sft/workflow.py", line 75, in run_sft
train_result = trainer.train(resume_from_checkpoint=training_args.resume_from_checkpoint)
File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 1539, in train
return inner_training_loop(
File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 1869, in _inner_training_loop
tr_loss_step = self.training_step(model, inputs)
File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 2768, in training_step
loss = self.compute_loss(model, inputs)
File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 2791, in compute_loss
outputs = model(**inputs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/accelerate/utils/operations.py", line 687, in forward
return model_forward(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/accelerate/utils/operations.py", line 675, in call
return convert_to_fp32(self.model_forward(*args, **kwargs))
File "/usr/local/lib/python3.10/dist-packages/torch/amp/autocast_mode.py", line 16, in decorate_autocast
return func(*args, **kwargs)
File "/root/.cache/huggingface/modules/transformers_modules/microsoft/phi-2/85d00b03fee509307549d823fdd095473ba5197c/modeling_phi.py", line 1049, in forward
outputs = self.model(
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/root/.cache/huggingface/modules/transformers_modules/microsoft/phi-2/85d00b03fee509307549d823fdd095473ba5197c/modeling_phi.py", line 919, in forward
layer_outputs = self._gradient_checkpointing_func(
File "/usr/local/lib/python3.10/dist-packages/torch/_compile.py", line 24, in inner
return torch._dynamo.disable(fn, recursive)(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/_dynamo/eval_frame.py", line 328, in _fn
return fn(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/_dynamo/external_utils.py", line 17, in inner
return fn(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/utils/checkpoint.py", line 458, in checkpoint
ret = function(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/root/.cache/huggingface/modules/transformers_modules/microsoft/phi-2/85d00b03fee509307549d823fdd095473ba5197c/modeling_phi.py", line 669, in forward
attn_outputs, self_attn_weights, present_key_value = self.self_attn(
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/amp/autocast_mode.py", line 16, in decorate_autocast
return func(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/amp/autocast_mode.py", line 16, in decorate_autocast
return func(*args, **kwargs)
File "/root/.cache/huggingface/modules/transformers_modules/microsoft/phi-2/85d00b03fee509307549d823fdd095473ba5197c/modeling_phi.py", line 319, in forward
query_states = self.q_proj(hidden_states)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/linear.py", line 114, in forward
return F.linear(input, self.weight, self.bias)
RuntimeError: mat1 and mat2 must have the same dtype, but got Float and Half
0% 0/31584 [00:01<?, ?it/s]

Expected behavior
期望能正常训练。
System Info
用Coogle Colab提供的T4 GPU
Others
No response

我也遇到了同样的错误

same issue as well

Set quantization to 8 for phi2 when loading the model for training. Working for me that way.

Is this a workaround or actually solves the issue?

I came across the same issue and the remedy for me is add hidden_states = hidden_states.to(self.q_proj.weight.dtype) at the beginning of the forward function in the PhiAttention class

如果不改代码，可以用fp32跑，至少在2080ti 22g上是能跑起来的。


optimize(hz): handler_single.go supports the same methods as handler.go

What type of PR is this?
optimize: A new optimization

Check the PR title.

[ ] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.
[ ] Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):
(Optional) Which issue(s) this PR fixes:
https://github.com/cloudwego/hertz/issues/1001

(Optional) The PR that updates user documentation:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: ypo2478:x: zongqian.liuzongqian.liu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Raphael Warnock W000790

I am suggesting we include this image which is sourced from Senator Warnock's Wikipedia article due to the fact he currently has none:
https://upload.wikimedia.org/wikipedia/commons/a/a3/Raphael_Warnock_official_photo.jpg
The metadata from Wikipedia lists it as part of the public domain as it relates to his official duties in Congress.

Photo now available:

https://theunitedstates.io/images/congress/original/W000790.jpg
https://theunitedstates.io/images/congress/450x550/W000790.jpg
https://theunitedstates.io/images/congress/225x275/W000790.jpg

However, the associated metadata file is missing: https://github.com/unitedstates/images/blob/gh-pages/congress/metadata/W000790.yaml


[Howto]: Use composer in another PHP Container

Have you already checked elsewhere?

[X] I have read the Devilbox documentation
[X] I have checked the Devilbox Troubleshooting Guide
[X] I have checked the Devilbox FAQ
[X] I have checked the Devilbox Howto
[X] I have checked the Devilbox Forum
[X] I have checked existing issues
[X] I have googled already with no luck
[X] I have not done any of the above

What are you struggling with?
I want to use different version of PHP of PHP in CLI but can't access to composer for install package with PHP82
What have you tried already?
I setup an project with backend.cfg, frontend working fine with php82 but CLI by default is launched with version 7.4.
I can start a CLI with PHP 8.2 that not the real problem, but composer is not accessible with the 82 CLI.
What is your goal?
Using composer in PHP82 container

@TheoD022 By default, it uses the prod version of the docker image. That's why there is no composer in that php82 container.
Please make sure to use the work version.
You need to edit docker-compose.override.yml and change the image to: image: devilbox/php-fpm:8.2-work-0.150

Thank you, this fixed it for me. What is prod and what is work?

@BWBama85  Read here: https://github.com/devilbox/docker-php-fpm#-flavours


The App crashes

Hi!
First, I really like your Idea of bringing the Garmin Hud back to life and sync it with Google Maps!
But i can't get it to work... Perhaps you can help me? I tryied severel App-Versions but the problem is always the same: the first time, i run the app after installation, i'm able to connect the hud and everything seems to work fine. But if i want to reconnect the hud, the hud doesn't connect automaticaly. And if i want to open the app to reconnect it manually, the app keeps crashing. The only solution i found, is to delete the storage of the app and set everything up from the beginning. Again, everything is working... Until the next reconnect.
I'm using your app on a Pixel 2 with Android 10 in german language.
I hope you understand what i'm writing, my english is not the best 😉

Hi, what is the newest version you try？
I had meet this problem in older version, but fix it after 0.6.3.

I tried 0.6.4, 0.6.3 and also older versions.

I played around with the problem... maybe it can help?
I figured out, that the app only crashes, when i reopen the app by clicking on the icon. If i open the app by clicking on the recent-app-list, there is no crash. But when i press the Bluetooth-reset-button, the app crashes immediately.
Once the garmin hud is powered off and on, it doesn't reconnect automatically. I can connect it manually by open the app like described above and connect it over the search-device-button. Sometimes i have to try it 2 or three times, but then it connects.

Hi
I disable the BT init procedure when app start.
Hopes this can find bugs out.
When you start app, touch "RESET BLUETOOTH" to init BT  ( If app didn't crash).
Then use app as previous.

Hi,
I tried to reproduce the issue on my device but didn't have any success.
On my device is installed version 0.6.4 and it runs fine.
Same requirements as @Joern80: Google Pixel 2 and german language
Strange issue

I tried the versions 0.6.5 and 0.6.6
0.6.5:
The first time i open the app after installation, everything works fine. I press "reset Bluetooth" and can make a connection over the "connect device". After turning the hud off and on, the app doesn't connect automatically.  Pressing the "Bluetooth reset" leads into a crash. If i don't press "reset", just pressing "connect device", the app tells me, it is connected to the hud, but in fact, it isn't.
0.6.6:
The same behaviour like 0.6.5
The difference between 0.6.4 and 0.6.5/0.6.6: I'm able to open the app by pressing the app icon.
@Niklas04 : your comment makes me hope! 😀 Whats the difference between our devices? I'm using apps, that have notification access: ifttt, tasker, auto notification, notification listener... I tried to turn off the access to notification for these apps, but nothing changed.

Yes, that is a good question, what the difference might be ...
I don't think it is an issue regarding the notifications, I think it might be an issue with Bluetooth connection functionality.
Did you try to start the app without Google Maps running? If the app keeps crashing nevertheless, this should completely exclude worries regarding notification - I think.
I didn't try to turn off Garmin HUD while navigation is running. I will try that. Maybe it loses Bluetooth connection and this is causing some weird issue.
Running an app from the app icon and recent app list shouldn't make a difference, in my opinion.

Did you try to start the app without Google Maps running?

Yes, it doesn't matter, if maps is running or not.

I didn't try to turn off Garmin HUD while navigation is running.

Most of the time i turn off the hud while no navigation is running.
Again I played around with 0.6.4. At first i reset the network settings (including Bluetooth). Nothing changed.
After connecting the hud for the first time, a press on "reset Bluetooth" leads to a crash. It doesn't matter, if the hud is on or off.
I didn't mentioned it before, I don't know it's important or not: after installing the app, the app wants me to enable the notification access. When I enable the access and go back, the app again wants me to enable the access. Everytime I ignored this because the notification access works fine.

Hi
Because of I don't have pixel 2 and not face this bug, all I can do is try&error.
Please try this v0.6.7
https://github.com/skyforcetw/Garminuino/releases/download/0.6.7/gmaps_hud-release_v0.6.7.apk
I think there is something wrong after first HUD connecting.
So I stop the most relative part to see is anything change.

0.6.7:
First connection works fine. The second connecting leads to a problem: Again, no automatical connection. When i press "search device", my phone says "Bluetooth is not available". If i press "reset Bluetooth", the app crashes. But I'm able to reopen the app by clicking the icon without a crash.
I'm still wondering, that Niklas has no problem with his pixel 2. Should i make a factory reset on my phone?

I think it might be another app, that causes the issue.
Maybe you can try to press "Force stop" on different apps (only one at a time) and then reopen the GoogleMaps HUD App and test if it crashes. (I don't know how long an app stops before it restarts itself.)
Another way might be to uninstall some apps that might have some extended functionality (e.g. Tasker)

Niklas04 should be right.
There is something change with Joern80's pixel2 bluetooth.
I modified the BT init procedure just like first time open the app in anytime.
Please try this one:
https://github.com/skyforcetw/Garminuino/releases/download/0.6.8/gmaps_hud-release_v0.6.8.apk

I'm a little busy but at the end of the week i will test 0.6.8. If it doesn't work, i will check some apps and force them to stop... And if this doesn't help, i will reset my phone.

I think I got a solution: it seems like the app "Flic" (Bluetooth Buttons) causes the problem. I'm not 100% sure, but when I delet the buttons in the Android Bluetooth Settings, the app don't forget the buttons, but the HUD app doesn't crash anymore.

I will install "Flic" and try.
Thanks for your information.

Unfortunately , I don't have Flic's hardware, cannot meet the same issue.


The right devops project name can't be showed at the secret list

What is version of KubeSphere DevOps has the issue?
3.3.0
How did you install the Kubernetes? Or what is the Kubernetes distribution?
No response
What happened?

Create a devops project named devops project and create a secret in it;
Enter into the view of the cluster resource managerment list and find the secret and you will see the name couldn't match the real name.
Relevant log output
No response
Additional information
No response

This page does not belong to DevOps.
/close


Update name of repo in README to smirnoff99frosst

This BEGINS the process of renaming to smirnoff99frosst from smirff99frosst, though to be finished, we need to wait until smirnoff finishes being separated from smarty.
@bannanc - can you do a quick check? The main goal in this PR was just to change the title on the README.md, but I made a few other edits as well.

@davidlmobley
So all the files are still called smirff99Frosst, does the conda install actually use smirnoff now?

So all the files are still called smirff99Frosst, does the conda install actually use smirnoff now?

A new conda installable version will be generated once we finalize whatever changes we want on here, do a new release, and then have Nathan/me push it to the channel (we do it manually for now). So, no, right now everything on conda is still as it was in the last release.


Clarify order of tasks shown by doit list command

The doit list command shows tasks in alphabetical order, but the
documentation gives the impression that tasks are shown in some other
order. This can cause confusion for users expecting tasks to appear in
order of execution.

Coverage remained the same at 99.789% when pulling 70833d8dcf152274356e6049c82635f994a143cf on poliquin:list_order into 234d9bda6e235a25e9ab7ce01cef0b7fadc647f4 on pydoit:master.


Update 'Why?' section of index

Signed-off-by: Jeff Schutt<EMAIL_ADDRESS>

love it. thanks!


Parameterize the amount of ethanol with the amount of precursors

Probably associate the tapping density with the volume of ethanol?

Implemented in some.


Allow services to free from package cache

This change allows folks to define a service on azure.yaml and ask azd to avoid holding the result of packaging for deployment  during azd up.
By allowing this, azd would re-package the service during azd up , before deploy, automatically.
This strategy will enable front-end applications to use the outputs from provision during deploy.
**schema-updates to be done apart...

I'm concerned about us having this switch to control the cache behavior.  Given that we are going to allow users to change the ordering in up in #3173 do we need to do this?

@ellismg , yes, I thought about it, but, using the workflow for that would mean re-defing azd up for all todo-samples, as we have an static web app on each of them.
We would need to do something like this to all templates:
workflow:
   up:
      - command: azd package --service api --output foo
      - command: azd provision
      - command: azd deploy api --from-package foo
      - command: azd deploy web

This is b/c there will be no memory cache in workflows between package and deploy, and we still want to use the package from api before provision.
It feels noisy and weird to redefine everything and to do it all all templates with a swa.
Imagine how it would look an azd project with 10 backend services and 5 swa...
That's why I am thinking on this easy alternative for swa services.
I am not saying we dont do the workflows.. I think it solves a different problems, and not just the swa

This is b/c there will be no memory cache in workflows between package and deploy, and we still want to use the package from api before provision.

I guess I don't understand why this is the case.  Why do we care about when the "package" action is run for the API?
If we instead just did:
workflow:
  up:
    azd: provision
    azd: package
    azd: deploy

Wouldn't that just work?
In fact, I suspect we could even elide the package step, since it will happen implicitly as part of deploy:
workflow:
  up:
    azd: provision
    azd: deploy

Is there something pushing us to wanting the package of the API to happen sooner?

Is there something pushing us to wanting the package of the API to happen sooner?

Not really. In my mind, it is all about modularity and composability.  Let me explain myself:

As a customer, when I pick a template (or look at azure.yaml), it is easier for me to see there is some special configuration for one service than looking special configuration for the entire project. When I see this:

workflow:
  up:
    azd: provision
    azd: deploy

I don't know why there is a change to the default azd up flow.  Is it b/c one of the services need it?  is it because all of them need it?  is it b/c performance?  etc. etc.  Without depending on some extra comments around there, it is not easy to get the reason why there is that set up for the template.

Another scenario:  Let's say I run azd init -t todo-something.  I want to take one of the todo (or any other tempate) as the base starting point for my application.  My application is just a backend server, so I think I can just remove all the things about the web and replace the api src code with my code. But, what about this workflow setting on azure.yaml...  How do I know I can remove it if it not easy to know why it is there. How do I know the implications of removing it.

Another thing on my mind is related to the easy-init flow.  I was thinking that, similar to how azd has those special discovery prompts for guiding users detecting their applications, azd could ask users, when finding a nodejs app, if the application is an static-web-app (or even auto detecting react/vue/etc) and if yes, the service configuration on azure.yaml will include this field noCache  (we can even consider renaming it to swa, or static. Or move the option to a bag of options for Node, similar on how we have a bag of options for docker and for spring).  This seems intuitive to me, because the service can be added/remove it without affecting the other services on the list.

The main potential I see for the workflows feature  is for very advance scenarios. Specially for those where we will typically see a call to azd deploy --from-package, (see this example: https://teams.microsoft.com/l/message/19:ug5DKpbpRJbBtgoSQAXdynHgthpALgePNJ8wb5AI8HM1@thread.tacv2/1704192371983?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=c99e8504-1250-4d95-a824-9778e0e626c7&parentMessageId=1704192371983&teamName=Azure Developer CLI (azd) Partners&channelName=General&createdTime=1704192371983).  Basically, as a way to re-define not only the order for azd up, but to re-define and customize the end2end flow. Combining hooks with workflow will empower people to use azd commands just as anchors to run any postcommand hook to re-define what the command does.
For the swa cases, I think the scenario should be handled directly as part of the service's configuration. I don't understand why the entire project should be updated (seems wrong).

As mentioned by @ellismg, the package caching would remain intact after we introduce the up workflow feature.  We would not need to use --output or --from-package flags.

@wbreza , see previous comments: https://github.com/Azure/azure-dev/pull/3177#issuecomment-1879480682

Are we asking folks to update the entire azd-project whenever they add an static web app service?
Are we going to use a custom-up flow for the easy-init when detecting nodejs apps?  (or static web apps). If we don't, azd up won't work (current issue).

@wbreza , see previous comments: #3177 (comment)

Are we asking folks to update the entire azd-project whenever they add an static web app service?
Are we going to use a custom-up flow for the easy-init when detecting nodejs apps?  (or static web apps). If we don't, azd up won't work (current issue).

It comes down to being up to the user.  If they want/need to use provisioning outputs in their packaging then they can write a custom workflow to do that.  If we are able to do some simple detection, then maybe easy-init does this for you but we can't solve for all the use cases.

Thanks for starting the conversation here, @vhvb1989.  I think I'd like us to not do this right now - let's see how far folks get with the ability to re-order the up workflow before doing this.  If it looks like folks still really need a simpler gesture to solve the caching problem, we'll go build it then.

Closing a per https://github.com/Azure/azure-dev/pull/3177#issuecomment-1913113041
The plan:
When customers require to access the infrastructure-outputs during deployment (for deploying at least one service), customers must define a custom workflow (as per azd-design).
Example:
For a project with a web and api service with an azure.yaml like:
# Raw azd project
name: foo-sample
services:
  web:
    project: ./src/web
    dist: build
    language: js
    host: appservice
  api:
    project: ./src/api
    language: js
    host: appservice

If the web service requires infrastructure-data (like Azure endpoints, kv accounts, etc), the azure.yaml should be changed as:
# Raw azd project with custom workflow that invalidates cache as a side effect for all services
name: foo-sample
workflows:
  up:
    steps:
      # We don't need azd package. running azd deploy will invoke package first.
      - azd: provision
      - azd: deploy
services:
  web:
    project: ./src/web
    dist: build
    language: js
    host: appservice
  api:
    project: ./src/api
    language: js
    host: appservice

This is what we want, instead of doing:
# Raw azd project with a field to opt-out from cache without custom workflow
name: foo-sample
services:
  web:
    project: ./src/web
    dist: build
    language: js
    host: appservice
    # ask azd to ingore cache for this service only, forcing azd deploy to run package again as a side effect
    NoMemoryCache: true
  api:
    project: ./src/api
    language: js
    host: appservice

Notes:

The opt-out option affects only the service which requires the special case, while the workflow changes the behavior of all services (as shown in previous example).

Supporting a combined project where:

one service must be packaged before provision and its output must be used for deploying.
other service must be packaged only after provision infrastructure

Requires a complex workflow to list all services and creating connection manually, between package and deploy (using arguments).

By looking at a custom-workflow, without a comment, it is imposible to know if the workflow is required for any of the services or not.  Customer must remember to document relationships between services and the custom-workflow.


Fixed starting service in the foreground

Installing Archives:
  Preparing to install archives
  Downloading SDK Platform Android 8.1.0, API 27, revision 1
  Download finished with wrong size. Expected 65606517 bytes, got 65738431 bytes.
  Done. Nothing was installed.

dunno what causing this...


ko.mapping.toJSON ignores options parameter

I guess

ko.mapping.toJSON = function (rootObject, options) {
  var plainJavaScriptObject = ko.mapping.toJS(rootObject);
  return ko.utils.stringifyJson(plainJavaScriptObject, options);
};

should be

ko.mapping.toJSON = function (rootObject, options) {
  var plainJavaScriptObject = ko.mapping.toJS(rootObject, options);
  return ko.utils.stringifyJson(plainJavaScriptObject);
};

This still doesn't work with toJS or toJSON. Basically my 'mapping' parameter (which I presume is options, since it's undocumented) gets ignored.

Can you add a reproduction scenario on jsfiddle?

Just so I'm not wasting time here: how should the mapping object (as given on the ko.mapping documentation page on the KO site) be passed to ko.toJS/ko.toJSON? I only see an options parameter for these functions, so I'm a bit confused.

It should simply be passed in as the only parameter, the options are automatically taken from the mapped object (inside your mapped object there is a ko_mapping property), e.g.:
var unmapped = ko.mapping.toJS(mappedViewModel);

No, this property is set automatically when you create a mapped object. The normal flow is something like:
var mappedViewModel = ko.mapping.fromJS(data);
// do stuff
var unmapped = ko.mapping.toJS(mappedViewModel);
mappedViewModel already contains the ko_mapping property, you don't need to do this manually. This is why it is not documented.

Oh, I see. And I think you mean that the mapping object can only be passed in on fromJS, per the Knockout documentation. e.g.
ko.mapping.fromJS(data, mapping)
but not the corresponding for the toJS/toJSON functions?

Yes, fromJS is intended to be used only with objects created with toJS. I hope this clarifies the problems you are seeing.

Thanks, all is clear now.


[New Feature] Music Command

TODO

[ ]  Simple Play and Pause Command
[ ]  use ffmpeg instead of opus for cross-compatibility
[ ] implement a skip/stop function (add voting system to it to promote fairness, Bot Owners should be exempted from this.)

Coming in the refactor uwu

:eyes:

Closed because Milestone has been completed


fix: bump deps to work with backstage v1.29.0

Description
Bump the dependencies to clear warnings in updating to backstage v1.29.0
Issue number: #74
Type of change

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

Checklist

[x] I have performed a self-review of this change
[x] Changes have been tested
[ ] Changes are documented
[x] Changes generate no new warnings
[x] PR title follows conventional commit semantics

If this is a breaking change 👇

[ ] I have documented the migration process
[ ] I have implemented necessary warnings (if it can live side by side)

Acknowledgement
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Hello @jpd4emis! Thanks for creating a PR for this one. Although it wasn't breaking anything I like to keep things clean. Thanks for supporting us on that.
I have tested locally and I confirm there are no changes in behaviour. I'll merge this and add the details to the release notes once I release it later today.


Fix dependency issue when running npm run dev

Related to #369
Update sanity version to resolve dependency conflict.

package.json

Update sanity version to 3.62.0 in dependencies.

studio/package.json

Update sanity version to 3.62.0 in dependencies.

I was waiting for Sanity to fix this issue before bumping the Sanity dependencies. I just merged a PR to migrate the Sanity loader; all dependencies have been bumped.


Problems with matterbridge-zigbee2mqtt.config.json on Docker installation

Hi,
installed Matterbridge using docker with this configuration:
  matterbridge:
    container_name: matterbridge
    image: luligu/matterbridge:latest # Matterbridge image with the latest tag
    network_mode: host # Ensures the Matter mdns works
    restart: always # Ensures the container always restarts automatically
    volumes:
      - "${HOME}/Matterbridge:/root/Matterbridge" # Mounts the Matterbridge plugin directory
      - "${HOME}/.matterbridge:/root/.matterbridge" # Mounts the Matterbridge storage directory

It works. Then, I installed matterbridge-zigbee2mqtt plugin, restarted Matterbridge, and it works too.
Problems arise when trying to configure the plugin. I created a matterbridge-zigbee2mqtt.config.json file on the correct path (${HOME}/.matterbridge) with this contents:
{
  "name": "matterbridge-zigbee2mqtt",
  "type": "DynamicPlatform",
  "unregisterOnShutdown": false,
  "host": "<IP_ADDRESS>",
  "port": 1883,
  "topic": "zigbee2mqtt",
  "username": "mqtt_user",
  "password": "MY_PASSWORD",
  "whiteList": [],
  "blackList": []
}

The mqtt broker address, username and password are right.
When starting, matterbridge-zigbee2mqtt plugin gives:
[08:50:59.846] [Zigbee2MQTT] Error connecting to mqtt://localhost:1883: Connection refused: Not authorized
which suggests that config file hasn't be loaded.
After checking paths, contents and so on, I tried several time: every time he uses "localhost" - not the right configuration.
So I tried with:
docker exec -it matterbridge sh
and, in /root/.matterbridge, I found out the matterbridge-zigbee2mqtt.config.json which the plusin is using (despite my configuration), with this own contents:
{
  "name": "matterbridge-zigbee2mqtt",
  "type": "DynamicPlatform",
  "host": "localhost",
  "port": 1883,
  "topic": "zigbee2mqtt",
  "username": "",
  "password": "",
  "whiteList": [],
  "blackList": []
}

so I manually changed this configuration, saved the file, restarted the plugin... and again, "localhost" is used, because the file turns back to the original configuration as above.
No way to make the plugin use a different config.
KC

Hi,
thank you for your interest.
The config files always "turn back to the original configuration" because you need to shutdown Matterbridge before.
The file inside and outside are the same.
From the readme.MD:
You can edit the config file (shutdown Matterbridge before):
On windows:
cd $HOME\.matterbridge
notepad matterbridge-zigbee2mqtt.config.json

On linux:
cd ~/.matterbridge
nano matterbridge-zigbee2mqtt.config.json

Beside this I tried on my test machine with docker and I reproduced the error you described.
I will update you as soon as I understand...

Yes you're right: the configuration has been made with the Docker container stopped, so when you run it Matterbridge-zsigbee2mqtt should be able to load it up at startup, but it seems not working.

I don't understand if is a mosquitto issue or a docker problem in general ... Try to run Matterbridge standalone.

It's not a mosquitto issue: the problem is that matterbridge-zigbee2mqtt@docker is not loading custom configuration, to let application uses the correct broker address/username/password.

Hi,
I found the problem.
The image is made with Alpine, apparently it cannot resolve names.
I made different tests and if you put the ip address it connects from inside like from outside the container.
If you stop matterbridge and changes the config, when you start it again it reads the new parameters.
So that's all.

I made different tests and if you put the ip address it connects from inside like from outside the container. If you stop matterbridge and changes the config, when you start it again it reads the new parameters.

that's precisely what I tried, but with no results: if you read on top in this thread, I placed the mqtt broker IP in the config: the prolem is that the application in the container seems not reading (and using) this configuration

I have 3 MQTT broker, I switched between each of them running inside docker compose and standalone.
It always changed the configuration and connected to the correct MQTT broker.
BTW I added a debug in the next release that log the whole config.
Any chance that you have an old raspberry arm/v7 or arm/v7? I need to test the image the arch...

Yes, got one. Tomorrow will do some tests

I confirm what @KC-inDomus says.
When I edit plugin config file, after a container restart, config file turns to original state and all changes are lost
This is my test...
I've just changed the mqtt broker listen port...
snakuzzo@herobox ~/prova/provaAle $ docker exec -it matterbridge sh
/usr/src/app # cat /root/.matterbridge/matterbridge-zigbee2mqtt.config.json  | grep port
  "port": 1884,
/usr/src/app #

Then...when I restart the container
snakuzzo@herobox ~/prova/provaAle $ docker-compose restart
[+] Restarting 1/1
 ✔ Container matterbridge  Started                                                                     5.4s
snakuzzo@herobox ~/prova/provaAle $ docker exec -it matterbridge sh
/usr/src/app # cat /root/.matterbridge/matterbridge-zigbee2mqtt.config.json  | grep port
  "port": 1883,
/usr/src/app #

My config file is overwrited and I've lost alla changes in my config file

Hi,
thank you for your message.
I will try to explain better:

the config files are loaded from the storage directory (.matterbridge) at start and saved on shutdown (the plugin can modify the config during the execution).

This means that (as reported in the readme.MD) to modify the config you have to:

shutdown matterbridge (since you are using docker: docker stop matterbridge);
edit the file from $HOME/.matterbridge/matterbridge-zigbee2mqtt.config.json
start matterbridge (since you are using docker: docker start matterbridge).

The command: docker exec -it matterbridge sh that you use implies that the container is running and so whatever you do on the config from inside the container or from outside (there is no difference) will be overwritten on shutdown.
This is the correct sequence:
docker stop matterbridge

cd ~/.matterbridge
nano matterbridge-zigbee2mqtt.config.json

docker start matterbridge

In the next releases will be possible to edit the config from frontend.

Hi,

This is the correct sequence:

docker stop matterbridge

cd ~/.matterbridge

nano matterbridge-zigbee2mqtt.config.json

docker start matterbridge

That's what I did, but the config won't load.

I've tried just now... It didn't work. Config file is overwritten

Ok...It works...my mistake.
You have to:

stop container
change config file
start container

If you edit file and then restart container, every change will be lost
So...you have to change file when software is not running

Ok...It works...my mistake. You have to:

stop container
change config file
start container

If you edit file and then restart container, every change will be lost
So...you have to change file when software is not running

yes, same here. Need to STOP, change, START. This could be misleading @Luligu

I'm glad we solved the problem.
Can I ask to make a test please?
The image: luligu/matterbridge:dev is build with a new technique from the 20-bullseye-slim for linux/amd64,linux/arm64,linux/arm/v7,linux/arm/v6.
If you have any linux/amd64,linux/arm64,linux/arm/v7,linux/arm/v6 can you try if it loads?
The dev contains already all the plugins installed (dev too for zigbee2mqtt) so do not install them just add them eventually.
Thanks

Hi,
thanks.
With latest it works regularly on the same machine in the same conditions ?

Yes... with latest I have no problems

Hi,
can you test again please?

ok...now it dev starts.
I just added plugin (it is already installed, as you said)...but on restart it overwrite mqtt parameters in config file.

Now with the dev you see more info so there is no doubt about config.
Thanks for the test.


feat(*): add --filter-out-file and --log-success options

These two options are meant to be used together to allow re-running only the failing tests of a test suite.  The --log-success option appends the name of each test to the given file, the --filter-out-file option specifies a file that lists tests which should not be run.

This needs a test and the getFullName function needs to be factored out, but what do you think about the approach @Tieske @hishamhm ?

Wouldn't the more typical pattern be to log failures and specifically rerun only previously failed tests? Kinda brainstorming here but it seems like that's a pattern I've used before in other test frameworks.

@alerque The thing with a "failed" list is that it is harder to maintain because entries need to be removed from it once they pass, while the "succeeded" list can just be appended to.  In fact, the --filter-out-file and the --log-success file can be the same for every (re-)try of the test suite.  I am aware that ideally, you'd want to fix your tests so that they are not flaky, but we are in a situation where we cannot quickly do that.  Thus, being able to run a large test suite repeatedly until all flaky tests have passed is what we need.
I can add a --filter-file and a --log-failure option if you think that someone would find that more useful.  The complication is that one would have to specify --filter-file only in the second and subsequent runs and use the --log-failure file of the previous run (if any) as input to --filter-file.  I'd prefer the simple solution, even if it might be unconventional.  Let me know what you think.

I assumed the use-case for this was hacking on the code until the tests pass. If dealing with flaky tests is the use case would a --retry-failed or similar way to give failed tests a second (or more) go in one test runner help?

A --retry-failed option would work in principle, but that would make it less apparent that there are flaky tests.  We want to be aware of the flakiness, so a failure of the test suite run is good and a manual intervention is acceptable.  What we want to avoid is having to re-run all the tests that passed, as that greatly reduces our productivity.  With my proposed approach, we can reduce the time that it takes to re-run a single failed test from 20-30 minutes to under one minute, which is a substantial win.

@alerque Is this PR now mergeable?  We would like to start using the added functionality more and it would be good to have it be in the upstream repo for that reason.

I actually just fixed all the nit picks from my code review, but I can't push it because apparently you don't have the "allow maintainers" option checked in this PR.

Can you either allow me access or pull the commits from this branch or split up the commits yourself as in that branch?

Thank you for your review - I've addressed your comments.  Where would I enable the "allow maintainers" option for next time?

There should be a check box on the right sidebar in this PR I think...

Thank you for your review - I've addressed your comments. Where would I enable the "allow maintainers" option for next time?

Unfortunately you can't address a comment about not touching irrelevant code by re-touching it again in another commit. That will just turn up 2 irrelevant commits in history on blame/bisect etc. I edited the history in way to completely remove the style change and move the unrelated bit to a different commit.
Yes you might be right about not being able to allow me access to an org you don't administer.
I see three options to fix this now:

You can pull in my branch linked above by adding a remote, then git reset --hard <branch_name_or_sha>, then force push this so that you send my commits to this PR.

You do the same git revise and/or git rebase foo to split and edit existing commits.

I can merge the commits manually outside of GitHub. You'll still be credited with the commit authorship but thy PR will be marked as closed instead of as merged. Up to you if you care.

No sweat off my back for any of the above, they just have tradoffs for you ;-)

I've reset the PR to your branch and force-pushed.  Thanks!

Thank you for merging, can you prepare a release as well or can I ping someone else to do it?

See v2.2.0.


source  = "terraform-aws-modules/ec2-instance/aws"

Description
source  = "terraform-aws-modules/ec2-instance/aws"
unable to donwload the GIT file as source does not exist , pls update accordingly
Error: Failed to download module
│
│ Could not download module "ec2-instance" (main.tf:7) source code from "git::https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v3.6.0": error
│ downloading 'https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v3.6.0': git must be available and on the PATH.
╵
╷
│ Error: Failed to download module
│
│ Could not download module "ec2-instance" (main.tf:7) source code from "git::https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v3.6.0": error
│ downloading 'https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v3.6.0': git must be available and on the PATH.

module "ec2-instance" {
  source = "terraform-aws-modules/ec2-instance/aws"
  # ...
}

More info - https://developer.hashicorp.com/terraform/language/modules/sources

module "ec2-instance" {
source = "terraform-aws-modules/ec2-instance/aws"
...
}
version = "~>3.0"
Error
terraform init

Initializing modules...
Downloading registry.terraform.io/terraform-aws-modules/ec2-instance/aws 4.3.0 for ec2-instance...
╷
│ Error: Failed to download module
│
│ Could not download module "ec2-instance" (main.tf:7) source code from
│ "git::https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v4.3.0": error downloading
│ 'https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v4.3.0': git must be available and on the
│ PATH.
╵
╷
│ Error: Failed to download module
│
│ Could not download module "ec2-instance" (main.tf:7) source code from
│ "git::https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v4.3.0": error downloading
│ 'https://github.com/terraform-aws-modules/terraform-aws-ec2-instance?ref=v4.3.0': git must be available and on the
│ PATH.
╵
PS C:\Temp\create a EC2>


Switching insertBefore to insertAfter

I've found some issues with utm_form when the forms have already hidden inputs for UTM tracking, for example, because there's some logic in place to retrieve UTM parameters from the URL.
The easiest solution to make utm_form work with those type of forms is to move the added fields added by utm_form from the top of the form to the bottom, so they effectively override the previous inputs.
Hence the switch from insertBefore to insertAfter.

Yes, I've noticed some people having those issues where a form plugin inserts the fields and the script values are not captured. This fix will help in those cases.
The changes look good. Can you please also bump the version to 1.0.3 and add the compiled js to dist folder?
Thanks @victorespigares.

Done :)


Use node ID, not node name, to find nodes sent back from server.

When associating nodes in a task graph log to those in the graph itself, we were using the node's name. This was not intended to be used for that purpose; instead we should be using its UUID, which is IDentifies it, Uniquely (Universally).

@thetorpedodog shall we merge this?


🗄🔧 CakePHP

Current Status

Codebase in progress: CakeDC/cakephp-realworld-example-app

Interested in helping out? Say hello! 🎉

Todo:

[x] 🏁 Fork the starter repo & post the link in this issue
[x] 🎨 Create logo for repo & update issue status (@ericsimons)
[x] 🔨 Implement all of Conduit's functionality per the spec & API
[ ] 👀 Move repo to main org & Peer review final codebase by admins/community (RFC)
[ ] 🎉 Tag v1 release and officially list it on the README!

We would like to implement the backend with CakePHP
We have already forked your starter app here:
https://github.com/CakeDC/cakephp-realworld-example-app

Code pushed, will update readme soon.

Awesome, I can't wait to see the final version! I also just created a logo that you can use for the repo:

Task list categorized by api

[x] Articles

[x]  GET - Feed
[x]  GET - All articles
[x]  GET - Articles by author
[x]  GET - Articles favorited by username
[x]  GET - Articles by tag
[x]  POST - Create article
[x]  GET - Single article by slug
[x]  DEL - Delete article
[x]  PUT - Update article
[x]  POST - Favorite article
[x]  DEL - Unfavorite article

[x] Auth

[x]  POST - Login
[x]  POST - Login and remember token
[x]  POST - Register
[x]  GET - Get current user
[x]  PUT - Update user

[x] Comments

[x]  GET - All comments for article
[x]  POST - Create comment for article
[x]  DEL - Delete comment

[x] Profile

[x]  GET - Profile
[x]  POST - Follow profile
[x]  DEL - Unfollow profile

[x] Tags

[x]  GET - Get all tags

@EricSimons The API is implemented and ready for peer review.

One thing I noticed is that MySQL is being used. I think MySQL is more common than PostgreSQL in the PHP community. Feel free to correct me if I'm wrong.
@EricSimons Do we have standards around which database should be chosen? Should database setup documentation be included in the repository?

Also, it looks like there is some generated code that can be removed. See src/Controller/PagesController.php.
My knowledge of PHP is limited, so feel free to correct me on anything I'm wrong about.

@brwr no — we let the author choose the desired DB.

@phpnut great work! Have you tried pointing one of our frontend implementations at this backend to see if it works? Often times CORS will manually need to be enabled, etc.  (btw I'm attempting to get this to run locally, but running into PHP ini issues)

I don't see any database requirements. But cakephp can work with any database: both MySQL and Postgress are fully supported.

@EricSimons I've tested with angluar2 and react frontends. Both was working really nice.

The CakePHP ORM works with many databases, the user can choose whatever they want. The migrations setup will setup the tables as needed.
Drivers include Mysql Postgres Sqlite Sqlserver

@EricSimons what errors are you getting? Is it related to intl extension?

@phpnut yup that's the one — any idea how to fix? (I'm a PHP noob :)

@EricSimons you need to have intl extension installed and enabled to use CakePHP. What OS are you using?

@phpnut Mac 10.12.1

@EricSimons ok, this is not compiled by default. MAMP for Mac has intl active by default, this would be the quickest way to download and test. If you would like to install intl extension on your vanilla php install on the Mac I can provide you with some steps to do this.
I am currently working on a plugin that can replicate the functionality CakePHP using for translations and other features, but life has thrown some blockers. I plan to start on it again soon.

@phpnut okay perfect, will try out MAMP and see if that works :)
In the meantime, if there are any other CakePHP folks out there who can review the code and 👍  or 👎  that would be great!

@EricSimons, that would be great. We kinda make a living reviewing CakePHP code for others :)

I'll give this a test on my end as well.

Looks like CakePHP hates windows setup. I got it running fairly easily on a vagrant box. But the instructions are clearly lacking for a beginner. What are the api routes? I'm getting an error on accessing http://cake.dev/api/articles or any url. The error message is "Extension class OptionsHandlerExtension could not be found."

What problems did you have with windows?

@SandeeshS it works on windows well as it was developed and tested there. There was old composer.lock file. Please pull and run "composer install" again.

@skie seems like the pull fixed it, got the api working fine now :+1: It's 1:30am here and i'm about to hit d bed. I'll do a thorough test in the morning and leave my feedback. Although at first glance there seem to be additional data coming through the api, like the tags count on tag, additional pagination info on articles.

Although at first glance there seem to be additional data coming through the api, like the tags count on tag, additional pagination info on articles.
Pagniation and tags count info is removed from response.

I think you should remove all empty (noise) folders, makes people easier to focus on the actual code inside the repo
e.g.

https://github.com/CakeDC/cakephp-realworld-example-app/tree/master/plugins
https://github.com/CakeDC/cakephp-realworld-example-app/tree/master/src/View/Helper
https://github.com/CakeDC/cakephp-realworld-example-app/tree/master/src/Controller/Component
https://github.com/CakeDC/cakephp-realworld-example-app/tree/master/src/Model/Behavior

etc.

Also, it looks like there is some generated code that can be removed. See src/Controller/PagesController.php.

@brwr This is used by the default route if someone was to visit / vs /api so it is needed

@EricSimons all unused directories and files removed. You can fork the project back to your GitHub account now.

Official repo is online at https://github.com/gothinkster/cakephp-realworld-example-app and @phpnut and @skie have been added as collborators :)

@EricSimons Thanks, glad to see your project and can see it being very useful to people looking at different tools to develop their apps with. Nice way to compare, create work.
Are you going to be able to change the gif? media/stacks_hr.gif

@phpnut it's actually a screencap of our animation on https://thinkster.io :) I need to split it out and make it easily expandable, but yes absolutely I'll include CakePHP in there once I find a few minutes to do that!
Now that this repo is in the main org, I'm gonna go ahead and close this issue. Thanks again for the amazing work CakePHP folks!

@EricSimons you can use this SVG, it you need another format let me know.
https://cakephp.org/v2/img/logos/CakePHP_Logo.svg


Implemented Lanczos Algorithm

closes #19

General question for you . Why did you add the 1chiML logo in a new resources folder. If i look at the original pdf it already had the image.

Hi @nicholaslegrand102, the image used in the .pdf is not part of this repository for some reason. Which means that I can't compile the .tex file into a pdf.
There might be another image elsewhere that I can use, but I don't know where this could be.

@GM07 I was thinking about making a PCA to demonstrate something that we could do with this algorithm. But this requires Jacobi to properly compute eigenvectors and eigenvalues.  I think we should start by merging this branch first and when your branch will be ready we'll make a third PR with the implementation of PCA. What do you think?


Fixed typo

@mimig1,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Dump .yardoc db in JSON

I'm working on a fork of yard which would take an option to dump the .yardoc database into JSON instead of Marshal. I'll be pushing commits to my fork in sometime, but before I do that, I wanted to understand if adding such functionality is part of yard's roadmap or is there a possibility of it's inclusion ?

Sorry for the lack of response on this.
There have been efforts to dump to JSON in the past, specifically when working on refactors of the templating engine to work more like a single page app. The biggest issue was speed and size, because a single JSON document is actually pretty hefty and slow to load. If performance benchmarks showed that JSON was similar in speed and size, it would be on the roadmap, but if it's significantly slower or larger I don't know that it would be part of core.
Note that you can always write these things as plugins. The Registry has a RegistryStore backend which actually manages the data on disk, and that can be swapped out (or should be swappable).

Closing as an answered question. Patches would be looked at for a YARD Registry to json exporter option, though as suggested, starting it as a plugin and opening a PR only after it is stable is the better path, I believe. I'm open to accepting PRs that fix any roadblocks in making this a plugin, if there are any.


Starlink 5 missing launch_site data

All three values are currently set to null. I imagine this is because that information doesn't exist yet. If possible, can assume it's Cape Canaveral, and change it when we receive new data?
I made this mistake of assuming this data would be available, so versions of my app (the majority of them) are crashing when receiving a null value. I've fixed it in a new build, but it would be helpful for older versions.
Thanks 🙏🏼

Going to fix this over the weekend. Currently the checks are hardcoded, which doesn't lend well to human input 🙃
A more flexible regex like the ones for dates should work better there

This is fixed in the v4 updater


Support for graphql as an element

Support for GraphQL would be pretty neat, to populate the object on load.
Something like this:
 <graphql>
{
    user {
        name
        email
        address_line_1
    }
}
 </graphql>

Which would then be able to fill the data object and redraw the view.
This would only be used for an on-load fetch

wow that's a neat idea!

I'm glad your interested. I can put some work into it if you want a PR, but obviously this is your project; so you understand it best. Would you like me to try it.

I currently don't have time to look into this, but it would be interesting to think through the design details first - e.g.

how would the full usage code look like, including JS and templates?
what integration layer to use? (raw graphql-js? vue-apollo?)
how about mutations? if user still needs considerable gql usage in JS, is this idea worth it?

I'll throw together an ideal usage example when I get the chance, probably this weekend.
I think raw graphql-js would be the best way to go about this.
A good starting point would be to simply let the user fetch data only (no mutations, queries only). We can always expand on it later on. Start simple, and see if people actually find this useful and want to use it.
In terms of whether its worth it, i think it will be, even just for the initial fetching of data; if we can simplify that process, then thats a good start.

I'm having trouble setting this up for testing it locally. Is the best way to do it to go TDD on it, and create some test files in the test folder and try to get the code to pass, or is there a better way?
Perhaps a contribution.md file to explain the best way to contribute would be good :)

Which branch are you working on? Make sure to work on top of next instead of master.

Ah. I was working on master. Okay, i'll switch my base :)

I'm trying to run the tests from the next branch; but get this on npm install:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
is there anything i'm doing wrong?

that was a peer dep of eslint-config-vue after update. Just install it and should be fine

Should it be saved into the package.json file or is it supposed to not be installed automatically?

It should, it's just not updated yet.

What do you think of this as something to aim for?
<template>
    Starwars Film: {{ film.title }}
    Directed by: {{ film.director }}
</template>

<graphql>
{
    film(filmID: 1) {
        title
        director
    }
}
</graphql>

<script>
    export default {
        props: ['film'],
        data(graphql) {
            return graphql
                .success(function(data) {
                    return {
                        film: data.film
                    }
                })
                .error(function(errors) {
                    // Handle errors here
                })
        }
    }
</script>

Example Used:
http://graphql-swapi.parseapp.com/?query={
  film(filmID%3A 1) {
    title
    director
  }
}


🐛 Bug Report: stuck while installing yarn

📜 Description
Yarn install taking too much time to install
👍 Expected behavior
It should install fast
👎 Actual Behavior with Screenshots
Installing dependencies:
init          git repository ✔
determining   yarn version ✔
executing     yarn install ◝

👟 Reproduction steps

Install npm and remaining prereqs for backstage
Run command npx @backstage/create-app@latest
Install yarn - npm install -g yarn
give name of app - test1

📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

I'm experiencing the same behaviour - have waiting hours (2+ hrs).
Mine is reproducible here: https://github.com/drewkhoury/backstage-3m/tree/patch-1 on a new M2 Mac.
git clone git@github.com:drewkhoury/backstage-3m.git

mkdir -p /tmp/backstage/data
ENVFILE=env.example make envfile
make bootstrap

...
  copying       SearchPage.tsx ✔
  copying       EntityPage.tsx ✔

 Installing dependencies:
  determining   yarn version ✔
  executing     yarn install ◡

well it is too slow. it means i am on 32 gb laptop and it is taking around 20 minutes and still ending abruptly

You can run create-app with the --skip-install flag and then once it's scaffolded run yarn install, that might help to debug which package fails to download/build.

I too was having a major issue with the installation on Fedora 37. I did have some success eventually though after updating node to 18.16.1 (current LTS) and Yarn 1.22.19 (latest), then running the create-app:latest (0.5.2?) with the --skip-install flag set. I then moved to the folder created for my app and ran yarn install. After that, Backstage came up. But it did take a couple of hours of trail and error with many failed attempts.

I also got bitten by this today. yarn install seemed to be stuck indefinitely. Happened consistently on 3 Ubuntu executions I ran. In the end going with --skip-install and then running yarn install in the app directory worked fine. Yarn install then took ~5 min.
Wondering if --skip-install should be made the default behaviour...

I just reproduced this in Ubuntu on WSL2 on Windows 11.  It has been running 'yarn install' for several minutes now and is still hanging there.   I recently ran this on a remote server and had no issues - yarn install was almost instant.  Not sure why it is hanging.

I'll just say that depending on your definition of "several", that sounds like a pretty short time to wait. Yarn easily downloads, unpacks and links several gigabytes, and then runs some native build steps too for some packages.

I'll just say that depending on your definition of "several", that sounds like a pretty short time to wait. Yarn easily downloads, unpacks and links several gigabytes, and then runs some native build steps too for some packages.

It was almost instantaneous the first time I ran it on the remote machine.  However, here is what I learned the issue was:
https://stackoverflow.com/questions/46013544/yarn-install-command-error-no-such-file-or-directory-install
I had to run with --skip-install and try and run yarn manually to see that the version installed with cmdtest was the culprit.

Nice to have would be to show some of the progress from the yarn output, even if it is only the most recent line of output from the 'yarn install' command.  That way users can tell what yarn install is doing and if it is hung or not.


What should the front page be?

Should the front page be set to the calendar directly? The intro text is not that useful, and the front page contains only static content now.

I think the front page should consist of:

The initial paragraph
A list of how people can keep up to date with the calendar (iCal, RSS, newsletter)


Store secrets firebase

Short Description
Introduces a script that fetchs the api secrets and stores it in an untracked file by git (.secrets_env)
This will grant the app access to the API_KEY value so that api calls can succeed
What changes in the code?
Adds the script
Modifies the remote data source so that it will eventually read the api key from the .secrets_env file (NEWS_API_KEY) variable
Did you test?

[ ] Yes
[ ] No

Note: Explain why you didn't test if that's the case

@Diogo00dev looks like the tests are failing because not being able to find the file .secrets_env which means I have the chance to rework the github action to fetch the secrets as part of this PR, I will close and reopen once that is done

@Diogo00dev this is ready to be merged, once it is please reopen #17 and review
Unfortunately we cannot run the script I created to be run by devs, fetch-secrets.sh from GitHub Actions, here things are slightly different.
I described the steps that are required as part of the workflow on the .workflow file

LGTM, thanks for the explanation in each step 💪


Update dcp-client to 0.35.0

Updates com.couchbase.client:dcp-client from 0.33.0 to 0.35.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.couchbase.client", artifactId = "dcp-client" } ]

labels: library-update, semver-minor

Superseded by #57.


Make everything position: relative

This is something @davidkpiano talks about and at first I was not on board and even made fun of him about it, but the more I think about it, the more I like it.
Possible benefits

Predictable parent relationships for absolute children
Stacking becomes easier (yes I know there's a plethora of ways that you can affect stacking order)
The potential of a lot less CSS written. The chances of removing relative for static etc are likely to be way lower that you’d add relative

I’ve been thinking about it again when he and Shaw were on ShopTalkShow, which is worth a listen.
It’s worth remembering that a lot of stuff in this reset goes against the browser defaults, so this one, albeit way against browser defaults fits in nicely IMO.
I’m opening this up for discussion because I might be missing a big issue here which I really don't want to create.

Thread on Twitter: https://twitter.com/hankchizljaw/status/1182396654001053696

I've deployed this type of change in a fairly large project, e.g., ~2 million page site. It worked well, so I'd say this is a fair inclusion.

With the caveat that I don’t use CSS resets (yes, I’m THAT kind of guy). When I use absolute positioning, it is a red flag that says “be aware what you are doing here because that can cause problems with zoom, responsiveness, overlapping and so on”.
Therefore absolute positioning is something I only use when I need to position something that can’t be done using grid/flex positioning. It makes those cases very rare and often means that I position something from a nested element in relationship to an element that is at least one layer up.
It feels counter-intuitive to me to then remove position: relative until I get to where I want to anchor the element to.
TL;DR: When I set position:absolute deliberately, I also set position:relative deliberately.

Adding this will make it more fiddly to intentionally choose what context you're absolutely positioning a given element against. If everything is relatively positioned, positioning context will always be the parent (unless one resets the parent's position). I think it is fairly common to want to position against a (great)grandparent, and would therefore advise against this.

Adding this will make it more fiddly to intentionally choose what context you're absolutely positioning a given element against

Perhaps this is a good constraint?

I think it is fairly common to want to position against a (great)grandparent, and would therefore advise against this

No, this is very uncommon.
To prove this:

Go to any webpage with non-trivial styles (such as this one, on GitHub)
Add the * { position: relative } style via browser dev tools
See if any styling breaks.

Chances are, very few things (or nothing at all) will break.

I think in that context, a rule like this could be feasible:
.component-with-absolute-grandchild,
.component-with-absolute-grandchild * {
  position: static;
}

.component-with-absolute-grandchild .absolute-thing {
  position: absolute;
}

That's presuming that this context is a rarity in your codebase though. If this is frequently having to be dealt with then I'd personally remove this rule line in the reset, just like I’d remove the nuclear reduced-motion rules if I had a responsible contextual system in place.

@davidkpiano

Perhaps this is a good constraint?

If it was part of the CSS spec, maybe. But it is a constraint that exists just on websites that use this reset, and not on others. I worry this will make it confusing for people who have learned CSS, as they now need to unlearn some of their expectations of how it works. Basically it changes how the standard works for only some websites.
For example: developer works on website A, website B, website C. Then they're hired by an agency to tweak some styles on website D, which uses this reset. Now positioning works differently than expected. I realise doing ^ { box-sizing: border-box; }, which I do like, potentially has the same problem.

Chances are, very few things (or nothing at all) will break.

This does surprise me! But it does not take away my worries… the “few things” might include something that is super hard to debug / that your whole business relies on / that causes hard-to-automatically-detect accessibility issues for some users etc
@hankchizljaw Right, yea, it is easy to re-reset. But if it wasn't there in the first place, it wouldn't need resetting… I guess the question really is, like you and @davidkpiano say, whether it is a rarity or not. To me it doesn't feel rare, but understand for many it would certainly be rare.

The beauty of this reset is that it's so tiny, taking elements away that are causing problems is really easy. A few people don’t like the ul[class], ol[class] stuff and my response to them each time is basically “don't use them, then”.


Allow Duplicate Scans For Four Days

ITS-Pro time category: https://its-pro.ucsd.edu/browse/MA-74
This is complete when:

[ ] The scan returns a success if the same user scans the same barcode value within four consecutive days

Deployed to QA and Prod

Deployed to QA and Prod


Remove inboxes and ActivityStreams JSON

SkoHub PubSub (as well as SkoHub Editor) hasn't been used in production settings yet. Because of this and because of missing resources we'd need for maintenance, we decided to switch off both modules on skohub.io for an indefinite period.
Against this background, we should better cleanly remove all PubSub related functions from SkoHub Vocabs, which are at least these:

[x] jsonas, inbox and followers stuff in gatsby-node.js, src/queries.js, /.env.example, src/common.js, /src/types.js
[x] inbox link in /src/components/Concept.js
[x] inbox mention in README.md

Here is my functional review of the changes to be introduced with #199:

When triggering a build for the first time, I got an error message, see https://test.skohub.io/build/?id=7193fc66-3a32-42f0-8880-cf8a8197c549. However, this must not be related to the changes.
When I triggered the build again, everything ran as expected: https://test.skohub.io/build/?id=b39ffa40-f830-423e-9dc0-5f15a1f1f12a
Furthermore, I had now problems when setting up a development server locally.
I could not find any remnants of ActivityStream data, the .jsonas files are completely removed, followers and inbox are gone from the .json and the inbox link isn't shown anymore in the HTML. (Also, the inbo mention from the README is gone.)

Over all, +1 fom my side.

Furthermore, I had now problems when setting up a development server locally.

@acka47 Can you specify what kind of problem you encountered when setting up the local development server? Or did you mean "no problems"?

Or did you mean "no problems"?

Yes, I meant that but by mistake added a "w" (which I now deleted).


Vite commonjs not getting converted to esm

Getting the following error:
Internal server error: module is not defined
      at eval (/node_modules/react/index.js:8:3)
      at instantiateModule (file:///Users/i24823/projects/svelte-design-system-ts/node_modules/vite/dist/node/chunks/dep-ae3fae1b.js:52409:15)
ReferenceError: module is not defined
    at /node_modules/react/index.js:6:3
    at instantiateModule (file:///Users/i24823/projects/svelte-design-system-ts/node_modules/vite/dist/node/chunks/dep-ae3fae1b.js:52409:15)

svelte config:
import adapter from '@sveltejs/adapter-auto';
import { vitePreprocess } from '@sveltejs/kit/vite';
import {mdsvex} from 'mdsvex';
import preprocessReact from "svelte-preprocess-react/preprocessReact";

/** @type {import('@sveltejs/kit').Config} */
const config = {
  // Consult https://kit.svelte.dev/docs/integrations#preprocessors
  // for more information about preprocessors
  extensions: ['.svelte', '.md', '.svx'],
  preprocess: preprocessReact({
    preprocess: [
      mdsvex({
        extensions: ['.md', '.svx'],
      }),
      vitePreprocess()
    ]
  }),
  kit: {
    alias: {
    '$library': './src/library',
    '$react': './src/react'
  },
    adapter: adapter()
  }
};

export default config;

vite.config (commented out lines are things I have tried):
import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vitest/config';

export default defineConfig({
  plugins: [sveltekit()],
  ssr: {
    noExternal: true
  },
  // build: {
  //   commonjsOptions: {
  //     include: [/node_modules/],
  //   },
  // },
  optimizeDeps: {
    include: [
      '@capsizecss/core',
      // 'react',
      // 'react-dom'
    ],
  },
  test: {
    include: ['src/**/*.{test,spec}.{js,ts}']
  }
});

Any thoughts?

This has to to with React still using commonjs, but I haven't encountered the issue you're describing. In my tests Vite was able to handle the react imports.
Could you try to recreate the bug on Stackblitz?

Thanks. I had a go but ran into some different errors on StackBlitz. Would you be able to get it running with SvleteKit 1.x on StackBlitz. Just default install with one react HelloWorld component on a route?
https://stackblitz.com/edit/sveltejs-kit-template-default-4ammlw?file=vite.config.js&terminal=dev
If I can start from something that works I can then see where I am breaking things.

https://stackblitz.com/edit/sveltejs-kit-template-default-539f8b?file=src%2Froutes%2FSomeComponent.tsx,src%2Froutes%2F%2Bpage.svelte&terminal=dev

Thanks

I think my problem was using it with vitePreprocess which it is meant to replace this is currently the default rather than sveltePreprocess. So it was not clear that I needed to replace vitePreprocess with sveltePreprocessReact. By reading the docs it looked to me like you needed vitePreprocess for TypeScript so I did not try removing it.
https://kit.svelte.dev/docs/integrations

Thanks again for taking time to do this all working now. noExternal: true in vite.config was also breaking this.
	// ssr: {
	// 	noExternal: true
	// },


Added RemoteWindowsDeployer

@Tratcher @victorhurdugaci @muratg
Will send out a PR for MusicStore later

:up: :date:
@victorhurdugaci The exit code stuff doesn't seem to work for me. Still investigating it, but there are other changes which you can probably review meanwhile

:up: :date:

:watch:

:up: :date:

Looks good to me :shipit:

80714a3d70a743cdea742e4ab27f1c17a2a8d2ee


[1.x] Revert "Set meilisearch data path"

Reverts laravel/sail#299
Reverting this because it causes Sail to throw permissions errors: https://github.com/laravel/sail/issues/300

Thank you, and sorry for all the trouble my PR has caused! 🙏

@caugner don't worry about it


python311Packages.aliyun-python-sdk-config: 2.2.11 -> 2.2.12

Changelog: https://github.com/aliyun/aliyun-openapi-python-sdk/blob/master/aliyun-python-sdk-config/ChangeLog.txt
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 252891 run on x86_64-linux 1

4 packages built:

python310Packages.aliyun-python-sdk-config
python310Packages.aliyun-python-sdk-config.dist
python311Packages.aliyun-python-sdk-config
python311Packages.aliyun-python-sdk-config.dist