add storm-id to worker log filename

add storm-id to worker log filename, so we can view logs group by the topology-id

@jessicasco change worker log, requires changes to core ui, logviewer, worker in order to make sure the links and other search functionality don't break.

We have topology-id and port in log directory,  current log structures under storm-local/workers-artifacts:
--topoId0
--topoId1
------port1
------port2
---------worker.log
---------worker.log.err
---------worker.log.out

@wuchong  I got it. Thank you.

@wuchong    How about 0.9.x version? I checked 0.9.6 still has worker-{port}.log, which mix different topology log to one file.  Will the workers-artifacts log feature merge to 0.9.x version?

@jessicasco  yes,  you are right.
The workers-artifacts feature is merged by @zhuoliu ,  you may ask him.

hi jessicasco, though worker-artifacts changes log directory structure and naming, when you download worker.log from UI, the storm id and port will be automatically append to the file name, which is quite convenient.

@zhuoliu  Thank you for your explanation.   Is there a simple way to split topology log in worker-{port}.log for storm 0.9.6?

Hi jessicasco, for the versions before workers-artifacts, the following code in util.clj might achieve what you want:
(defn- logs-rootname [storm-id port]
  (str storm-id "-worker-" port))

(defn logs-filename [storm-id port]
  (str (logs-rootname storm-id port) ".log"))

(defn logs-metadata-filename [storm-id port]
  (str (logs-rootname storm-id port) ".yaml"))

(def worker-log-filename-pattern #"^((.*-\d+-\d+)-worker-(\d+))\.log")

(defn get-log-metadata-file
  ([fname]
    (if-let [[_ _ id port] (re-matches worker-log-filename-pattern fname)]
      (get-log-metadata-file id port)))
  ([id port]
    (clojure.java.io/file LOG-DIR "metadata" (logs-metadata-filename id port))))

@zhuoliu Thank you for your code snippet.

@jessicasco could be named with topology-name ?

@darionyaphet  not topology-id but topology-name?

@darionyaphet, in 0.10 and before, worker log file has topology-id and port in its name. In latest version, the topo-name and port no longer exist in its same (please see [storm-901 | https://github.com/apache/storm/pull/822]). However, when user download log file from ui, topo-id and port will be added to the downloaded file's name automatically.

@jessicasco yep
current log's name looks like worker-{port}.log rename to 'topo-name-{port}' maybe better ?

@darionyaphet My code rename the log file to {topology-id}-{port}.log, but as @zhuoliu says they have a better solution since 0.10.

@zhuoliu  Storm current log structures is:
storm-home/logs/
------supervisor.log
------nimbus.log
------workers-artifacts/
-----------topo1/
------------------port1/
------------------port2/
------------------------worker.log
------------------------worker.log.err
------------------------gc.log
worker's gc log's name maybe like {workers-artifacts}-{topo}-{port}-{worker}.gc. Supervisor will restart the worker if some worker dead. Then the worker's gc name is the same as before. I find the dead worker gc log is   coverd with new gc log

@jessicasco sorry  I'm using 0.9.4 ..

Hi Fang, @hustfxj. Great question! We also met the same problem. Actually our setting for gc log name is "-Xloggc:artifacts/gc.%p.log". Then gc log won't be overwritten due to worker restating.
Then we will also need to https://issues.apache.org/jira/browse/STORM-1206 to avoid too many gc files' names crashing the logviewer JVM (this might happen in  a very very extreme and rare case, only once in our cluster).

very good! thank you  @zhuoliu


[FEAT]

Is your feature request related to a problem? Please describe.
Currently the hook useForm does not have a way to add parameters to the request, this happens when we get values when editing a record.
Describe the solution you'd like
We could add the initialFilter property as used in useTable, this would add more parameters to our request.
Example:
/post/1?field=value

Hey @hectoryx ,
Firstly, Could you add the Issue title?
Could you also share your use case with us? What do you want to do and why is it not working? Theoretically you shouldn't need this. But we are wondering about the use case.

Hey @hectoryx , Firstly, Could you add the Issue title?
Could you also share your use case with us? What do you want to do and why is it not working? Theoretically you shouldn't need this. But we are wondering about the use case.

Sure, in the specific case of strapi, when we have draft records, these records are not visible in the requests, the solution is to add ?_publicationState=preview to the request, this applies in one record or many.

Hey @hectoryx , Firstly, Could you add the Issue title?
Could you also share your use case with us? What do you want to do and why is it not working? Theoretically you shouldn't need this. But we are wondering about the use case.

Sure, in the specific case of strapi, when we have draft records, these records are not visible in the requests, the solution is to add ?_publicationState=preview to the request, this applies in one record or many.

Ohh okay. We add the use of the "metadata" field for "publicationState" for Strapi v4 data provider. I think we can do the same for v3. So you get what you want!
I don't know if we can do this anytime soon, but I think you can too.
While doing this, you can be inspired by Strapi v4 Data provider,
https://github.com/pankod/refine/blob/strapi-v4/packages/strapi-v4/src/dataProvider.ts#L101
https://github.com/pankod/refine/blob/strapi-v4/packages/strapi-v4/src/dataProvider.ts#L190

Got it, Thanks!


rhcos - Fix for multi builds

Based on the doozer adjustment for unified builds https://github.com/openshift/doozer/pull/691/files
Test:
elliott -g openshift-4.11 rhcos --release 4.11.0-0.nightly-2022-12-07-113128 -p kernel

/lgtm


Add Support for DATE datatype in Pinot

We have use case where we need to store date datatype in pinot.

Can you elaborate more on the use case and curious if TIMESTAMP can be an alternative for it?
cc: @Jackie-Jiang

We are using tableau for visualization and due to its licensing cost we are in process to deprecate it with superset
But tableau has extract feature in which we save output of sql query in tableau server as in-memory.
To add this functionality in superset we build one service that will take sql query from superset, run it on trino then trino-pinot connector will insert data into pinot(insert support added by @elonazoulay in trino )
In our service we first take the query from user, get its schema from trino and convert the schema in a way that will be compatible to pinot like bigint to long
As hive tables  has support for date datatype but not in pinot then we need to ask users to cast date type to varchar in query.
As we have all primitive data type support in pinot except Date. We want to add this support in pinot so that users will have good experience.
please let me know if you need more information
Thanks

For the DATE type, do you need time zone info, or the plain text such as 2022-10-13? To support it, internally we can store the value as either long (millis since epoch) or int (days since epoch).
We need to consider whether to support the comparison across different time types, e.g. comparing DATE with TIMESTAMP. We also want to introduce DATE_TIME in the future, which support custom date time pattern and time zone.

we are only looking for plain text at the moment. i think we can store as long (millis since epoch) that will help in future once we introduce DATE_TIME in the future.

Actually, in PrestoDB, there is a config to infer DATE type based on Pinot Schema: pinot.infer-date-type-in-schema.
https://prestodb.io/docs/current/connector/pinot.html#map-pinot-schema-to-presto-schema
I feel maybe we can implement this in Trino as a temporary workaround before this type is supported in Pinot.

+1 to add date as a first class data type. Will be useful as we integrate with tools other than presto/Trino

@xiangfu0 we are inserting data through trino and reading directly from superset. i think this property will not help much in this case but thanks to your suggestion.

Related to #9546

is this a duplicate of https://github.com/apache/pinot/issues/8045 or do we expect more / different from a DateTime type?

@walterddr we are looking to have DATE type in pinot, we can insert date type from trino and read from python connector (https://pypi.org/project/pinotdb/ ).  i am ok with Datetime as well but i need to make modification in connector code to make it compatible with date type only

@Jackie-Jiang

Related to #9546

we are looking for date type support only in which we don't have any time part. let me know your thoughts

@Jackie-Jiang @walterddr @xiangfu0 @kishoreg Guys, can we support this in near future?

@jatin5251 It is not on our top priority list, but contribution is very welcome.


Corrected typo in my profile, updated picture and social links

Updated some info and corrected typos

Docs Build status updates of commit 3774b1f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/gwyneth-penasiguenza.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/gwyneth-pena.jpg
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b24da46:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/gwyneth-penasiguenza.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/gwyneth-pena.jpg
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Brine Production

Hey!
I've run into a few problems with brine production.
Often the Solar Evaporation Tower's will get stuck at 300K despite it being day time.
Also brine production is unbalanced in the latest version.
http://i.imgur.com/Z06tpPo.png
I have 30 full size Evaporation towers but I still can't support 5 Elite Factories.
Thanks!
Sonar

Show  a Screen from the Data of the Plants.

http://i.imgur.com/lVtFOmN.png

There is a 0 muliplier. Multiplying production rate by 0 means you get 0 output. The biome your towers are in it bad for producting brine.

That is something that would be great for the wiki, you should put it up.
On Tue, Jul 7, 2015, 12:50 PM mercsniper<EMAIL_ADDRESS>wrote:

There is a 0 muliplier. Multiplying production rate by 0 means you get 0
output. The biome your towers are in it bad for producting brine.
—
Reply to this email directly or view it on GitHub
https://github.com/aidancbrady/Mekanism/issues/2803#issuecomment-119265748
.

Nope, the biome is fine. It's in a Normal Minecraft Dessert Biome. I should add this is seen on only some of the towers. I think it seems to be more of a packet problem, as brine is still produced. But considering how many towers I have it still should produce more brine than this. :/

Multiplier = biomeTemp x (activeSolars / 4) according to the wiki, I would
check the panels and make sure they are powered.
On Tue, Jul 7, 2015 at 1:04 PM, SonarSonic<EMAIL_ADDRESS>wrote:

Nope, the biome is fine. It's in a Normal Minecraft Dessert Biome. I
should add this is seen on only some of the towers. I think it seems to be
more of a packet problem, as brine is still produced. But considering how
many towers I have it still should produce more brine than this. :/
—
Reply to this email directly or view it on GitHub
https://github.com/aidancbrady/Mekanism/issues/2803#issuecomment-119269566
.

--
Brad

@SonarSonic http://wiki.aidancbrady.com/wiki/Solar_Evaporation_Plant#GUI <- it's in the Wiki...
Maybe try in another Biome?

It's not the Biome... I made a Plant in the Desert. Mult 2.0x... Which Version do you use?

If the output of the solar generators isnt touching a solar evaporation block, I don't think it is counted in the active solar count. Check and wrench the panels and let me know.

@mercsniper Thats not right. The Solars are not like a energy-source. You just need it. You can output the whole Energy out of the Solars.

@aidancbrady would this aspect be worthwhile to change?

I thinks the way it works is okay. The Solars heating the Plant up. If Aidan would change this the Plant should also work with alternative energy. So. Let's stay this way.

I'll go have a look at the code. It just think it is a sync problem, cause brine is still being produced. I think more should be produced tbh though.

@SonarSonic , if the multiplier inst being registered, the tower wouldn't be heating up, and then you are losing out on production. See what the code says.

Can't spot a problem with the code as such.

You can change production rates in the config.  Make sure you're using the latest Mekanism release.


resolves issue #9 by taking screen width instead of collectionView frame

Changed width from collectionView frame to Screen width (based on orientation).

Thx for PR!
Sorry, but u code left the same size of cells in landscape mode as portrait. This can confuse when numberOfDatesInOneScreen in configuration is does not match visible days.
I already fixed this in version 2.0.1


Segfault

Hi,
when I used Titan for one of my fuzzing targets, the static analysis crashed with a segfault. As the precondInfer is inherited by Beacon, I'm posting this here.
With some further investigation I found out that the crash appeared in file AbstractState.cpp, line 236 in function AbstractState::set:
if (valRange.empty() && memRange.empty()) {
    const Value *placeHodler = *valKeys.begin();
    valRng.insert({placeHodler, Interval::createTop(placeHodler->getType()->getIntegerBitWidth(), true)});
  }

gdb showed that variable placeHodler is a nullpointer, which is then dereferenced in the next line causing the segfault.
The CPP reference states for cases as this that "If the container is empty, the returned iterator value shall not be dereferenced." which is the case here.
I am not sure, why valKeys is empty though and if this might be an error in my configuration, but the other targets worked just fine so far.
My fuzzing target was flex with the following cstest.txt:
misc.c:106
skeletons.c:103
header_nr_main.c:34
bison_yylval_main.c:32
cxx_multiple_scanners_main.cc:46
dfa.c:147
no_bison_stub.c:36
bison_yylval_main.c:39
main.c:350
multiple_scanners_nr_main.c:42
mywc.c:11
header_r_main.c:65
bison_yylloc_main.c:28
bison_yylval_main.c:31
bison_yylloc_main.c:39
skeletons.c:108
libyywrap.c:27
tblcmp.c:597
tblcmp.c:652
sym.c:114
yylex.c:109
ccl.c:195
tables.c:409
mywc.c:14
multiple_scanners_nr_main.c:41
nfa.c:373
ccl.c:49
multiple_scanners_r_main.c:47
buf.c:61
buf.c:82
dfa.c:469
scanflags.c:66
bison_yylloc_main.c:32
bison_nr_main.c:31
header_r_main.c:53
scanflags.c:42
dfa.c:1037
tables_shared.c:68
scanflags.c:67
dfa.c:319
malloc.c:15
malloc.c:6
bison_yylval_main.c:27
tblcmp.c:465
filter.c:148
regex.c:140
no_bison_stub.c:26
main.c:1684
mywc.c:13
misc.c:270
libyywrap.c:26
dfa.c:536
gen.c:53
tables.c:225
skeletons.c:101
header_nr_main.c:35
bison_nr_main.c:30
gen.c:635
cxx_multiple_scanners_main.cc:38
mywc.c:17
nfa.c:602
scanflags.c:56
buf.c:91
top_main.c:53
regex.c:56
misc.c:255
tables_shared.c:65
misc.c:157
misc.c:330
multiple_scanners_r_main.c:48
ecs.c:145
malloc.c:16
tables.c:118
filter.c:153
sym.c:81
ccl.c:142
malloc.c:14
no_bison_stub.c:28
tblcmp.c:368
libyywrap.c:24
sym.c:132
misc.c:422
multiple_scanners_r_main.c:30
top_main.c:65
misc.c:610
regex.c:129
gen.c:179
sym.c:92
scanflags.c:48
gen.c:444
multiple_scanners_nr_main.c:43
cxx_multiple_scanners_main.cc:37
header_r_main.c:52
header_nr_main.c:30
tables.c:235
header_r_main.c:62
regex.c:51
scanopt.c:617
main.c:1459
header_r_main.c:33
libmain.c:26
buf.c:53
realloc.c:15
tblcmp.c:778
main.c:757
skeletons.c:223
misc.c:625
skeletons.c:143
yylex.c:48
misc.c:396
options.c:49
libmain.c:33
yylex.c:51
no_bison_stub.c:30
gen.c:956
options.c:186
tables.c:150

Could you please provide the bc file and the related options you used for Titan?

@vannussina I am unable to reproduce using 1fb90fffa4402. The provided target file causes beacon to exit with malformed target file -- exiting!. Which version of the code are you testing? Thanks.

The target file was for Titan, which supports multi-targeting. Beacon doesn't support multi-targets, so I suppose that's why it failed. I just posted this here because I analyzed Beacon's PrecondInfer as it's only in binary form in the Titan repo.
In the mentioned Titan issue above I attached all files from the out folder as well for another target where I came across the issue.

@vannussina  f5489224ec39aed3 fixes the crash.
The problem is that our ICFG fails to identify any caller of the target function. This could either due to that the target is indeed unreachable or the function pointer analysis (based on SVF) is unsound. The latter case needs to be visited case by case.
For instance, no callers for buf_prints  are found by the static analysis. If you have identified a caller of it at run time, then we can also try to fix the call graph to make it more sound.

@vannussina We will soon update the code for Titan, too.

update: I have examine the bitcode flex.bc. It seems that buf_prints is indeed unreachable. I think this specific issue is fixed.

Thanks! I'll check again with my targets as soon as the Titan repo is updated.

Thank you for bringing this matter to our attention:)
We have made updates to Titan's code based on this issue, and the precondInfer now handles your bc file.
If you have any further questions or encounter any issues, please feel free to reach out to us.

Thanks for the quick fix! I checked and now it works! 👍

@vannussina Yes. The filename can be ignored as it doesn't impact the functionality :)


training is not completing

I followed the guide for custom object detection android app.
[################################----------------------] 608/1000 | ETA: 12 minssuccess model files saved to bucket
the entire model was not trained
please advise on what might be the error

actually now that I checked I am getting this when I check the progress of my model:
error training failed or canceled

See issue #191


[Bug] Import-Module fails to import dbatools when it is a RequiredModule in the manifest

Environmental information
#### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.14409.1005
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1005
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

#### dbatools Module version:

Name    : dbatools
Path    : C:\Users\<USER>\Documents\WindowsPowerShell\Modules\dbatools\0.9.834\dbatools.psd1
Version : 0.9.834

Note the dbatools version installed is the one that works for me. I have tried 1.0.0, 1.0.32 and 1.0.34 that don't work.
SQL Server:
This isn't related to SQL Server.
Report
I have a very bizarre issue with dbatools that I'm struggling to understand. I have two modules - module_a and module_b. module_a has module_b as a RequiredModule in the manifest. module_b has dbatools as a RequiredModule in the module manifest (so they are chained together in that respect).
If I install dbatools, versions up to 0.9.834, it imports without issue if I run Import-Module module_a (which in turn imports module_b which in turn imports dbatools through the RequiredModules key in the manifests). If I install any version of dbatools from 1.0.0 onwards (tried 1.0.0, 1.0.32, 1.0.34) and run Import-Module module_a I get the following error:
Import-Module : Could not import
C:\Users\<USER>\Documents\WindowsPowerShell\Modules\dbatools\1.0.0\bin\smo\Microsoft.SqlServer.BatchParser.dll :
Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly 'Microsoft.SqlServer.BatchParser.dll' or one of its dependencies. The specified module could not be found."
At C:\Users\<USER>\Documents\WindowsPowerShell\Modules\dbatools\1.0.0\internal\scripts\smoLibraryImport.ps1:132 char:17
+                 [Reflection.Assembly]::LoadFrom($assemblyPath)
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : FileNotFoundException

At line:1 char:1
+ ipmo module_b
+ ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Microsoft.PowerShell.Commands.ImportModuleCommand

I get the same if I run Import-Module module_b.
If I remove dbatools from the RequiredModules in module_b and add the following to the top of module_b.psm1:
$dbatools_serialimport = $true
Import-Module dbatools

And then run Import-Module module_b it does import. But Import-Module module_a still fails with the same error.
As an aside, after importing using Import-Module module_b and then running get-dbatoolsconfig -name serialimport I get:
Module: import

FullName            Value Description
--------            ----- -----------
import.serialimport False Enabling this will cause the module to perform import in a serial manner, not parallelizin...

I would expect the value to be True?
I can raise an issue for this but I thought I'd bring it here as it's so weird I think it's something straightforward.
Note that the sqlps or sqlserver module are not being imported anywhere (asked to confirm by wsmelton)
Host used

[X] powershell.exe
[ ] ISE
[ ] VS Code
[ ] Other (please specify)

Errors Received
Error is shown in the Report above.
Steps to Reproduce
Steps shown in Report above.
Expected Behavior
I expected dbatools to import normally.
Actual Behavior
See Report above - dbatools fails to import at any other version beyond 0.9.834.

@wlansdowne Post code between three backticks - so 3 backticks, newline, post your code, newline, 3 backticks.

If this is still an issue can you verify that Visual C++ Redistributable Packages for Visual Studio 2013 is installed on the machine? We have seen some folks install this and it magically fixes it...just adding it here as I do not know that it is a be-all fix.


feat: implement oAuth2.0 user context

See : https://developer.twitter.com/en/docs/authentication/oauth-2-0/authorization-code
Solve : https://github.com/redouane59/twittered/issues/326

I started this PR @PhantomYdn , could you check this week-end too ?

@PhantomYdn the pull request is ready for a review, if you have some time :)

@PhantomYdn ?

Still no news of @PhantomYdn so I'm going to merge it now...

One missing commit added after the merge :
https://github.com/redouane59/twittered/commit/9f9edeea5d9fb7b1661d797126ffacb1151230bb


[Bug]: Step Selected Values Date Format

Apache Hop version?
2.7 and 2.8
Java version?
11
Operating system
Windows
What happened?
I noticed a strange body in Step Selected Values.
The Pipeline receives a DateTime, example: 2024-01-01 23:59:59, and with Step Selected Values it should convert it to date 2024-01-01.
Conversion is not occurring.
Would this be the same behavior as Step?

Issue Priority
Priority: 3
Issue Component
Component: Actions

If the original type is already a date there is no conversion happening, the only change that's happening is we only show the data formatted in the requested format mask. but behind the scenes, it's still a java date containing all the information.
If you want to strip the time you can either convert to a string, or use an other transform (formula) to set the time to 0 hours

I converted it to String yyyy-mm-dd and then to Date it reset the time.
tks


Revert rakefile to previous state

Fixes (hopefully) error that arises when installing the gem.
Bundler::GemNotFound: Could not find gem 'rspec' in any of the gem sources listed in your Gemfile or available on this machine.

Coverage remained the same at 99.441% when pulling 6eba3194ecb98cc989c59539b7212f1c28eaa5ea on revert-rakefile into 77391dcf366e2722b67e7a9f4525d9e0c8e14a43 on master.


Bugs in Recurring invoices

[x] sort by option under listing page
date not needed
change total price to Amount
change name to customer name
created time is missing
name sorting is not working under listing page
last invoice date is not displaying any dates
[x] invoice is not getting created automatically while creating recurring invoices
[x] profile name is not displayed under the detailed page

[x] error response message is not in proper format

ISSUE FIXED!


Remove opam pin  to avoid issues with opam 2.1

See https://github.com/ocaml/opam/issues/4501
Some more details on the issue can be seen in https://github.com/ocurrent/opam-repo-ci/pull/148/commits/a4cbe3f3ad89ba6d7816df9280b209639d4c72f6

Mmh, the pin was added in https://github.com/ocurrent/docker-base-images/pull/61. I’m not sure how to fix both issues :/

I think that the target here would be to have a precise switch invariant - that'll do exactly what the pin did before without triggering #61 (at least I don't think it should trigger that - if the package in the switch invariant is no longer available, I don't think that causes the solver to ignore the invariant).
I've no idea what that means in terms of having an opam 2.0 root initially, though 😭


Rewrite in rust

CC @dvzrv

Yep. I added that one to have a known good config but a simpler one would definitely help. Do you have any particular case in mind?


Tab titles in overflow menu sometimes not correct

The titles of tabs in the overflow menu are sometimes just labelled with the website name, instead of the title of the already loaded page.

This is still true, I might investigate it during the browser rework


Correct I2C Clock setting

The I2C clock setting should be changed, the settings used give a clock frequency of
Standard: 104 kHz
Fast Mode: 560 kHz
Fast Mode+: (not working at all)
Proposed settings:
Standard: 99 kHz
Fast Mode: 390 kHz
Fast Mode+: 930 kHz

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I've made a quick round of measurements and  the default values ar ok for me, so i'm closing this PR
UNOR4 Wire

I2C_MASTER_RATE_STANDARD 96kHz
I2C_MASTER_RATE_FAST 409kHz
I2C_MASTER_RATE_FASTPLUS not supported

C33 Wire1

I2C_MASTER_RATE_STANDARD 99kHz
I2C_MASTER_RATE_FAST 440kHz
I2C_MASTER_RATE_FASTPLUS 943kHz


update default theme ux/ui

Updates to the default theme to look more like this
@Gerrit0

The old default theme looked like this:

I created a small demo: https://native.okikio.dev/api

Hey! I really like this take on TypeDoc's default theme UI - it's definitely in need of a revamp. Funnily enough, I've been working over the past couple of weeks to redesign it as well, though the time I've had to dedicate to this (and by extension my progress) has been limited. If you're interested in discussing how we could work to improve the TypeDoc experience, I've been sharing my progress in the #typedoc channel on the TypeScript Community Discord server. Feel free to hop in if you want to chat, I'm always lurking there.

@Gerrit0 Should I close this pull request and wait for @futurGH complete design?


Calling string(fun)

This kind of looks like a bug: datafile_latlon = DIR * "/remapped_" * string(Interfacer.name) * ".nc", since name is just a method, this might as well be: datafile_latlon = DIR * "/remapped_name.nc", unless, for some reason, we overload Base.string(::typeof(::Interfacer.name)), which doesn't seem ideal.

Good catch! This function cgll2latlonz is also only called once in a test, so maybe we can move it to test/ and change this to datafile_latlon = DIR * "/remapped_name.nc"


Modification to how user found zulip input.

[x] Show Advertisement
[x]  Show At an organisation that's using Zulip? as Organization
[x]  Add Reddit below Hacker News
[x]  "Which one?" follow-up question when they pick "Review site".

(ignore the empty advertisement: fields they were created by mistake and are not actually possible to create by a user filling the form)

Merged, thanks @amanagr!


Add HTML/CSS language support

Helping out with #45!
I've run the HTML and CSS logos through an ASCII art generator and touched them up by hand.

Nice to see you took advantage of the multicolor feature for the ascii logo.
Unfortunately, it looks a little noisey/unpolished and also too big.
You're almost there @MaxJohansen
Looking forward to merge your PR :100:

I've shrunk the logos down to 21 lines, which is more in line with the other ones :-)
Also made them more uniform to avoid the business of more granular ASCII art, what do you think?


Doesn't launch on Ubuntu 20.10

Hi,
I was trying to cover it on itsfoss.com
Installed the application via the PPA but when I try to run it, it doesn't start and crashes.
In the terminal, it shows the following error message:
`sudo sysmontask
[sudo] password for abhishek:
/usr/lib/python3/dist-packages/sysmontask/sysmontask.py:5: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk as g , GLib as go
/usr/lib/python3/dist-packages/sysmontask/proc.py:1: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk as g , GLib as go,GdkPixbuf,Wnck, Gio
acquired root permission
(sysmontask:11757): Gtk-WARNING **: 17:26:28.271: Could not load image 'SysMonTask.png': Failed to open file “/usr/share/sysmontask/glade_files/SysMonTask.png”: No such file or directory
(sysmontask:11757): Gtk-WARNING **: 17:26:28.276: Could not load image 'usr/share/sysmontask/icons/SysMonTask.png': Failed to open file “/usr/share/sysmontask/glade_files/usr/share/sysmontask/icons/SysMonTask.png”: No such file or directory
memory tab initialising
nvme0n1
/bin/sh: 1: nvidia-smi: not found
no nvidia gpu found
Traceback (most recent call last):
File "/usr/bin/sysmontask", line 33, in
sys.exit(load_entry_point('sysmontask==1.1.0', 'console_scripts', 'sysmontask')())
File "/usr/lib/python3/dist-packages/sysmontask/sysmontask.py", line 555, in start
main=myclass()
File "/usr/lib/python3/dist-packages/sysmontask/sysmontask.py", line 93, in init
self.procinitialisation()
File "/usr/lib/python3/dist-packages/sysmontask/proc.py", line 248, in procInit
self.processSystemd=ps.Process(self.systemdId)
AttributeError: 'myclass' object has no attribute 'systemdId'
`

Hi, Thank you so much for reporting it.
By tonight, a newer version with a couple of other new feature will be added and this bugs with others will be fixed. Please wait till then.
I will be ping you when that is done.

Hi,
I have fixed the issue :) with a couple of other features.
Please update me if it works for you or in case of any other issue.

I confirm that the new version now launches and works on Ubuntu 20.10. I'll cover it on itsfoss.com next Monday.

Thank you, for your support for this project :)


[No QA] Create Money Request Header component

@mountiny @luacmartins please review
Right now to get this to show I do a couple of things
Web

Find an IOU report, since this has the same structure as the type of report we'll be showing here
Get the reportID for it
Apply this diff:

diff --git a/src/pages/home/ReportScreen.js b/src/pages/home/ReportScreen.js
index df5ba50e62..83aed35fed 100644
--- a/src/pages/home/ReportScreen.js
+++ b/src/pages/home/ReportScreen.js
@@ -39,6 +39,7 @@ import personalDetailsPropType from '../personalDetailsPropType';
 import getIsReportFullyVisible from '../../libs/getIsReportFullyVisible';
 import EmojiPicker from '../../components/EmojiPicker/EmojiPicker';
 import * as EmojiPickerAction from '../../libs/actions/EmojiPickerAction';
+import MoneyRequestHeader from '../../components/MoneyRequestHeader';

 const propTypes = {
     /** Navigation route context info provided by react navigation */
@@ -241,6 +242,16 @@ class ReportScreen extends React.Component {
         // (which is shown, until all the actual views of the ReportScreen have been rendered)
         const shouldAnimate = !shouldFreeze;

+        const moneyRequestHeader = this.props.report.type === 'iou' && this.props.report.reportID === '5571340985182399'
+            ? <MoneyRequestHeader report={this.props.report} policies={this.props.policies} personalDetails={this.props.personalDetails} />
+            : (<HeaderView
+                reportID={reportID}
+                onNavigationMenuButtonClicked={() => Navigation.navigate(ROUTES.HOME)}
+                personalDetails={this.props.personalDetails}
+                report={this.props.report}
+                policies={this.props.policies}
+            />);
+
         return (
             <ScreenWrapper
                 style={screenWrapperStyle}
@@ -273,13 +284,7 @@ class ReportScreen extends React.Component {
                                     errors={addWorkspaceRoomOrChatErrors}
                                     shouldShowErrorMessages={false}
                                 >
-                                    <HeaderView
-                                        reportID={reportID}
-                                        onNavigationMenuButtonClicked={() => Navigation.navigate(ROUTES.HOME)}
-                                        personalDetails={this.props.personalDetails}
-                                        report={this.props.report}
-                                        policies={this.props.policies}
-                                    />
+                                    {moneyRequestHeader}
                                 </OfflineWithFeedback>
                                 {Boolean(this.props.accountManagerReportID) && ReportUtils.isConciergeChatReport(this.props.report) && this.state.isBannerVisible && (
                                     <Banner

Replace<PHONE_NUMBER>182399 with the reportID of your IOU
Navigate to that report in your browser URL, i.e. http://localhost:8080/r/5571340985182399
If you want to test the Expense Report Only Features you can apply this diff

diff --git a/src/libs/ReportUtils.js b/src/libs/ReportUtils.js
index 7aae22feee..0f03fc99d1 100644
--- a/src/libs/ReportUtils.js
+++ b/src/libs/ReportUtils.js
@@ -105,7 +105,7 @@ function getReportParticipantsTitle(logins) {
  * @returns {Boolean}
  */
 function isExpenseReport(report) {
-    return lodashGet(report, 'type') === CONST.REPORT.TYPE.EXPENSE;
+    return true;
 }

Mobile

In addition to the diff above add the following so that every time you click and IOU you load the MoneyRequestHeader instead:

diff --git a/src/components/ReportActionItem/IOUAction.js b/src/components/ReportActionItem/IOUAction.js
index a7fe3f1710..6835776a87 100644
--- a/src/components/ReportActionItem/IOUAction.js
+++ b/src/components/ReportActionItem/IOUAction.js
@@ -67,7 +67,7 @@ const defaultProps = {

 const IOUAction = (props) => {
     const launchDetailsModal = () => {
-        Navigation.navigate(ROUTES.getIouDetailsRoute(props.chatReportID, props.action.originalMessage.IOUReportID));
+        Navigation.navigate(ROUTES.getReportRoute(props.action.originalMessage.IOUReportID));
     };

     const shouldShowIOUPreview = (

To view the Header, click "Pay" on the IOU preview:

Details
Adds the Money Request Header component into the code so that it can be used in Money Request Flows.
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/270587
Tests

Use the instructions above to apply a diff and load an IOU report to display in the header.
Load the header
Click the three dot menu item makes sure it load the menu in the correct spot
On Mobile or any other small screen, make sure that a back button is rendered and that takes you back to the Chat List Menu. On large screens (web and desktop) make sure there is no back button present.

Offline tests

QA Steps

No QA - this cannot be as there's no currently logic that loads this component

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

Note: The Header gap here is a different color. This is because the ScreenWrapper component in ReportScreen does not have a background color set and we'll most likely need to pass it in as a prop. However, because we're not showing the component yet I'm not sure this is the time to take care of this - since this exists outside of the component.

iOS

Android

@parasharrajat @bondydaa One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@parasharrajat I wanted to give you the extra context that this PR is blocking a set of downstream PRs that tie to functionality that we're trying to release in two weeks. It would be awesome if you're able to prioritize this one today so we can get it merged.

Updated, looking into what could be causing the discrepancy between native and web there, can't seem to figure it out (was looking yesterday as well) 🤔

maybe it's related to the data fetching for those reports, although the 2nd avatar seems to in the wrong position.

Could you add test steps to QA on workspace vs DM, and also paid versus unpaid (and any other cases where there are visual differences)
If the < button should only be present on certain screen sizes, let's add that as a check too

BUG: The tooltip point is not aligned with the icon.

This seems pretty minor and something we can tackle on a follow up. I won't block on it.

@yuwenmemon Looking good! Only comment- should the < button be present on all widths? Or only mobile width?
| Web | Desktop | IOS | Safari | Android | Chrome |
|-----|-----|-----|-----|-----|-----|
|||||||

@grgia the left caret should only be visible on native and mWeb since it takes you back to the LHN and that would be redundant on web/desktop.

I think so. Just waiting on the checklist

@parasharrajat apologies but what error are you getting?

Okay - @parasharrajat do you want me to do something about it? What are you getting at exactly? I tested and I did see a different JS error which I fixed - but I'm not seeing what you're reporting.

Can we pull out whatever remaining issues we're seeing, get a checklist in this PR, and then merge? Unfortunately this PR holds up a cascading series of downstream PRs for our upcoming conference. I'd love to get this merged and still keep working on whatever issues we're finding separately.

Also for what it's worth, we are going to purposefully break IOUs in the coming week.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Okay I'm merging this, for the other reviews on here if you have outstanding concerns please spin up new issue(s) for them and we can get them addressed then.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

I was going report the issue but then slack conversation leaded me here.
I think this line broke the header.
https://github.com/Expensify/App/blob/5f649d5045762177c6a6db08265d2d82655bce71/src/components/HeaderWithCloseButton.js#L168

Ah, my b. Will look at this.

@yuwenmemon feel free to assign me for review

Yep, our bad.

🚀 Deployed to staging by https://github.com/bondydaa in version: 1.3.11-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

We missed a case here, which led to this issue


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: istio-testing
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
1e20cd443f340c0d4b4c303daaeedad08a96b07c
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
1e20cd443f340c0d4b4c303daaeedad08a96b07c
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
1e20cd443f340c0d4b4c303daaeedad08a96b07c
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add support for binary data extension protocol and FP16 datatype

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3643
https://github.com/triton-inference-server/server/blob/main/docs/protocol/extension_binary_data.md
Type of changes
Please delete options that are not relevant.

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

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[x] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[x] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

/rerun-all

/rerun-all

/rerun-all

/rerun-all

@sivanantha321 Need a rebase after merging the inference client PR

/rerun-all

/rerun-all

/rerun-all

/rerun-all

/rerun-all

/rerun-all

/rerun-all

/rerun-all


Race condition: Incorrect saving of "running files" in workspaces.yml local state file

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Apr 10, 2018, 08:13
Commit https://gitlab.com/BuildStream/buildstream/commit/1d9ea9171dbf4c3244c9acf8da7a00c6825c3217 from merge request !315 cannot be working correctly.
What the above commit does:

Modifies the workspace data model in an isolated build task
Saves the modifications in the isolated build task

The result is that as soon as two workspaces are building in parallel, only one of the modifications can possibly be taken into account after the builds complete, the second update of the running files will discard the modifications made by the first, or rather, since the main task never updates it's data model except for doing Workspace.clear_running_files(), only one set of running files can ever be saved. For a session of bst --on-error continue build ..., it will only ever be the last modification which is saved.
I noticed that Workspace.clear_running_files() is also called in Element._assemble_done(), which is called in both the isolated task and in the main process after a build completes; but this part is not problematic, because it only hits that code path from the frontend if self_cached() is True, which only happens in the frontend, I thought this was done intentionally.
The solution to this is not to use lock files (there shalt be no lock/reload workspace file/modify/save/unlock performed in the tasks), rather; the changes which a task desires to make to the workspaces.yml must be sent back to the main process upon completion, such that the data model is maintained in the main process and writes are serialized there.

In GitLab by [Gitlab user @tristanvb] on Apr 10, 2018, 08:16
changed the description

In GitLab by [Gitlab user @tlater] on Apr 10, 2018, 09:47
created branch 352-race-condition-incorrect-saving-of-running-files-in-workspaces-yml-local-state-file

In GitLab by [Gitlab user @tristanvb] on Apr 10, 2018, 11:43
mentioned in commit ea1272b8e6817e377e9a72b877d48bce20d5befb

In GitLab by [Gitlab user @tristanvb] on Apr 10, 2018, 13:12
mentioned in commit a9cbb0f7074286f5323954d327bc923c0028e7c0

In GitLab by [Gitlab user @tristanvb] on Apr 10, 2018, 13:28
closed via merge request !376


[scfsd] - CSV Output

With or without header

Moved core processor to its own lib. Anyway can create extracts as they see fit


Miscellaneous Pipeline Fixes (draft)

Description

Trying to fix codecov decrease with explicit flags separating coverage for the 2 build (pr-gate & nightly)
Add flaky markers to unstable tests.

Related Issues

Checklist:

[x] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[x] I have updated the documentation accordingly.
[x] This PR is being made to staging branch and not to main branch.

Codecov Report

Merging #1545 (67fdf4e) into staging (9f19411) will increase coverage by 0.08%.
The diff coverage is 94.25%.

:exclamation: Current head 67fdf4e differs from pull request most recent head 50b18b2. Consider uploading reports for the commit 50b18b2 to get more accurate results

@@             Coverage Diff             @@
##           staging    #1545      +/-   ##
===========================================
+ Coverage    62.12%   62.21%   +0.08%
===========================================
  Files           84       84
  Lines         8397     8442      +45
===========================================
+ Hits          5217     5252      +35
- Misses        3180     3190      +10

Flag
Coverage Δ

pr-gate
62.21% <94.25%> (?)

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

Impacted Files
Coverage Δ

recommenders/evaluation/spark_evaluation.py
86.66% <ø> (ø)

recommenders/evaluation/python_evaluation.py
93.68% <94.11%> (-3.21%)
:arrow_down:

recommenders/utils/spark_utils.py
96.15% <100.00%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #1545 (67fdf4e) into main (2770922) will decrease coverage by 12.17%.
The diff coverage is 100.00%.

:exclamation: Current head 67fdf4e differs from pull request most recent head 5d1e1fe. Consider uploading reports for the commit 5d1e1fe to get more accurate results

@@             Coverage Diff             @@
##             main    #1545       +/-   ##
===========================================
- Coverage   74.38%   62.21%   -12.18%
===========================================
  Files          84       84
  Lines        8441     8442        +1
===========================================
- Hits         6279     5252     -1027
- Misses       2162     3190     +1028

Flag
Coverage Δ

pr-gate
62.21% <100.00%> (?)

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

Impacted Files
Coverage Δ

recommenders/utils/spark_utils.py
96.15% <100.00%> (+0.15%)
:arrow_up:

...ecommenders/models/newsrec/io/mind_all_iterator.py
12.21% <0.00%> (-86.65%)
:arrow_down:

recommenders/models/newsrec/io/mind_iterator.py
15.67% <0.00%> (-82.71%)
:arrow_down:

...ommenders/models/deeprec/io/sequential_iterator.py
15.85% <0.00%> (-81.94%)
:arrow_down:

recommenders/models/newsrec/models/base_model.py
30.90% <0.00%> (-59.40%)
:arrow_down:

...deeprec/models/sequential/sequential_base_model.py
46.97% <0.00%> (-48.33%)
:arrow_down:

recommenders/models/geoimc/geoimc_data.py
41.66% <0.00%> (-44.80%)
:arrow_down:

...enders/models/deeprec/io/dkn_item2item_iterator.py
45.61% <0.00%> (-42.11%)
:arrow_down:

...menders/models/deeprec/models/graphrec/lightgcn.py
51.47% <0.00%> (-40.24%)
:arrow_down:

recommenders/datasets/mind.py
0.00% <0.00%> (-30.85%)
:arrow_down:

... and 11 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 2770922...5d1e1fe. Read the comment docs.

Codecov Report

Merging #1545 (50b18b2) into staging (9f19411) will increase coverage by 0.08%.
The diff coverage is 94.25%.

:exclamation: Current head 50b18b2 differs from pull request most recent head edc8377. Consider uploading reports for the commit edc8377 to get more accurate results

@@             Coverage Diff             @@
##           staging    #1545      +/-   ##
===========================================
+ Coverage    62.12%   62.21%   +0.08%
===========================================
  Files           84       84
  Lines         8397     8442      +45
===========================================
+ Hits          5217     5252      +35
- Misses        3180     3190      +10

Flag
Coverage Δ

pr-gate
62.21% <94.25%> (?)

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

Impacted Files
Coverage Δ

recommenders/evaluation/spark_evaluation.py
86.66% <ø> (ø)

recommenders/evaluation/python_evaluation.py
93.68% <94.11%> (-3.21%)
:arrow_down:

recommenders/utils/spark_utils.py
96.15% <100.00%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #1545 (2967412) into staging (9f19411) will increase coverage by 0.08%.
The diff coverage is 94.25%.

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

@@             Coverage Diff             @@
##           staging    #1545      +/-   ##
===========================================
+ Coverage    62.12%   62.21%   +0.08%
===========================================
  Files           84       84
  Lines         8397     8442      +45
===========================================
+ Hits          5217     5252      +35
- Misses        3180     3190      +10

Flag
Coverage Δ

pr-gate
62.21% <94.25%> (?)

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

Impacted Files
Coverage Δ

recommenders/evaluation/spark_evaluation.py
86.66% <ø> (ø)

recommenders/evaluation/python_evaluation.py
93.68% <94.11%> (-3.21%)
:arrow_down:

recommenders/utils/spark_utils.py
96.15% <100.00%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #1545 (3d978fc) into staging (9f19411) will increase coverage by 0.08%.
The diff coverage is 94.25%.

@@             Coverage Diff             @@
##           staging    #1545      +/-   ##
===========================================
+ Coverage    62.12%   62.21%   +0.08%
===========================================
  Files           84       84
  Lines         8397     8442      +45
===========================================
+ Hits          5217     5252      +35
- Misses        3180     3190      +10

Flag
Coverage Δ

pr-gate
62.21% <94.25%> (?)

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

Impacted Files
Coverage Δ

recommenders/evaluation/spark_evaluation.py
86.66% <ø> (ø)

recommenders/evaluation/python_evaluation.py
93.68% <94.11%> (-3.21%)
:arrow_down:

recommenders/utils/spark_utils.py
96.15% <100.00%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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


Lot of account with real mail are present on first start

Hi
I test your application, and I found a problem in admin panel : Lot of real mail are present on first start.

I think is not good for privacy :)
And It's surprise me on fresh install.
So, is it possible to delete these accounts at the first installation?
Regards

Hi,
those accounts are fakes and generated at startup (see generateFixtures in https://github.com/jbl2024/latelier#configuration). It was a way for me to test the application with some kind of data.
Do you have set up a config file with this parameter set ?
Best regards

Okay, thank you :)
Yes, generateFixture is set to true so, the website generate fakedata :sweat_smile:
Thank for your anwser


Update manifest.yml

@miteshgurjar i am closing this pull request. we don't need the default app name changed. if you are interested though, we do need to update manifest.yml to allow for random routes (https://github.com/Call-for-Code/Solution-Starter-Kit-Cooperation-2020/issues/76). if you want to submit a pull request for that it would be welcomed.


Improve PR #315 for GitHub Action setting

Changed log

Improve PR #315.

Changed log

Improve PR #315.

@peter279k  Many thanks for your time.


Some Programming Participations are not gradable

Describe the bug
One of our courses encountered the problem that some participations (~10) for programming tasks are not gradable via artemis:

The participation in this example contains two submissions.

In GitLab I see only one push event. Therefore, I assume that both commits are pushed via one push to the repository.
If you are looking on the dates, it seems that the first submission has a later date.
Nevertheless, the second submission is the second commit and should be gradable.
If I delete the first submission, it is gradable again (at least that was the case for the other cases)
I assume that could to be related to #4830 .
To Reproduce
Unclear
Expected behavior
The participation should be gradable.
Screenshots
No response
What browsers are you seeing the problem on?
Firefox
Additional context
No response
Relevant log output
No response

As always: Feel free to adopt the priority. I assume that to be high, as it effects the grading of tasks.

So in general, it makes sense that the order is as it is as we don't care about the order within the system but the one with the latest submission date.
The actual question is why there are these two distinct submissions.
Could you submit

The Gitlab push event with as much information as possible
The Git history (Commit date & Commit hash) from everything between those two given commit hashes (including).

Of course, you may redact any confidential information.

Push events (I don't know their current API)

Upper Date Time: 2022-05-08T19:42:09Z
Lower Date Time: 2022-05-04T16:11:12Z
Git Log:
commit d87ff7a83de02eb9a4280722e8fd5706f8e3f123 (HEAD -> main, origin/main, origin/HEAD)
Author: STUDENT
Date:   Sun May 8 21:42:04 2022 +0200

    Added new ****.

commit 0f599ad3348a25a5c36be85f5fc7634ce2729dd6
Author: STUDENT
Date:   Sun May 8 21:38:33 2022 +0200

    Added new maven ****

commit 844a40ceca1b75058d53ff10d394dfce9d4b481b
Author: INSTRUCTOR
Date:   Mon Apr 25 13:54:26 2022 +0000

    Exercise-Template pushed by Artemis

This looks like it requires substantial research as these are, on the first look, two different things and partially things we already intended to have solved.
Once I have the time, I'll look into it, so I'll assign myself for now, but this will be the earliest in a week. If anyone else wants to do that, feel free to reassign.

Regarding https://github.com/ls1intum/Artemis/issues/5145#issue-1246173417 :
The instructor of this course has updated the test repository during the conduction of the task.
Nevertheless, all of our courses have cases of https://github.com/ls1intum/Artemis/issues/5145#issuecomment-1137385536 .

@julian-christl feel also free to contact me via Slack. We are very interested to fix this bug, since it affects many exercises :)

Some related issue was also that some students pushed to the old "master" branch instead of "main". Since builds are triggered, artemis made some strange ordering (e.g., the first commit in the submission view (which was the last commit on the "master" branch is the one that got graded by artemis. Therefore, the results are not shown / the participation was not marked as assessed)

Some related issue was also that some students pushed to the old "master" branch instead of "main".

This actually is even worse, as tutors could also assess a wrong version of the code as described in https://github.com/ls1intum/Artemis/issues/5165


Implement perftest duration slider

Implement perftest duration slider.
this slider bar works in both directions depending on  time-select and weight.

LGTM!!


what is a "public room"

tbh this is not a problem that is limited to the spec, and it probably overlaps with other existing issues, but I'm going to file it here for want of anywhere better right now.
Essentially, the term "public room" (or its counterpart, "private room") gets bandied around (most recently in https://github.com/matrix-org/synapse/pull/7639), but there is no good definition of what defines whether a room is public or private.
For example, is it determined by:

the join rule (https://matrix.org/docs/spec/client_server/r0.6.1#m-room-join-rules)
the history visibility (https://matrix.org/docs/spec/client_server/r0.6.1#module-history-visibility) (which to be fair doesn't use the words public or private, but tends to get tied up here)
whether the room is included in the results of publicRooms (https://matrix.org/docs/spec/client_server/r0.6.1#get-matrix-client-r0-publicrooms)
which preset was used to create the room with /createRoom (https://matrix.org/docs/spec/client_server/r0.6.1#post-matrix-client-r0-createroom)

fwiw riot-web considers the join rules as the single identifier of public. The history visibility goes a step further to indicate how searchable/on-the-record it is.
In my mind the presets are just templates and no different from someone specifying the state events manually.

another thing that sometimes get confused here is the dm flag.

fwiw riot-web considers the join rules as the single identifier of public. The history visibility goes a step further to indicate how searchable/on-the-record it is.

I think this is probably fair. We could work towards having that be what we "normally" mean by public/private, and make it explicit when we are using an alternative meaning.
tbh a lot of the problem here is the unfortunate name of /publicRooms.

(synapse's config file appears to use public to refer to publicRooms :-S )

In my mind the presets are just templates and no different from someone specifying the state events manually.

the confusing thing here is that, if you don't choose one, the preset is chosen based on the visibility, not the join rules. :/

table flip

After discussions on matrix with @ara4n, @turt2live and @richvdh, we've decided that the presets are a suitable way of describing whether a room is "private" or "public", due to:

Riot(-web at least) is using the presets when creating a public vs. private rooms

Though it's important to note that it later uses the join rules for the lock/globe icons

Synapse also deciding on a preset to use when creating a room (if one is not provided), based on other parameters provided by the user.

As such, we're going to use presets to differentiate between public/private rooms in https://github.com/matrix-org/synapse/pull/7639.

@anoadragon453 how do you plan to use presets to determine if a room is public after creation?

or when the room becomes "private" under some metric.

oh, I guess for the particular synapse issue it doesn't matter. For notifications it matters.

Indeed, my issue was just at creation, not run time. Presets seem to only solve the former.

@anoadragon453

After discussions on matrix with @ara4n, @turt2live and @richvdh, we've decided that the presets are a suitable way of describing whether a room is "private" or "public"

I think this is only true in the context of https://github.com/matrix-org/synapse/pull/7639. I think it's still the case that the terms "public" and "private" are unclear in the general case.


After upgrading to 3.8.1, nuxt dev breaks if you have a .env file with DEBUG=true

Environment

Operating System: Linux
Node Version:     v18.18.2
Nuxt Version:     3.8.1
CLI Version:      3.9.1
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
Look at the console:
https://codesandbox.io/p/sandbox/gracious-paper-mylhf8
Describe the bug
If you have a .env file with DEBUG=true, the dev server will throw a bunch of errors related to finding node modules:
⚙ [nuxt] warmup for node:https failed with: Failed to load url node:https (resolved id: node:https). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 1)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmupViteServer (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:854:3)

Additional context
The problem doesn't seem to happen with <3.8.0 versions, I had just upgraded from 3.7.4 to 3.8.1 with npx nuxi upgrade. Tried with multiple node versions (~18.xx, ~20.xx) in WSL2.
The log attached was taken from the reproduction link (hence the warning about the Node version).
Logs
yarn run v1.22.19
$ nuxt dev

[6:13:31 PM]  WARN  Current version of Node.js (16.17.0) is unsupported and might cause issues.
       Please upgrade to a compatible version >= 18.0.0.

 Please consider upgrading to Node.js >= 18.

[nuxt] nitro:init: 0.519ms                                          6:13:34 PM
[nuxt] ready: 0.853ms                                               6:13:34 PM
[nuxt] listen: 0.017ms                                              6:13:34 PM
[nuxt] devtools:customTabs: 0.172ms                                 6:13:34 PM
[nuxt] components:dirs: 0.013ms                                     6:13:34 PM
[nuxt] app:resolve: 2.004ms                                         6:13:34 PM
[nuxt] pages:extend: 0.039ms                                        6:13:34 PM
[nuxt] prepare:types: 0.357ms                                       6:13:34 PM
[nuxt] components:extend: 1.089ms                                   6:13:34 PM
[nuxt] app:templates: 18.791ms                                      6:13:34 PM
ℹ Compiled app-component.mjs in 4.48ms                             6:13:34 PM
ℹ Compiled types/app.config.d.ts in 4.59ms                         6:13:34 PM
ℹ Compiled app.config.mjs in 4.83ms                                6:13:34 PM
ℹ Compiled nitro.client.mjs in 5.17ms                              6:13:34 PM
ℹ Compiled css.mjs in 5.18ms                                       6:13:34 PM
ℹ Compiled fetch.mjs in 5.47ms                                     6:13:34 PM
ℹ Compiled error-component.mjs in 5.77ms                           6:13:34 PM
ℹ Compiled layouts.mjs in 6.14ms                                   6:13:34 PM
ℹ Compiled middleware.mjs in 6.33ms                                6:13:34 PM
ℹ Compiled types/nitro-nuxt.d.ts in 6.26ms                         6:13:34 PM
ℹ Compiled nuxt.config.mjs in 6.61ms                               6:13:34 PM
ℹ Compiled types/plugins.d.ts in 6.66ms                            6:13:34 PM
ℹ Compiled paths.mjs in 6.37ms                                     6:13:34 PM
ℹ Compiled root-component.mjs in 6.57ms                            6:13:34 PM
ℹ Compiled test-component-wrapper.mjs in 6.18ms                    6:13:34 PM
ℹ Compiled types/vue-shim.d.ts in 6.44ms                           6:13:34 PM
ℹ Compiled vue-router-stub.d.ts in 6.51ms                          6:13:34 PM
ℹ Compiled pages.mjs in 6.8ms                                      6:13:34 PM
ℹ Compiled unhead-plugins.mjs in 7.05ms                            6:13:34 PM
ℹ Compiled components.d.ts in 7.28ms                               6:13:34 PM
ℹ Compiled components.plugin.mjs in 6.88ms                         6:13:34 PM
ℹ Compiled component-names.mjs in 7.74ms                           6:13:34 PM
ℹ Compiled components.islands.mjs in 7.96ms                        6:13:34 PM
ℹ Compiled devtools/settings.mjs in 12.11ms                        6:13:34 PM
ℹ Compiled imports.d.ts in 11.19ms                                 6:13:34 PM
ℹ Compiled imports.mjs in 12.13ms                                  6:13:34 PM
ℹ Compiled types/schema.d.ts in 14.54ms                            6:13:34 PM
ℹ Compiled types/imports.d.ts in 56.48ms                           6:13:34 PM
ℹ Compiled plugins/server.mjs in 109.39ms                          6:13:34 PM
ℹ Compiled plugins/client.mjs in 128.17ms                          6:13:34 PM
[nuxt] imports:extend: 0.129ms                                      6:13:35 PM
[nuxt] app:templatesGenerated: 3ms                                  6:13:35 PM
[nuxt] build:before: 0.016ms                                        6:13:35 PM
[nuxt] vite:extend: 0.731ms                                         6:13:35 PM
[nuxt] vite:extendConfig: 1.189ms                                   6:13:35 PM
[nuxt] vite:configResolved: 0.023ms                                 6:13:35 PM
[nuxt] builder:chokidar:watch: 715.152ms                            6:13:35 PM
[nuxt] vite:serverCreated: 1.716ms                                  6:13:35 PM
[nuxt] server:devHandler: 0.116ms                                   6:13:35 PM
[nuxt] vite:extendConfig: 0.565ms                                   6:13:35 PM
[nuxt] vite:configResolved: 0.016ms                                 6:13:35 PM
[nuxt] build:manifest: 0.129ms                                      6:13:35 PM
[nuxt] vite:serverCreated: 0.225ms                                  6:13:36 PM
[nuxt] schema:beforeWrite: 0.011ms                                  6:13:36 PM
ℹ Vite client warmed up in 1386ms                                  6:13:37 PM
[6:13:37 PM] ⚙ [nuxt] warmup for node:http failed with: Failed to load url node:http (resolved id: node:http). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmupViteServer (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:854:3)
[6:13:37 PM] ⚙ [nuxt] warmup for node:https failed with: Failed to load url node:https (resolved id: node:https). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 1)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmupViteServer (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:854:3)
[6:13:37 PM] ⚙ [nuxt] warmup for node:zlib failed with: Failed to load url node:zlib (resolved id: node:zlib). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 3)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[6:13:37 PM] ⚙ [nuxt] warmup for node:stream failed with: Failed to load url node:stream (resolved id: node:stream). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 4)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[6:13:37 PM] ⚙ [nuxt] warmup for node:buffer failed with: Failed to load url node:buffer (resolved id: node:buffer). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 5)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[6:13:37 PM] ⚙ [nuxt] warmup for node:util failed with: Failed to load url node:util (resolved id: node:util). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 6)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[6:13:37 PM] ⚙ [nuxt] warmup for node:url failed with: Failed to load url node:url (resolved id: node:url). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 7)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[6:13:37 PM] ⚙ [nuxt] warmup for node:net failed with: Failed to load url node:net (resolved id: node:net). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 8)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[6:13:37 PM] ⚙ [nuxt] warmup for node:fs failed with: Failed to load url node:fs (resolved id: node:fs). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 9)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[6:13:37 PM] ⚙ [nuxt] warmup for node:path failed with: Failed to load url node:path (resolved id: node:path). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 10)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[nuxt] schema:written: 0.021ms                                      6:13:37 PM
[nuxt] nitro:build:before: 0.054ms                                  6:13:37 PM
[6:13:38 PM] ⚙ [nuxt] warmup for node:crypto failed with: Failed to load url node:crypto (resolved id: node:crypto). Does the file exist?

  at loadAndTransform (node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:839:7)
  at async Promise.all (index 0)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 5)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 2)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
  at async Promise.all (index 3)
  at async warmup (node_modules/@nuxt/vite-builder/dist/shared/vite-builder.20543d77.mjs:849:7)
[nitro] rollup:before: 614.505ms                                    6:13:38 PM
ℹ Vite server warmed up in 2203ms                                  6:13:38 PM
✔ Nitro built in 745 ms                                      nitro 6:13:39 PM
[nitro] compiled: 0.572ms                                           6:13:39 PM
[nuxt] build:done: 2.530s                                           6:13:39 PM
> Nitro Start (9ms)
[nitro] dev:reload: 378.208ms                                       6:13:39 PM
[nitro-runtime] request: 0.558ms
[nuxt-app] app:created: 0.972ms
[nuxt-app] vue:setup: 0.025ms
[nuxt-app] app:rendered: 0.013ms
[nitro-runtime] render:html: 0.033ms
[nitro-runtime] render:response: 0.016ms
[nitro-runtime] beforeResponse: 0.013ms
[nitro-runtime] afterResponse: 0.019ms
[nitro-runtime] request: 0.081ms
[nuxt-app] app:created: 0.47ms
[nuxt-app] vue:setup: 0.012ms
[nuxt-app] app:rendered: 0.016ms
[nitro-runtime] render:html: 0.014ms
[nitro-runtime] render:response: 0.008ms
[nitro-runtime] beforeResponse: 0.01ms
[nitro-runtime] afterResponse: 0.011ms

Hi,
I confirm, I got the same bug.

Thanks for spotting! This is a non-fatal issue but should be resolved in https://github.com/nuxt/nuxt/pull/24162.


Support installation in upstreams

Note that the include directories necessary to use libbtf are capable of being installed.

I believe that this will make it possible for upstream users of this library to install libbtf when they attempt to install themselves.

coverage: 95.204%. remained the same
when pulling 11c7b4289ade59e199a9fa55b91dbe2f3248045b on hawkinsw:main
into 69e02688e89352d49c72707c2819448515d856df on Alan-Jowett:main.


Perceptually uniform cyclic colormaps

I'm considering packing proplot with some custom cyclic colormaps. Below is an example that I'm toying with.
@bradyrx It turns out that luminance + chroma as sine curves in quadrature give you uniform, colorblind-friendly single hue maps! I tried making a cyclic multihue map this way but it turns out to be way harder. HSL and HPL give weird zig-zags in chroma/luminance and it's almost impossible to "thread the needle" between valid HCL values (i.e. values that translate to non-impossible RGB colors).
This example might break if you try it on master branch -- I did some bugfixing on #47 that came about while just fixing the docstrings. But feel free to play with it after #47 is merged.
import proplot as plot
import numpy as np
space = 'hsl'
hue = 150
reverse = False
luminance_shift = 0
saturation_shift = np.pi/2
luminance_offset = 0
saturation_offset = 0
luminance_scale = 80
saturation_scale = 60
luminance = lambda x: luminance_offset + 50 + luminance_scale*np.sin(x*2*np.pi + luminance_shift)/2
saturation = lambda x: saturation_offset + 50 + saturation_scale*np.sin(x*2*np.pi + saturation_shift)/2
cmap = plot.PerceptuallyUniformColormap.from_hsl('_cyclic',
    # hue=(hue, hue + 360)[::1 - 2*reverse], # cyclic hues!
    hue=hue, # constant hue!
    saturation=saturation, luminance=luminance,
    cyclic=True, space=space)
cmap = cmap.shifted(180) # optionally shift
f = plot.show_channels(cmap, rgb=False, axwidth=1.5)
f, ax = plot.subplots()
ax.pcolormesh(np.ones((30,30)).cumsum(axis=0) % 10, cmap=cmap, colorbar='b')
ax.format(suptitle='Cyclic colormap test')

Here's a blue one:
space = 'hcl'
hue = 'medium blue'

And a red one (...I'm done now).
space = 'hcl'
hue = 'brick red'

Throwing in some hue wiggles makes it a bit more interesting (might use something like this one!).
import proplot as plot
import numpy as np
space = 'hcl'
hue = 'brick red'
reverse = False
luminance_shift = 0
saturation_shift = np.pi/2
hue_offset = 20
luminance_offset = 0
saturation_offset = 0
hue_scale = 50
luminance_scale = 60
saturation_scale = 60
hue = lambda x: hue_offset + hue_scale*np.sin(x*2*np.pi)/2
luminance = lambda x: luminance_offset + 50 + luminance_scale*np.sin(x*2*np.pi + luminance_shift)/2
saturation = lambda x: saturation_offset + 50 + saturation_scale*np.sin(x*2*np.pi + saturation_shift)/2
cmap = plot.PerceptuallyUniformColormap.from_hsl('_cyclic',
    # hue=(hue, hue + 360)[::1 - 2*reverse], # cyclic hues!
    hue=hue, # constant hue!
    saturation=saturation, luminance=luminance,
    cyclic=True, space=space)
cmap = cmap.shifted(180) # optionally shift
f = plot.show_channels(cmap, rgb=False, axwidth=1.5)
f, ax = plot.subplots()
ax.pcolormesh(np.ones((30,30)).cumsum(axis=0) % 10, cmap=cmap, colorbar='b')
ax.format(suptitle='Cyclic colormap test')

This looks great!


didUpdateResource not working in background

When I implement this in the parent app:
[self.sentinel addListenerForResource:@"message" withCompletionHandler:^(id response) {
[weakSelf.parentAppMessage setText:response];
}];
and this in the extension:
[self.sentinel didUpdateResource:@"message" withContent:self.userInput.text];
Then it is not working in the background.

I where trying out RBSentinal because I am experiencing a 4 second delay when I use  [WKInterfaceController openParentApplication:...] when running on a physical watch (simulator is working fiine).

will look into this.. thanks for the feedback


Renamed ENV vars to use F8 prefix and binary from alm to wit

This PR is a follow up of #1450

@kwk please, read the description :). We need to wait for @aslakknutsen PR #1450

@kwk please, read the description :). We need to wait for @aslakknutsen PR #1450

What do you mean? You've replace a binaries name (BINARY_CLIENT_BIN=$(INSTALL_PREFIX)/wit-cli) and that clearly isn't what's in the description or the title of this PR.

@kwk My comment means that the Makefile was modified in a previous PR. So, of course, I didn't modified the Makefile, and thereby there were several occurrences of almighty.

What do you mean? You've replace a binaries name (BINARY_CLIENT_BIN=$(INSTALL_PREFIX)/wit-cli) and that clearly isn't what's in the description or the title of this PR.

Did you point it this out before ? The commit message describes what I did in this PR as well.

[test]

Codecov Report

Merging #1451 into master will decrease coverage by 0.12%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #1451      +/-   ##
==========================================
- Coverage   60.31%   60.18%   -0.13%
==========================================
  Files         118      118
  Lines       10981    10981
==========================================
- Hits         6623     6609      -14
- Misses       3720     3733      +13
- Partials      638      639       +1

Impacted Files
Coverage Δ

resource/require.go
80% <ø> (ø)
:arrow_up:

main.go
0% <0%> (ø)
:arrow_up:

configuration/configuration.go
75.2% <100%> (ø)
:arrow_up:

remoteworkitem/github.go
77.14% <0%> (-22.86%)
:arrow_down:

models/transaction.go
50% <0%> (-20%)
:arrow_down:

remoteworkitem/scheduler.go
53.65% <0%> (-9.76%)
:arrow_down:

tool/alm-cli/main.go

tool/wit-cli/main.go
0% <0%> (ø)

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 1a14a72...6462b8f. Read the comment docs.


[Bug]: Sometimes the clipboard history provided by "Clipboard plugin" is not displayed on the active desktop.

Before submitting your bug report, please confirm you have completed the following steps

[X] Searched the issue is not already listed in the Issue List (I've searched it)
[X] Searched in the Quicksilver Users' Group for questions relating to tech support.
[X] Downloaded the latest version of Quicksilver for your system and confirmed the issue still persists.

Bug description
Hi.
Sometimes (not always) the clipboard history provided by "Clipboard plugin" is not displayed on the active desktop.

Steps to reproduce

using two monitors, use the mission control function to create more spaces.
move to the second space and invoke Quicksilver
copy some value (example: text from the browser)
Press the ⌘L shortcut to open the clipboard history
Observe that you can't see the clipboard history. Reason => the clipboard history is opened on the first space, but you (an quicksilver interface) are on the second space

Expected behavior
I expect see the clipboard history on the same space than Quicksilver interface.
MacOS Version
macOS 13
Quicksilver Version
2.4.2 (4041)
Relevant Plugins
Clipbaord plugin. Version 1.8.1
Crash Logs or Spindump
No response
Screenshots
No response
Additional info
No response

Any update related to this issue?

No, sorry. I don't have a second monitor to test, and I'm (slowly) trying to focus on the crashes and race conditions first.