Upgrade version 0.0.5

Add ship object for drawing gif

Codecov Report

Merging #7 (4e6cd5b) into main (d6d860d) will decrease coverage by 2.28%.
The diff coverage is 95.83%.

:exclamation: Current head 4e6cd5b differs from pull request most recent head 647e5b5. Consider uploading reports for the commit 647e5b5 to get more accurate results

@@             Coverage Diff             @@
##              main       #7      +/-   ##
===========================================
- Coverage   100.00%   97.71%   -2.29%
===========================================
  Files            8        8
  Lines          381      394      +13
===========================================
+ Hits           381      385       +4
- Misses           0        9       +9

Flag
Coverage Δ

unittests
97.71% <95.83%> (-2.29%)
:arrow_down:

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

Impacted Files
Coverage Δ

shipmmg/draw_obj.py
76.92% <93.33%> (-23.08%)
:arrow_down:

shipmmg/__init__.py
100.00% <100.00%> (ø)

shipmmg/kt.py
100.00% <100.00%> (ø)

shipmmg/mmg_3dof.py
100.00% <100.00%> (ø)

shipmmg/ship_obj_3dof.py
100.00% <100.00%> (ø)

tests/test_shipmmg.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Before merging, we have to set Pypi and Anaconda....

https://github.com/ShipMMG/shipmmg/issues/9
Solve this issue


[Gestures] Changing to final workspace shows first workspace briefly

At the end of the video you can see the first workspace briefly appear behind the windows.
https://user-images.githubusercontent.com/29136904/179372396-d0077368-e9a2-4c7c-8f41-04ce40c4e42f.mp4

does this also happen if you wait for the animation to end and then switch? You did 2 quick switches.

https://user-images.githubusercontent.com/29136904/179372581-3da7f290-96d0-4720-8e92-bec65a4b006f.mp4
yes, if I wait for the animation to finish, then swipe again it will still happen

alr, will try to fix tmr

fixed in 0026414f9bbefed9ba4838b600dd2566968bfc8a


Fixes #5747: Only activate sound output device

Fixes #5747 by only activating the sound output device instead of both, input and output devices.
This works around the problem that some microphone monitoring tools (like "Micro Snitch") were activated by just playing a sound inside a remote session.
This also fixes the problem that starting with macOS 10.15 sometimes the audio device wasn't ready when sound was starting to play. The fix is to check if the audio engine is running, and if it isn't, starting it inside rdpsnd_mac_start.

@freerdp-bot test

@lemonmojo could you run clang-format on your patch?

@akallabeth done!

@freerdp-bot test


Refactor internal components

Proposal
I've been thinking about our code and I think that it's a bit coupled, making difficult to manage the life cycle of the items internally sometimes. (During the last months we have had several issues related with the scaler lifecycle, not properly closed connections, etc) and I don't like so much some parts of the core code. IMHO there are mixed responsibilities about what each thing does, and we have some duplications (almost the same code) because the querying way when internal scale loop is slightly different from the HPA querying way. Although the goal and the main idea is quite similar, the code is duplicated. This idea has been in my head for some time and recent issues related with the scaler lifecycle and unclosed connections have pushed it out.
My proposal is to split the responsibilities in different layers (I'm not speaking about tons of interfaces, DTOs and clean code patterns at all, just from resposibities pov), where we manage each layer isolated from others, not sharing the internal information to avoid coupling them.
Disclaimer: Please, ignore the term "service", I used it to make a difference between our controllers (strongly related with k8s controllers) and the controllers/layers/services.
The main idea is that instead of querying metrics in different ways, we have a single layer (scaler service) where all the scalers of an scalableobject (SO/SJ) live, and other layers on top that consume this scaler layer but totally as blackbox. Let's explain the SO flow:

A ScaledObject is created
ScaledObject controller creates the HPA and calls the scaledobject service to register the ScaledObject
The ScaledObject service pass the ScaledObject to the scalableobject service (a common service for SO and SJ) and starts a loop that queries every polling interval the status of the ScaledObject (Active/Inactive).

If the scaler changes the status, it scales from/to 0

The scalableobject service parses the scaledobject received and call to the scaler service to create the required scalers.

If the scaler configurations/types/etc changes, this service call to the scaler service to update/remove the scalers
This service can be queried about the scalableobject state or just about a single metric
This service calls to fallback layer to calculate the fallback if the SO defines it and there is a fail on a scaler
This service calls to the formula calculator if required

The scaler service is the responsible for creating/refreshing/deleting the scalers when it's required, but also is the responsible for querying the specific scaler.

Scalers are treated as single items, not knowing about other scalers in the SO/SJ
This service stores (or not) the metric based on an arg, e.g: we could use an enum to defice if we have to READ,READ&STORE or READFROMCACHE
The service handles scaler recreation on demand when it's required (e,g: failures)
The service handles the scaler creation, including the arrange of envs from auth sources

This is a good improvement that makes the structure and responsibilities cleaner. I just have a few detailed questions:

Do the ScaledJob controller and ScaledObject controller each have a looping structure? Will every ScaledJob/ScaledObject start a loop?
Is it correct that the cached metric value of the scaler will only be refreshed when a ScaledJob/ScaledObject calls after the poll interval or when the metric server is queried?
The formula calculator and fallback layer are called by the scalableobject service, but each ScaledJob/ScaledObject's definition is different. Will the scalableobject service query back to the ScaledJob/ScaledObject controller to retrieve the definition, or will the ScaledJob/ScaledObject controller pass each ScaledJob/ScaledObject's formula and fallback definition to the formula calculator and fallback layer during creation?


IndexError while executing test-eval.py

I have downloaded the pre-trained weights in the checkpoints and I am executing the test-eval.py code on a cluster. I am facing the following error.

I've had the same error when trying to run on AWS. Did you manage to resolve it?

Ok, Thanks! I will look into it.


Use scoped routes for GitLab URLs

Fixes https://github.com/ben-gibson/GitLink/issues/284

Thanks for fixing this.


Extend unseen categorical check to counterfactuals

@gaugup will you explain why counterfactual should validate this? Which scenario are we in?

DiceML fails on unknown categories -> need to validate
DiceML does not fail on unknown categories, but the results are invalid for some reason -> need to validate
DiceML appropriately ignores/drops unknown categories -> no validation needed

@gaugup will you explain why counterfactual should validate this? Which scenario are we in?

DiceML fails on unknown categories -> need to validate
DiceML does not fail on unknown categories, but the results are invalid for some reason -> need to validate
DiceML appropriately ignores/drops unknown categories -> no validation needed

Yes, the recent version of dice-ml 0.7 added a check which would fail the CFE computation if the query instance carries a categorical value which is not present in training data. So the first one is True.


Add browser prefixes to CSS3 rules

Many of the state changes do not appear on iOS because you don't have the webkit prefixes. Example: Focusing on an input does not float the label on iOS event though the mui-is-focused class is added.

We actually removed vendor prefixes in v0.5.0 in favor of an autoprefixer. See the notes here:
https://github.com/callemall/material-ui/releases/tag/v0.5.0
Currently, we're using gulp-autoprefixer - https://github.com/sindresorhus/gulp-autoprefixer
Here's how we're doing it:
https://github.com/callemall/material-ui/blob/master/docs/gulp/tasks/less.js#L13
Looks like this is something we need to document.


Sensor needed when device is mowing

As an owner, knowing when the device is actively mowing in the yard could be very helpful.
The motion sensor service contains a status active characteristic that should be used for this mechanism.

This mechanism will require the event streaming api from #30


fix(weapp): prevent throwing when 6to5 transform not enabled

https://forum.leancloud.cn/t/cannot-assign-to-read-only-property-localstorage-of-object-window/12967/

Current coverage is 65.50% (diff: 100%)

Merging #434 into master will not change coverage

@@             master       #434   diff @@
==========================================
  Files            32         32
  Lines          2661       2661
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1743       1743
  Misses          918        918
  Partials          0          0

Powered by Codecov. Last update b1fa63f...7f03d18


model prediction

How to predict for a new test data?

model = anago.Sequence().load('training_result_path')
results = model.analyze(text.split(" "))


AppArmor disable umount & deny proc files.

If a container cannot mount, it cannot umount.
We should also restrict writing /proc/kcore and the
other paths libcontainer now masks.
This is a less aggressive prelude to #578.
Signed-off-by: Eric Windisch<EMAIL_ADDRESS>

I personally know nothing about AppArmor.
but looks okay
LGTM
ping @crosbymichael

Obsolete


Add namespace to pinecone hybrid search

Description:
Pinecone hybrid search is now limited to default namespace. There is no option for the user to provide a namespace to partition an index, which is one of the most important features of pinecone.
Resource:
https://docs.pinecone.io/docs/namespaces

is this finished and working ?

this should be good to go just waiting on the guys to merge


Upgrade mongodb-sync-4 to 4.3.2

Hello,
Is it possible to move to last version of mongodb sync driver to benefit last mongo features ?
Thanks

Hello @tleveque ,
these dependencies are quite up to date in the version 5 we have released recently.
This is the cofinguration is currently(however, in next releases we will update them to the latest ones)
    <spring-data-3.version>3.2.5</spring-data-3.version>
    <spring-data-2.version>2.2.13.RELEASE</spring-data-2.version>
    <mongodb-sync-4.version>4.3.2</mongodb-sync-4.version>
    <mongodb-driver-3.version>3.12.10</mongodb-driver-3.version>

Although, as said, we have released the version 5.0.8.RC, we haven't still make it public as we are still working on the documentation, our expectation is next week or week after.
If you want to upgrade to the version 5, please follow this temporal guide. We'll help you in anything you need to have it working.

Thanks
I do not see same version into pom.xml of dev and master branches.
<mongodb-sync-4.version>4.2.3</mongodb-sync-4.version>
instead of
<mongodb-sync-4.version>4.3.2</mongodb-sync-4.version>
Actually, we would like to create mongo time series with mongock and as far as I know we need 4.3.2 version of java driver.

Sorry, it was a mistake, the version currently in use is 4.2.3.
We'll release a new version next week or the week after(more likely next week) with the latest versions.
But you would need to upgrade to Mongock version 5. Here you have a document in which we briefly explain how to upgrade.
If you need anything, please let us know.
Cheers

Hello @tleveque ,
we have release the version 5.0.20.RC. With the previous version you could use the latest version of MongoDB, however there were some stuff you needed to do, specially if you were using MongockTemplate.
Now we have fixed and you can use any version of MongoDB you want with no problem.

Just a note. When testing mongodb-sync:4.3.3, for some reasons it was importing the version 4.1.1 of the bson and mongodb-core, we had to explicitly import these ones too. It seems that our systems was confused,  but in case you get an error about some method not found, it's worthy to do a mvn dependency:tree to double check 😉


reafactor(GUI): App as functional component

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Refactoring

What is the current behavior? (You can also link to an open issue here)

Sofie has a lot of very simple, legacy components implemented as Class components, even though they can easily be converted to a Functional component.

What is the new behavior (if this is a feature change)?

Implement App and a couple of top-level View components as Functions.

Other information:

Status

[x] Code documentation for the relevant parts in the code have been added/updated by the PR author
[x] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report
Patch coverage has no change and project coverage change: -9.18 :warning:

Comparison is base (7c63440) 59.32% compared to head (60694bf) 50.15%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@              Coverage Diff              @@
##           release50     #908      +/-   ##
=============================================
- Coverage      59.32%   50.15%   -9.18%
=============================================
  Files            464      363     -101
  Lines          71039    50757   -20282
  Branches        3656     2147    -1509
=============================================
- Hits           42144    25456   -16688
+ Misses         28846    25274    -3572
+ Partials          49       27      -22

see 105 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add folder to workspace

Issue Type: Bug
Hi,
I'm using a Mac, Catalina 10.15.17. Some things are not responding in visual studio code. For example, when I control+click in the workspace area and then "Add Folder to Workspace..." nothing happens, I am not prompted with finder to add this folder as I was before.
When I am on the Welcome tab and I click "Open folder..." nothing happens. Also, when I went to Code -> About Visual Studio Code nothing happened. I'm not sure how to fix this and I couldn't find anyone with the same issue on the forms.
So the result is nothing and my expected result is to be prompted with finder window to add a desired folder to me workspace.
VS Code version: Code 1.53.0 (8490d3dde47c57ba65ec40dd192d014fd2113496, 2021-02-03T16:01:04.046Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz (8 x 2400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 2, 2

Memory (System)
16.00GB (3.22GB free)

Process Argv
--crash-reporter-id 0198779c-d7c1-46f4-8232-6d64ba58eb30

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

vscode-json
and
1.5.0

latex-workshop
Jam
8.15.0

linter-gfortran
krv
2.2.2

python
ms-
2021.1.502429796

jupyter
ms-
2020.12.414227025

cpptools
ms-
1.2.0

vscode-arduino
vsc
0.3.4

Using the command pallette, try running extension bisect to see if your issue resolves

@sferrone if the native system file/folder dialog does not open, then there seems to be a serious issue that could be unrelated to VSCode. As a workaround you can configure files.simpleDialog.enable: true in settings to use our file dialog, that should work fine.


Fix crash in name resolution with custom transforms and emitDecoratorMetadata

Fixes #17551

This has also been ported to release-2.5


fix flake8 build error due to missing stacklevel argument for warn method

Seeing gated builds fail due to new errors:
./python/interpret_community/mimic/models/linear_model.py:45:[13](https://github.com/interpretml/interpret-community/actions/runs/4264305493/jobs/7422204144#step:6:14): B028 No explicit stacklevel keyword argument found. The warn method from the warnings module uses a stacklevel of 1 by default. This will only show a stack trace for the line on which the warn method is called. It is therefore recommended to use a stacklevel of 2 or greater to provide more information to the user.
./python/interpret_community/widget/explanation_dashboard.py:55:9: B028 No explicit stacklevel keyword argument found. The warn method from the warnings module uses a stacklevel of 1 by default. This will only show a stack trace for the line on which the warn method is called. It is therefore recommended to use a stacklevel of 2 or greater to provide more information to the user.
./tests/common_utils.py:160:9: B028 No explicit stacklevel keyword argument found. The warn method from the warnings module uses a stacklevel of 1 by default. This will only show a stack trace for the line on which the warn method is called. It is therefore recommended to use a stacklevel of 2 or greater to provide more information to the user.

These warnings seem to have been added to the newer releases of flake8-bugbear extension package to flake8.
This PR fixes the error by explicitly setting the stacklevel argument on the warn method call.  It seems it is recommended to set it to level 2 as it creates better warning messages by excluding the warn method itself from the printed stacktrace which can be confusing.

Codecov Report
Base: 87.83% // Head: 87.57% // Decreases project coverage by -0.27% :warning:

Coverage data is based on head (4d52fb4) compared to base (788c9e4).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #554      +/-   ##
==========================================
- Coverage   87.83%   87.57%   -0.27%
==========================================
  Files          62       62
  Lines        4094     4007      -87
==========================================
- Hits         3596     3509      -87
  Misses        498      498

Flag
Coverage Δ

unittests
87.57% <ø> (-0.27%)
:arrow_down:

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

Impacted Files
Coverage Δ

...n/interpret_community/mimic/models/linear_model.py
92.68% <ø> (-0.18%)
:arrow_down:

...nterpret_community/widget/explanation_dashboard.py
100.00% <ø> (ø)

...erpret_community/mimic/models/explainable_model.py
81.57% <0.00%> (-3.21%)
:arrow_down:

...ython/interpret_community/common/base_explainer.py
86.95% <0.00%> (-1.05%)
:arrow_down:

...mmunity/_internal/raw_explain/data_mapper_utils.py
80.85% <0.00%> (-0.79%)
:arrow_down:

...n/interpret_community/shap/gpu_kernel_explainer.py
22.55% <0.00%> (-0.58%)
:arrow_down:

...hon/interpret_community/explanation/explanation.py
90.23% <0.00%> (-0.48%)
:arrow_down:

...hon/interpret_community/mimic/models/tree_model.py
90.90% <0.00%> (-0.48%)
:arrow_down:

...interpret_community/mimic/models/lightgbm_model.py
85.63% <0.00%> (-0.33%)
:arrow_down:

python/interpret_community/common/aggregate.py
90.32% <0.00%> (-0.31%)
:arrow_down:

... and 15 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Stop! java is not a valid candidate.

I am facing an exception 'Stop! java is not a valid candidate.'  when I try to install java via sdkman with following command on cli .
sdk install java

sdk selfupdate force


The DepthStateDesc.mDepthTest is ignored on the Metal backend

You have to set the CMP to ALWAYS to get the effect you'd expect from depth test = false on Mac Metal (probably iOS as well but not tested).
To test create a DepthState with
mDepthTest = false;
mDepthFunc = CMP_NEVER;
and render something
You expect it to render as even tho func is never, the test should be off but it won't render. Change mDepthFunc to CMP_ALWAYS and its renders.

Resolved with release 1.33.


Test Coverage Metrics

We're having the rdfunit-junit integration up and running which provides us with a good overview of failing test cases, esp. in conjunction with IDE and/or CI-server. If  a test is "red" we can trust something broke.
However, the issue with "green" tests is, that we actually do not know why it is green: could be data that's valid according to the test case or maybe because there's no data to validate at all. The latter fact would decrease significance of that test (at least in the given context).
Furthermore we're missing metrics of how much input-data is actually covered by the test cases. Looking at the TestCoverageEvaluator this seems usable - though we need some elaboration. It's currently not clear what input is expected.
Request:

Can we figure out on a per-test-case basis if there is data to be tested (before/after test is run)? We could use the "test-skipped" notificaiton of JUnit to provide an overview how many tests are not testing anything.
Could the API of TestCoverageEvaluator elaborated?

TestCoverageEvaluator was created at the very first beginning of the project and not used since. I updated the code a bit to make not throw errors.
It is still not working correctly but now shows some (wrong) output when you pass -c as a CLI parameter
[INFO  TestCoverageEvaluator] Fdom Coverage: 0.0
[INFO  TestCoverageEvaluator] fRang Coverage: 0.0
[INFO  TestCoverageEvaluator] fDep Coverage: 0.0
[INFO  TestCoverageEvaluator] fCard Coverage: 0.0
[INFO  TestCoverageEvaluator] fMem Coverage: 0.0
[INFO  TestCoverageEvaluator] fCDep Coverage: 0.0

if this is updated to provide the correct numbers it could probably handle your use case.
Each metric measures a specific test coverage according to pages 3-4 in http://svn.aksw.org/papers/2014/WWW_Databugger/public.pdf
the lower the metric numbers the fewer cases are actually tested in the input source.
This class was more like a hack to generate table 4 in the paper.
What is does (or what I remember it was doing) is

relate RDFUnit patterns to each metric
calculates class & property statistics for the input source
exploit some rdfunit pattern hacks to get the classes / properties / patters associated with each test case and calculate the metrics

It needs some work to get this in a good shape & usable. Let me know if working in this directions covers your goal

Note that, ideally, the metrics should be identified by doing pattern identification inside the SPARQL queries.
This would also work on non pattern-based test cases or pattern-based test cases where the pattern is not associated with coverage metrics.
However, this approach handles most cases easily.


[SMALLFIX] Use hdfs1 API in KeyValueOutputCommitter

This is needed to fix the hdfs1 build

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8179/
Test PASSed.

@aaudiber Thanks for the fix, could we add a comment as to why we are using the older API? Also, is there any downside to using the older API?

@calvinjia Comment added. I don't think there's any downside to using the older API - we're just missing out on some syntax sugar (the approach we use is still supported in the new API)

This is duplicated in https://github.com/amplab/tachyon/pull/2547, but if this is a blocker for you, LGTM ++

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8185/
Test FAILed.

Jenkins, test this please.

@uronce-cc Fixing the build is higher priority than merging new code, so build fixes shouldn't be tacked on to other code which might cause them to get blocked, as happened with https://github.com/amplab/tachyon/pull/2547

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8190/Build result: FAILURE[...truncated 3796 lines...][JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-s3/0.9.0-SNAPSHOT/tachyon-underfs-s3-0.9.0-SNAPSHOT-javadoc.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-clients/0.9.0-SNAPSHOT/tachyon-clients-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client-unshaded/0.9.0-SNAPSHOT/tachyon-client-unshaded-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client-unshaded/0.9.0-SNAPSHOT/tachyon-client-unshaded-0.9.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client-unshaded/0.9.0-SNAPSHOT/tachyon-client-unshaded-0.9.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client-unshaded/0.9.0-SNAPSHOT/tachyon-client-unshaded-0.9.0-SNAPSHOT-javadoc.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-keyvalue/0.9.0-SNAPSHOT/tachyon-keyvalue-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-servers/0.9.0-SNAPSHOT/tachyon-servers-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-hdfs/0.9.0-SNAPSHOT/tachyon-underfs-hdfs-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-hdfs/0.9.0-SNAPSHOT/tachyon-underfs-hdfs-0.9.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-hdfs/0.9.0-SNAPSHOT/tachyon-underfs-hdfs-0.9.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-hdfs/0.9.0-SNAPSHOT/tachyon-underfs-hdfs-0.9.0-SNAPSHOT-javadoc.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-parent/0.9.0-SNAPSHOT/tachyon-parent-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-keyvalue-servers/0.9.0-SNAPSHOT/tachyon-keyvalue-servers-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client/0.9.0-SNAPSHOT/tachyon-client-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client/0.9.0-SNAPSHOT/tachyon-client-0.9.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client/0.9.0-SNAPSHOT/tachyon-client-0.9.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-client/0.9.0-SNAPSHOT/tachyon-client-0.9.0-SNAPSHOT-javadoc.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-shell/0.9.0-SNAPSHOT/tachyon-shell-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-glusterfs/0.9.0-SNAPSHOT/tachyon-underfs-glusterfs-0.9.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-glusterfs/0.9.0-SNAPSHOT/tachyon-underfs-glusterfs-0.9.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-glusterfs/0.9.0-SNAPSHOT/tachyon-underfs-glusterfs-0.9.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.tachyonproject/tachyon-underfs-glusterfs/0.9.0-SNAPSHOT/tachyon-underfs-glusterfs-0.9.0-SNAPSHOT-javadoc.jarchannel stopped
Test FAILed.

Jenkins, test this please.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8192/
Test FAILed.

Jenkins, test this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8194/
Test PASSed.

+1 LGTM


placeholder missing from TextOptions interface

I'm not sure if you intend to release current master but just FYI that TextOptions is missing the placeholder option. I note that placeholder is actually not documented in the addText page, though it is shown in the placeholders example on the Master Slide page. It looks like they have made it into 3.0 as you have placeholder back in the interface.
I would just emphasise the importance of being able to associate objects with a master placeholder. Doing that allows users to apply a design template to the created presentation and get the relevant design elements applied to the placeholders. Given that you are never going to go down the road of using a template as a basis for creating the presentation, having placeholders is the next best thing.

Fixed in v3.0


Windowsizelock

Its Functional, but the settings arent saved at this State
Menu items created,
Function linked
WindowManager extended

I can implement
The spin boxes should automatically populate with the actual window size when the lock is enabled
but saving and loading is a problem right now.

Should not add it to version 0.9 and 0.10 wont work, and also 0.11 will be a proplem in loaddata
if version >= 0.11:  means =>  0.2  > 0.11
I think the "Version" should change to string before adding these value in _load_data.
_save_data looks fine to already add it to.

Oof I forgot about the version number issue. We don't want to increment to 1.0 until we hit a milestone. Code and I were talking about changing version number to a string and we have it on the roadmap. Looks like we're at a tipping point where it needs to be our highest priority now. I think this issue might be blocked by that. I'll spend some time working on it today.

okay,
if possible i would want to avoid making a rebase,  (bad memories from a lot of failed merges)
You could make another issue /pull request after you are done.
Or inlcude these 3 variables while you are already chancing the save/load functions.

I don't mind rebasing and resolving the merge conflicts! Whatever happens, I'll make sure your commits stay intact so you get credit for your contributions

I did the version string thing in #102 . Need Code's review though. There is a chance we won't get it merged until Sunday, but I'll poke him and see if he has time.

Code and I just looked at your latest changes in a call and here's our notes:

Rename the check box to "Fixed window size"
Make sure the Quit button is always the last button in the list
Changing the numbers doesn't resize the window
Every time the lock is toggled, the window shrinks by 10 pixels
Code confirmed my suspicions that this is a really good feature and we're both really excited about it

Every time the lock is toggled, the window shrinks by 10 pixels

I stoped the shrinking, but i can't fix the margin changes on the title.
https://github.com/godotengine/godot/issues/81640


undeploy behavior should be similar to deploy

undeploy uses --actions and --static flags while deploy uses --skip-actions and --skip-static
deploy is able to auto-detect if project has ui and/or actions while undeploy throws an error if there is not web-src/ or actions folder

problem also with delete action output
[...]
> deleting action 'campaign-standard', please make sure to cleanup associated dependencies and configurations yourself
✔ An action was deleted locally, run **`aio app deploy -a`** to sync your current actions deployment


Adds error handling for the async client

Description
Continuation of https://github.com/dapr/python-sdk/pull/659 for the async client.
Issue reference
https://github.com/dapr/python-sdk/issues/648
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[X] Created/updated tests

@berndverst  the python 3.11 run passes now, after having merged main. We should be good to go.

@elena-kolevska that makes no sense, but I'll take it :D


BUG: static_analyzer crash

There is no check for a null pointer here, so the program will crash afterwards.
https://github.com/vul337/PrIntFuzz/blob/b7a33fa326b154dfee7e0147502c43926ca6c61a/static_analyzer/src/analyzer/property.cpp#L1072
Root Cause:
In some versions(at least llvm-14.*), LLVM will optimize some code, e.g. https://elixir.bootlin.com/linux/v5.18-rc1/source/include/linux/device.h#L249
static inline int devm_add_action_or_reset(struct device *dev,
					   void (*action)(void *), void *data)
{
	int ret;

	ret = devm_add_action(dev, action, data);
	if (ret)
		action(data);

	return ret;
}

define internal fastcc i32 @devm_add_action_or_reset(%struct.device* noundef %0, i8* noundef %1) unnamed_addr #7 align 64 {
  %3 = tail call i32 @devm_add_action(%struct.device* noundef %0, void (i8*)* noundef nonnull @anx7625_runtime_disable, i8* noundef %1) #11
  %4 = icmp eq i32 %3, 0
  br i1 %4, label %7, label %5

5:                                                ; preds = %2
  %6 = bitcast i8* %1 to %struct.device*
  tail call void @__pm_runtime_use_autosuspend(%struct.device* noundef %6, i1 noundef zeroext false) #11
  tail call void @__pm_runtime_disable(%struct.device* noundef %6, i1 noundef zeroext true) #11
  br label %7

7:                                                ; preds = %5, %2
  ret i32 %3
}

at call site:
  %299 = call fastcc i32 @devm_add_action_or_reset(%struct.device* noundef %6, i8* noundef %298) #14

so, we can't find the func ptr through 1st args at call site.

Thanks for reporting the bug. This is actually a test function and has no effect on the functionality of PrIntFuzz, I forgot to remove them before the release and some of the code may not have been updated, now I remove them.


Delete Old Branches

We have a lot of old branches. Not sure which ones can be deleted, but would love to clean it out. Any branches that we should leave alone (besides any that are in a PR)?

Good idea - probably worth doing across all repos.

@cc7768 Can this be closed?
Spencer has cleaned up the branches.

I'm happy for this to be closed whenever the group feels it is clean. It looks good to me.


Object deletion API.

This PR is for implementing the object deletion API as per #AB40 for all NovelObjects.

I need more eyes on this. I am unhappy with the current implementation but cannot see a way to make it nicer at the present.

More a comment on an over-arching design here; but, basically you have two sides of resources to manage (CPU side and GPU side). For the purposes of below, I'm going to refer to create/delete as the CPU side and bind/unbind as the GPU side.
Essentially, users will create objects on the CPU side. Some of these are not-expensive (i.e. rectangles), others can be potentially expensive (i.e. images), and some will eventually be a mix (i.e. text, where the font will be shared/cached and is "expensive", but the glyphs and string to render are "cheap").
For this, you'll probably want to allow users to create an object but not load the assert (into CPU memory). You probably want loading of the asset to be lazy (it doesn't happen until its actually needed the first time).
Then, the next step is actually using it on the GPU, which involves "binding" (copying the resource to the GPU, creating the appropriate resource ids, etc). This again should be "lazy" (you don't want to be binding 100s of objects in a scene graph if, on average, only a handful will be used per frame).
Creation is then pretty straightforward. But, for deletion and unbinding, there is both a bit of "needs to automatically happen" and a bit of "the user should be able to control this". For example, you probably don't want to hardcode it so that a resource is unbound as soon as someProperty == false, as the user might be displaying it again in a few frames (in which case unbinding is more expensive).
To that effect, you ultimately have a few states:

isActive -- is the object bound to the GPU
isEnabled -- can the object receive input
isVisible -- is the object actually being rendered

These states work in conjunction with each other to determine everything with isActive and isVisible largely playing off one another. For example, isVisible can't be true unless isActive is also true. As long as isActive is true, the resource is a GPU resource and can be rendered etc (and for some things, like a primitive rectangle, isActive might always be true).

I'm closing this due to its age and having another go at it this week.


Enable Custom Date Formats for AreaSparklineChart

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[X] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

Current behavior

Current issue is about AreaSparklineChart component, but probably there are more similar components that have the same issue.
When setting a data for AreaSparklineChart, the key doesn't accept custom time formats
Example:
<AreaSparklineChart
  series={<AreaSeries colorScheme={[colors.pink[100]]} />}
  data={[
    {
      data: 1,
      key: new Date()
    }
  ]}
 />

In the example below the key is set as new Date(), but we can also set the key as any integer key={111} and it will work
Expected behavior
Expecting to be able to set any value for the key property, for example '2024-08-15 13:41:42 GMT-4'
Minimal reproduction of the problem with instructions
Render this component :
<AreaSparklineChart
  series={<AreaSeries colorScheme={[colors.pink[100]]} />}
  data={[
    {
      data: 1,
      key: '2024-08-15 13:41:42 GMT-4'
    }
  ]}
/>

Libs:
- react version: 18.2.0
- reaviz version: 15.18.4

Browser:
- [X] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: 20.15.0
- Platform:  Windows 10
-

cc: @cloughrm


Client should not require Block hash to be H256 for everything useful

This pollutes everything.
When we need to use hashes as keys on disk, I think it would be fine to truncate hashes to 256 bits silently and internally (as that is more than enough entropy), but not to require it as a type parameter everywhere.

@andresilva pointed out that somewhere we need a bound proving that Backend::Hasher::Out == Block::Hash.
We should aim to make this more flexible with some kind of conversion parameter or drop the requirement entirely.

I'm confused.. Isn't H256 exactly what avoid the type parameter everywhere?

@burdges This line https://github.com/paritytech/substrate/blob/203e2c23b51bf23f778b3afee16465e6dca04cf2/core/client/src/client.rs#L301 is the one that should be dropped.

Well, I suppose in some sense it's avoiding a concrete specification of the hash algorithm, but Substrate in some places says "we're generic over the hash output length" and in most (important places) it says "the hash length must be 256 bits".

I see..  We need 256 bit hashes for 128 bits of security anyplace where birthday attacks pose a threat, like in Merkle trees.  We can safely neglect that we technically loose some security bits from the Merkle tree itself, so we do not afaik require more than 256 bits anyplace.
If we identify places that only require fewer bits of security, like MACs, then we could make them use some MacTag128 or H192 types, but yeah I agree being generic over hash size everywhere is either harmful or useless.

Well, it should either be fully-generic or fully-non-generic, not some weird halfway-house.

I'm saying non-generic is fine.  If we find a place where a smaller size it appropriate, then we can make that non-generic at the smaller size.

Right - and just to clarify, any cryptographic non-safety caused by too-small hashes is not something that would arise as part of the implementation of this issue. That would happen in the chain configuration, where somebody might choose a hash size which is too small.

IMO, a better option would be to have a type SubstrateHash = H256 and then use SubstrateHash everywhere.  That way, we can still change the type if we need to.


pychx v4.0.7

Has the fix from https://github.com/NSLS-II/pyCHX/pull/30.
Based on the tag: https://github.com/NSLS-II/pyCHX/releases/tag/v4.0.7.

Tested locally in a Docker container with the passed GH_TOKEN, works fine. Going to build it internally and put it to our internal channel.
attn @leofang, please have a look how the version can be parametrized.


Bug lc 190 update wcag

Replaced by https://github.com/Civil-Service-Human-Resources/lpg-management/pull/227/files


Http to https redirect

Hello,
Having a positive result in Lighthouse (devtools) PWA testing is currently not possible anymore: Lighthouse requests a http > https redirection to give a positive audit. A nice to have feature would be a simple option added when we start the server (like "--redirect-https" for example).

Possible duplicate of:

#273
#598
#600

Yeah I'm going to call this a duplicate of #273

Thank you for the info. Maybe it's a good idea to add the info in the documentation ?


Internet NEG backends must not have a health check

Pulumi attempts to enforce the healthChecks field on the compute.BackendService resource but this field must not be passed to the GCP API in certain circumstances.
// The following infrastructure is used so that we can use Cloud CDN with Cloud Functions.
const cloudFunctionsNEG = new gcp.compute.GlobalNetworkEndpointGroup(
  'cloud-functions',
  {
    networkEndpointType: 'INTERNET_FQDN_PORT',
  },
  { provider: gcpProvider },
)
const cloudFunctionsNE = new gcp.compute.GlobalNetworkEndpoint(
  'cloud-functions',
  {
    globalNetworkEndpointGroup: cloudFunctionsNEG.name,
    fqdn: `us-central1-${project}.cloudfunctions.net`,
    port: 443, // HTTPS
  },
  { provider: gcpProvider },
)
const cloudFunctionsBS = new gcp.compute.BackendService(
  'cloud-functions',
  // @ts-expect-error: `healthChecks` is required by Pulumi but backend services with
  // internet NEG backends must not have a health check according to GCP docs.
  //
  // See https://cloud.google.com/compute/docs/reference/rest/v1/backendServices
  {
    backends: [{ group: cloudFunctionsNEG.id }],
    enableCdn: true,
    protocol: 'HTTPS',
  },
  { provider: gcpProvider },
)

Unfortunately the @ts-expect-error directive doesn't help here since the SDK checks the field at runtime.

Looks like this is tracked upstream in https://github.com/terraform-google-modules/terraform-google-lb-http/issues/105 and once that's fixed should get picked up with the next pulumi-gcp update.

This has been resolved upstream.

@lmakarov Thanks for the friendly notification on this!

@leezen I've just updated to the latest version of pulumi (2.11.0), but I'm still getting this error:
  gcp:compute:BackendService (web-service):
    error: Error creating BackendService: googleapi: Error 400: Invalid value for field 'resource.healthChecks': ''. At least one health check needs to be specified., invalid

let webService = new gcp.compute.BackendService("web-service", {
  protocol: "HTTPS",
  backends: [
      {
          group: webNEG.selfLink,
      },
  ],
});

I assume, a new release of pulumi/pulumi-gcp is necessary to address this issue?

@lmakarov This is dependent on the version of @pulumi/gcp

It looks like I referenced the wrong issue actually earlier and should have referenced https://github.com/hashicorp/terraform-provider-google/issues/6155 which is fixed in 3.32 of the TF provider, which corresponds to the 3.16.0 update (and subsequent) of the @pulumi/gcp package.

which is fixed in 3.32 of the TF provider, which corresponds to the 3.16.0 update (and subsequent) of the @pulumi/gcp package.

@leezen The example error I posted earlier was with@pulumi/gcp v3.25.0. Any debug output I can provide to help diagnose the issue?

Never mind. Figured out the issue.
I was mistakenly using gcp.compute.NetworkEndpointGroup instead of gcp.compute.GlobalNetworkEndpointGroup.
The following works as expeceted:
const webNEG = new gcp.compute.GlobalNetworkEndpointGroup("web-neg", {
  networkEndpointType: "INTERNET_FQDN_PORT",
});

const webService = new gcp.compute.BackendService("web-service", {
  protocol: "HTTPS",
  backends: [
      {
        group: webNEG.selfLink,
      },
  ],
});


Cloud 747

Organized CB exception classes (deleted unused ones)
Only exception messages logged by the flow's error handler (to avoid misinterpretation of logs)

@biharitomi @doktoric pls check this out

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1294/


Profiler

Hello,
I have follow all the cours but the  web profiler don't work.
log message:
[2015-08-18 19:32:21] MicroCMS.CRITICAL: Twig_Error_Syntax: The function "render" does not exist in<EMAIL_ADDRESS>at line 5 (uncaught exception) at S:\wamp\www\silex\vendor\twig\twig\lib\Twig\ExpressionParser.php line 578 {"exception":"[object] (Twig_Error_Syntax(code: 0): The function "render" does not exist in<EMAIL_ADDRESS>at line 5 at S:\wamp\www\silex\vendor\twig\twig\lib\Twig\ExpressionParser.php:578)"} []
Thank you for your help.
PS: The cours is very interesting

Hi,
Thanks a lot for your message.
I am aware of this problem and will try to update the course in the following days/weeks. In the meantime, see this Silex issue for a workaround which should solve the problem.

Ok, it work ! Thank you


WebpackError: Cannot read property 'android' of undefined

Just tried to build the via Netlify without any options and this was the outcome of that.
v2.1.1

I had the same problem, turns out there was no default options in v2.2.1. I used the README.md from here https://github.com/Creatiwity/gatsby-plugin-favicon/tree/v2.1.1 and had to add options to my plugin in gatsby-config.js.
{
  resolve: 'gatsby-plugin-favicon',
  options: {
    logo: './src/favicon.png',
    injectHTML: true,
    icons: {
      android: true,
      appleIcon: true,
      appleStartup: true,
      coast: false,
      favicons: true,
      firefox: true,
      twitter: false,
      yandex: false,
      windows: false
    }
  }
}

Thanks for this!

Indeed there wasn't a working default configuration in 2.1.1. Please see https://github.com/Creatiwity/gatsby-plugin-favicon/tree/v2.1.1


missing pre-recorded rosbag

Hello here, I am now testing the performance of your algorithm, unfortunately, the two bags you provided is not available for now.

Due to some legal restrictions, we are currently adjusting our data opening strategy, please wait a few days.


SQLite Query: Cast from decimal to double not translated

When using Sqlite as a database for EFCore, the following expression doesn't work:
Where(x => x.Price > -1)

This expression will return items where Price is -5. One workaround is to use Decimal.Negate and reverse the expression, but that shouldn't be needed. Both methods work fine with using SQL as the database.
Steps to reproduce
Given Db Model Item:
class Item
{
    public long Id { get; set; }

    public string Name { get; set; }

    public decimal Price { get; set; }
}

and db context
class TestDbContext : DbContext
{
    public TestDbContext(DbContextOptions options) : base(options) { }

    public DbSet<Item> Items { get; set; }
}

and the following repo:
static async Task Main()
{
    var connection = new SqliteConnection("DataSource=:memory:");

    connection.Open();

    var options = new DbContextOptionsBuilder<TestDbContext>()
                        .UseSqlite(connection)
                        .Options;

    var context = new TestDbContext(options);

    context.Database.EnsureCreated();

    var items = new List<Item>
    {
        new Item{Id = 1, Name = "Item 1", Price = 100},
        new Item{Id = 2, Name = "Item 2", Price = 10},
        new Item{Id = 3, Name = "Item 3", Price = 0},
        new Item{Id = 4, Name = "Item 4", Price = -1},
        new Item{Id = 5, Name = "Item 5", Price = -5}
    };

    context.Items.AddRange(items);
    context.SaveChanges();

    var query1 = context.Items.Where(x => x.Price > 0).Select(x => x.Name);
    var results1 = await query1.ToArrayAsync();
    Console.WriteLine($"Items with price greater than 0 - {string.Join(',', results1)}");

    var query2 = context.Items.Where(x => x.Price > -1m).Select(x => x.Name);
    var results2 = await query2.ToArrayAsync();
    Console.WriteLine($"Items with price greater than -1 - {string.Join(',', results2)}");

    var query3 = context.Items.Where(x => decimal.Negate(x.Price) < 1).Select(x => x.Name);
    var results3 = await query3.ToArrayAsync();
    Console.WriteLine($"Items with price greater than -1 - {string.Join(',', results3)}");

    Console.ReadLine();
}

The result of query2 produces Item 1, 2, 3 and 5, where only Item 1, 2, 3 are expected.
Console.WriteLine("Hello World!");

Further technical details
EF Core version: 2.0.01
Database Provider: Microsoft.EntityFrameworkCore.Sqlite 2.0.1)
Operating system: Windows 10
IDE: Visual Studio 2017 15.5.2

#8861 added ability to introduce casting for projection but not for other places.

I think I already updated this to client-eval in 2.2 when there’s no cast.

Generated SQL in new pipeline
SELECT "p"."ProductID", "p"."Discontinued", "p"."ProductName", "p"."SupplierID", "p"."UnitPrice", "p"."UnitsInStock"
FROM "Products" AS "p"
WHERE CAST("p"."UnitPrice" AS REAL) > -1.0

My hero! lol, I'm so happy with all the improvements around types in 3.0


Is it possible to add number on top right corner of each day?

I would like to show how many users logged in on each day of a week. Is it possible to customise the day html or append a span to each day?

Hi @prabhakaran-r2
Sorry, I am late but your case is not possible with this component.
But you can create an own version of this component and do it possible. You can start from here: https://github.com/kekeh/angular-mydatepicker#development-of-this-component


Speed up model generation for decision trees

Most of the time is spent in generating indicator constraints.
We should try to make that faster and avoid it when possible (bounds already determine branching direction or even generate directly big-Ms).

Looking at profiler output this should be OK now.
The most time seems now spent on submodel book-keeping. We could skip it for gradient boosted regressor and random forest if we want to make those faster.


Patch and test some edge cases for deserializing OneDrive metadata

Description
Currently no folder path entry is stored for the root folder. This leads to not having a folders map but having a valid delta token if all items are in the root of the drive.
Update the code to add at least an empty folders map entry so we don't think we have missing metadata. Add tests to check for these edge cases.
Long-term we may want to add a folder entry for the root folder. Whether we do or not may depend on how we decide to set the state field for that collection.
Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[x] :no_entry: No

Type of change

[ ] :sunflower: Feature
[x] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Test
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

#2122

Test Plan

[ ] :muscle: Manual
[x] :zap: Unit test
[ ] :green_heart: E2E

@meain tagging you here as there's some stuff about folder path metadata you may need to change when setting state fields
(from PR description)

Long-term we may want to add a folder entry for the root folder. Whether we do or not may depend on how we decide to set the state field for that collection.


withoutActuallyEscaping with isolated argument causes region based isolation checker error

Description
If we use withoutActuallyEscaping within a function that has an isolated parameter, the compiler will stop with an error.
error: pattern that the region based isolation checker does not understand how to check. Please file a bug
Reproduction
using: // swift-tools-version: 6.0
func f(
    isolation: isolated (any Actor)? = #isolation,
    operation: () async throws -> ()
) async throws {
    try await withoutActuallyEscaping(operation) { operation in
        try await operation()
    }
}

Expected behavior
Compiler did not stop
Environment
❯ swift --version
swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx14.0
Additional information
No response

I've read something similar here: https://github.com/swiftlang/swift/issues/76205


Try getting corresponding symbols for ANCM builds

We don't export corresponding symbols for msis with ANCM. This is a simple approach for now.

Eventually what you'd like is a release pipeline that can run off a specific signed build. We use that for some of our webtools builds today and it takes care of publishing our installers to VSDrop, archiving symbols and creating an insertion PR.

@aspnet/build my build is failing for installing VS reasons I think.

Nvrm, I see that https://github.com/aspnet/AspNetCore/pull/9266 will correct it.

@aspnet/build this is a high priority issue for inserting ANCM into visual studio. Feedback is appreciated so I can get this merged soon.

Should mention #9263 brings in the change you duplicated in InstallVisualStudio.ps1 That looks like it'll be in master in less than an hour. 2nd attempt already further along.

Sorry was impatient and wanted to verify my change. I'll revert appropriately.

@jkotalik https://dnceng.visualstudio.com/internal/_build/results?buildId=151176 went well and I've retried https://dev.azure.com/dnceng/public/_build/results?buildId=151165.
Plase confirm the ANCM artifacts from https://dnceng.visualstudio.com/internal/_build/results?buildId=151176 look correct.

Verified that the symbols are correct and are matching. 😄

Let me know if you want me to archive a new build for the insertion


[CT-909] Adapter Management works with Click

User Story:
As a user of dbt, adapters continue to work as they do currently
Acceptance Criteria:

The logic found in the adapter_management context manager is moved to the root click group and propagates down to all subcommands

I love the idea, but it ended up being only one line of code to move this to the Click world so the global state persists for now.

@iknox-fa great solution to the scope of this initial ticket!


Failure in tests marked COF is not failing the test case

Expected behavior
A test should fail, if there is a failure.
Actual behavior
If it is marked as COF, throwing an exception in step also does not fail the test case.
Steps to replicate

create a basic project
Give step implementation of Vowels in English language are <vowelString>. as

    @ContinueOnFailure
    @Step("Vowels in English language are <vowelString>.")
    public void setLanguageVowels(String vowelString) throws Exception {
        vowels = new HashSet<>();
        for (char ch : vowelString.toCharArray()) {
            vowels.add(ch);
        }
        new Exception("sfd");
    }

Running the spec is not failing the suite.

Version
Gauge version: 0.9.2.nightly-2017-08-30
Commit Hash: b0fda9f

Plugins
-------
csharp (0.10.1)
java (0.6.5.nightly-2017-08-14)
ruby (0.4.1)
spectacle (0.1.2)
xml-report (0.2.0)

Expected behavour with gauge-java. See here


undefined is not an object (evaluating 'window.safari.pushNotification')

I've got the Web SDK working, with Laravel 9 / Vue3 / Inertiajs. After that I've spend the day implementing the Beams beta with safari/iOS support.
It works when I test it locally (and on staging) in Safari Tech Preview, User Agent set to Safari - iOS 16.0. I can trigger the notification permissions popup and subscribe. Even send notifications to my User ID.
I get errors when I test it on staging on my iPhone, remote debugging on my macbook with Safari Tech Preview (User Agent set to Safari - iOS 16.0 or even default).
Basically 2 errors:

On page load: Unhandled Promise Rejection: Error: Cannot read value: DeviceStateStore not connected to IndexedDB
On click to trigger the permissions popup: TypeError: undefined is not an object (evaluating 'window.safari.pushNotification')

Then nothing happens. I've cleared the website data, tried reloading the PWA, rebuild the js.
Anyone got any ideas?

Hi man
Were you able to solve this issue?
I am currently facing the same problem. It works fine when testing locally but it gives the "TypeError: undefined is not an object (evaluating 'window.safari.pushNotification')" when trying on the staging environment .

Unfortunately the issue can't be solved at this moment, as there is not support for iOS at all.. only for Safari on desktop, that's why it works when testing locally but failing when testing on your phone.
I've asked the Pusher support team to make this more clear in the documentation. They said Apple will probably start supporting push notifications for PWA's on iOS somewhere in 2023, but for now there's no option for this.
My solution for now was to add email notifications for iOS users.

@SanderGo is correct, iOS does not support web push notifications at this time. This is an iOS/Safari limitation and not a Beams limitation - if you need to push notifications to iOS devices then we do have a Swift library available, although you would need to build an app and publish to the App Store for this.


Python:Loops-while loop #557

This is a tutorial video on while loop, explaining what it is? how to use it? and what attributes it provides.
contributed by-
Subhoshree pattnaik
python batch 1

Description 📜
This is a tutorial video on while loop, explaining what it is? how to use it? and what attributes it provides.
contributed by-
Subhoshree pattnaik
python batch 1
Fixes # <557>

Type of change 📝

[x] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Python_#Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@adityabisoi  @ankurg132 can you please review my PR
subhoshree pattnaik
python batch 1

Can you use # with the number 557 so that the issue can be directly linked as #3425

Can you add the correct issue linked with this PR using # and the issue number.

The issue number is # 557


DO NOT MERGE! Fast Forward stable to 828374e480058c6b3544ad0dfbcdd020154a0766.

This PR will be merged automatically once checks are successful.

Jenkins job manager/postsubmit passed

Jenkins job manager/e2e-suite passed


Missing IPv6-Addresses

Hi there. Great Module. It makes things really easier.
Any Chance to include the MS IPv6-Addresses too?

Yes this would be very helpfull


Gradio auth

Hello,
On other gradio application, we can set an auth using the parameter --gradio-auth :
Is this possible with musicgen gradio interface ?
thanks

Forget, I realize that we can use --username and --password for that


why use gpt4 to evaluate the output?

Based on the paper, the output of LVM is {yes, no, unknown}.

Thanks for your interests. in our paper! Our benchmark is a diagnostic suite to analyze the hallucination of LVLM. If the answer is only yes or no without furthermore explanations, it will be hard to classify whether it's language hallucination or visual illusion. Sometimes even though GPT-4v generates yes at the beginning of the sentence, the semantic meaning of the left part of the sentences is negative. Therefore, only using keyword matching algorithms will not work. GPT4 can solve this challenge.


crnn can recognize line of charactors by my understading

crnn can recognize line of charactors by my understading, but images of yours appears to be 2 lines.
is my understand right?

I know that only one line of CRNN input is used for general text recognition.
However, because I applied CRNN only to license plate recognition, I think that it is possible to do 2 lines.

Originally, images with two lines of text do not work well, but I can tell you two things.
Since crnn is a structure that creates a height of 1 and a feature vector of width and channel, increasing the width expects to be able to distinguish the letters by the space between the upper and lower texts of the license plate. (It 's just my idea. )
And the other one is to increase the number of fake images a lot.
But it is unlikely to be a fundamental solution. It may be necessary to separate the top and bottom of the license plate by preprocessing

@qjadud1994 Thanks for the reply.


Apply user filters to scanset

Closes #40

Hello @matteobachetti! Thanks for submitting the PR.

In the file srttools/core/imager.py, following are the PEP8 issues :

Line 41:80: E501 line too long (82 > 79 characters)
Line 42:80: E501 line too long (82 > 79 characters)


Not getting any response after uploading picture in search field of product.

Bug report
Title
Not getting any response after uploading picture in search field of product.
Issue Description
Not getting any response after uploading picture in search field of product.
Preconditions
1. framework Version.-master

Steps to reproduce
1. step1-Go to Search Product here and upload a product to search.

Expected result
After uploading picture it should show any response
Actual result
Not getting any response after uploading picture

@jyoti-webkul
As I have checked it's working fine.


Add an archives page

Planning to add an archives page with a search feature so that blogs can be searched out.

Archives page added along with new theme


class_generator - add object as field type

Summary by CodeRabbit

New Features

Enhanced type safety and clarity in multiple classes through updated type annotations for parameters, ensuring expected input is now explicitly defined as dictionaries.

Bug Fixes

Adjustments made to the SecurityContextConstraints class to improve flexibility and clarity by broadening type definitions and simplifying logic.

Refactor

Removed nested Type class from the Service class to streamline service type handling.

Documentation

Updated docstrings across various classes to reflect new parameter types and improve clarity for end-users.

Report bugs in Issues
The following are automatically added:

Add reviewers from OWNER file (in the root of the repository) under reviewers section.
Set PR size label.
New issue is created for the PR. (Closed when PR is merged/closed)
Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
verified label removed on each new commit push.
To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.

Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
Cherry-pick will be started when PR is merged

To build and push container image command /build-and-push-container in the PR (tag will be the PR number).

You can add extra args to the Podman build command

Example: /build-and-push-container --build-arg OPENSHIFT_PYTHON_WRAPPER_COMMIT=<commit_hash>

To add a label by comment use /<label name>, to remove, use /<label name> cancel
To assign reviewers based on OWNERS file use /assign-reviewers
To check if PR can be merged use /check-can-merge

Supported /retest check runs

/retest tox: Retest tox
/retest python-module-install: Retest python-module-install

Supported labels

hold
verified
wip
lgtm

/verified


Changed single nearest study group to multiple ones, sorted by distance

@dexrualo I like it. Nice work. Just running some tests. For me, the mindif of 20 is to small to register a single group even in my region. I'll probably make it 100 and I'm thinking about adding a select menu giving users a choice of radius.

@ginoskotheon Thank you! Yes, letting users choose a radius would be nice. And congrats with this project of yours. I think its a good idea.


Update README.md for conda based installation

Dear team,
Thanks at first for creating this beautiful package! I must admit I do not understand half as much as I would like of the overall structure -- so I just followed the Readme. ;)
Being based on debian with miniconda, I needed to adjust the command to install the "right" python version, to accomodate the exact requirements. The requirements I had to install with pip.
I will file further issues / pull requests for the remaining errors that occured during the installation. See you then. :)

Thanks for pointing this out! It's been a very long time since any us have tried a Conda installation. I'm working on a more thorough update to the top-level README, and this is a great start.


[otbn] Use a simpler example for the DIF smoke test

The OTBN DIF smoke test currently runs a barrett384 application on OTBN. Even though it's not that much code, it takes 10 minutes to run in Verilator simulation. And since we run the smoke test in CI once with the model (ISS) and once with the RTL, we add 20 min to CI. We should look for a significantly smaller smoke test which only takes a couple of cycles to actually test the DIF - OTBN integration, and keep the other test to run less frequently (or only on FPGA; to be determined).
Keeping tests other than the smoke test currently depends on the merging of the OTBN driver framework (#4136) unfortunately, which is blocked on SW review.
[Note: we could parallelize the test runs in CI, but that's not very pretty since we have to manually split the test suite in reasonably equal-sized chunks, or use lowRISC-provided-and-paid-for builders.]

estimate 4

It turns out most of the time spent in the smoke test in Verilator is due to logging being extremely time-consuming on that platform (it's a simulated UART, which just takes a lot of cycles to get characters sent out). In numbers, the smoke test runs on my machine in 1:36 min with logging, or in 33s without logging (end-to-end, including simulator startup), or roughly 3x as fast.
We'll likely need a system-wide solution for better simulation logging in Verilator, but until that arrives, I'll just cut down on the LOG_* statements used in the test.

It turns out most of the time spent in the smoke test in Verilator is due to logging being extremely time-consuming on that platform (it's a simulated UART, which just takes a lot of cycles to get characters sent out). In numbers, the smoke test runs on my machine in 1:36 min with logging, or in 33s without logging (end-to-end, including simulator startup), or roughly 3x as fast.
We'll likely need a system-wide solution for better simulation logging in Verilator, but until that arrives, I'll just cut down on the LOG_* statements used in the test.


fix: include skipped partial withdrawal to partialWithdrawalsCount

ethereum/consensus-specs#3943 fixes calculation of partial_withdrawals_count such that partial withdrawals can be dequeued correctly.

:tada: This PR is included in v1.23.0 :tada:


Missing SOFT LEAD Company in Scraper UI

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10 Pro
STEPS TO REPRODUCE:
Open the URL https://scrapers.peviitor.ro/
Write "Soft Lead" in the search bar
EXPECTED RESULTS:
The company "Soft Lead" should be found and displayed in the search results when entered in the search bar.
ACTUAL RESULTS:
The company "Soft Lead" is not found or displayed in the search results.

Fixed, can you retest in validator?

Still not found


Damarcus Jones Ai Chips

directory: "/" # Location of package manifests

Thank you for opening this issue, we will look into it.

directory: "/" # Location of package manifests


vscode marketplace shows wrong installation instructions

For example for my debugging extension the vscode marketplace says I should do ext install debug but when entering that into the console it wants to install some python extension as it has debug in its description and is the most downloaded extension. Showing publisher.extension in the marketplace would make this more unique

You run this command from the command palette not on the command line, see the first sentence.

@waderyan we should try to avoid this confusion.  I suggest to show this is a two steps

open command palette
run this command

yeah I meant command palette instead of console but I actually did it in the command palette

The issue is that if I run the command in the command pallete (ctrl-p) as it says on the vscode marketplace, it will search for the extension now but it will select the wrong extension. Currently when I run the command it gives me (ext install debug), it will show PHP Debug as first result. However this is not the extension I got the command for (actual extension I would want to install)
This isn't really a big issue now that it doesn't install the extension anymore but instead searches for it in the extensions dialog. However users who are new to vscode and want to install an extension they found on the internet could get confused why it isn't showing up in the results (you might need to scroll because the extension doesn't have 100k downloads but a very generic name)

This has been addressed by the support to install from the marketplace directly.


Error when tagging

I keep getting this when I'm trying to tag any .cbz file. Fix?

I'm seeing the same error on the macOS version.

I can't reproduce the issue, but it looks like whatever comics you're trying to tag don't have covers on comicvine yet

I can't reproduce the issue, but it looks like whatever comics you're trying to tag don't have covers on comicvine yet

The stuff I was tagging had covers in Comicvine. Anyways, the error fixed itself for some reason.

Same for me. Might have been comicvine connectivity issues (timeouts).
Dale Lovingood - Chat @ Spike	[2bdzdw]
On October 31, 2023 at 3:40 GMT, IDontKnow218 @.***> wrote:
I can't reproduce the issue, but it looks like whatever comics you're trying to tag don't have covers on comicvine yet
The stuff I was tagging had covers in Comicvine. Anyways, the error fixed itself for some reason.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I'm also having the same issue

I can't do anything without a log or a comic that can consistently re-produce the issue

I can't do anything without a log or a comic that can consistently re-produce the issue

It started working fine again, so I don't know what was happening

I also have had the same issue come up, on and off over the past week or so. It does not consistently happen for the same issue each time

@laxtrey5 your issue is completely separate, and is probably fixed in the latest alpha, but I'll have to check

If this happens again open a new issue


Bug: pushing to registry requires kubeconfig

Using the push goal prints an error about missing kubeconfig. Building and publishing a helm chart to a repo, should not require a Kubernetes cluster.
This is a fault of helm rather than this maven plugin, but it can provide a way to work around it.
One way to supress this is by using an empty config file and providing it to helm via --kubeconfig flag.
This flag is currently not exposed into the plugin config. Is it possible to add that in please?

Which helm-version do you use? I cannot reproduce the warning. Can you provide a helm command to enforce this warning?

Which helm-version do you use? I cannot reproduce the warning. Can you provide a helm command to enforce this warning?

And now I can't reproduce it either.


Translate to sql at compile time

EF Core vs Dapper
I often use EF Core and dapper together in projects depending on how certain queries perform and how fast I need them to be.  EF Core is slightly slower due to translating sql at runtime, while dapper does not have to perform this operation.  It would be nice to not have to compromise typed queries and speed.

Generate Sql at compile time
I think it would be awesome if we could generate our ef core queries into sql queries at compile time.  This would increase the performance of EF Core without sacrificing usability.
I have been working on a prototype using Microsoft.CodeAnalysis to inject code into assemblies.  The compiled queries could be controlled by having something like [CompileQuery] on top of the class, method, or for an entire assembly.  I have done some benchmarks and doing something like this performs better than Compiled queries.
I was wondering if this is something that would be practical and if there are some tools in the EF Core codebase that might help with building something like this.  For example, I know that there is tools to generate DbContexts and the needed classes.

EF Core only generates SQL queries the first time that a LINQ query is executed, and caches that. The second time that the same query is executed (even with different parameter values), the cached SQL is reused without having to regenerate the SQL. There are some important missing details in this description but overall it's correct for the purpose of this discussion. Generating SQL queries could still make sense in order to reduce application startup time, but would not affect stable run time (which is perf after queries have already been compiled). See #1906 and #16496 about this.
Now, there's still an overhead of getting to the cached SQL. If perf is extremely important to you, you can use compiled queries to avoid that as well.
Beyond that we're aware that EF Core's runtime performance can be improved, and this is one of areas of focus for the 5.0.0 release.
Hope that explains the situation, if I've misunderstood you suggestion please post back - will leave this open for a bit.

I think in most real-world scenario this would be very complicated, expecially in dynamic query that depends on variables not known at compile time ( i refer mainly to not-static "where" / "order by" condition, that canno't be mapped as parameters)
example:
var query = (IQueryable<MedicalReportSection>)dataContext.MedicalReportSections;

if (!string.IsNullOrWhiteSpace(command.Filter.Text))
{
	query = query.Where(a => (a.Name).Contains(command.Filter.Text))
		   .OrderBy(a => a.Name.IndexOf(command.Filter.Text));
}
else
	query = query.OrderBy(a => a.Order).ThenBy(a => a.Name);

an access to a related entity will cause an additional join in the middle of the query, hard to manage statically.

I think in most real-world scenario this would be very complicated

What exactly do you think would be very complicated? Most of what I referred to above is already implemented and working.
In any case, the example you gave above isn't really a dynamic query scenario - it's just a scenario with two query structures. The moment one of these is executed, it is compiled and then cached - just like with any normal query - and will then be reused. EF already handles these in an efficient manner. It's true that this could present some significant challenges to any design-time optimizations (which again, would only help startup performance and not stable query execution times), but we're far from that in any case.
Note that it possible to produce "truly dynamic" query structures, e.g. where the number and/or composition of Where predicates depends on variables which change all the time. This kind of scenario is rare/exotic, and pretty much impossible to handle in an efficient way, since at some point each query structure has to be compiled independently. It also wouldn't be possible to do any sort of design-time optimization here, since nothing is known at design-time.

Don't want to generate a flame, I speak because in one of my projects i had to write something similar :)
In some query you have to filter / order a set based un user-defined criteria. In a simple if/else scenario you have only two cases. In 5 if scenario (each one is an optional criteria), you must take in account all 5 combinations 00001 - 00010 - etc (1/0 = criteria on/off, 2^5 = 32 combinations)
Or dynamic concat the strings in order to add all the pieces in the select /where / from / order by statements.
In EF each criteria is stored in memory once is added, so in the end you can optimize what you have, and easly translate in that unique sql query

After doing some benchmarks, it seems that compiled queries perform better than I thought.  The performance is comparable to Dapper.
Is there a reason for compiled queries to be static funcs?  It'd be neat to get the benefit of compiled queries while just writing standard linq.

@aguerrieri82 no worries about starting a flame :) There's nothing inherently wrong with dynamically constructing queries, you just need to be aware of the perf impact of that. 32 combinations isn't that much - EF Core will compile these 32 combinations and cache them internally without any issue, this should already work quite efficiently. On the other hand, if you allow for a totally open dynamicity which can lead to query explosion, you may encounter a severe perf degradation as EF is constantly forced to compile different query structures. I don't really think there's anything we can do about this. Again, none of this is really directly related to this issue ("translate to SQL at compile time").
@chrisevans9629 good to hear that you're seeing good perf with compiled queries. Compiled queries are expressed via standard LINQ - but you have to provide that LINQ once and tell EF Core to compile it. In the normal non-compiled case where you just use LINQ inline, EF Core receives a LINQ expression tree and has to look it up in its internal cache; this step can be quite heavy perf-wise, and the whole point of compiled queries is to avoid it.

I'm not sure this issue currently adds new information beyond what is already present in issues like #1906 and #16496, so I'll go ahead and close it for now. However, we can continue the conversation here and if something new comes up, we can reopen.

@roji AOT is the other situation where doing this at compile time is useful because then we can compile the needed materialization delegates rather than generating and compiling them dynamically. If we do something like this, which I hope we will, then I think that will be the primary motivator, even above startup perf. I suspect compiled models is likely to be the biggest win in startup perf.

Yeah. I admit my thinking about compiled models tends to focus on the negatives (but I haven't been in these conversations):

We get shapers, but only when the full entity gets projected out; when a query projects out arbitrary columns we lose this. I hope that doesn't mean we can't project out when on AOT.
Even related entities seem to make this difficult: unless we pregenerate shapers for all possible permutations of related entities (blogs alone, blogs with posts, blogs with posts and comments...), we again lose the advantage.
Unless I'm mistaken, we'd still need to go through query compilation for SQL generation. I'm not sure how much time goes into shaper generation/compilation vs. the rest of compilation, but if we're doing AOT it would be great if we could also cache the SQL. Ideally, at application startup we'd have everything we need.

So I tend to think more towards an approach that would analyze code, identify queries and somehow generate shapers and SQL from them at design-time (this could hopefully be made possible via the new code generators coming in C# 9). That may be overly ambitious or I may be missing various aspects of the problem.

@roji Is your point to distinguish compile-time from design-time?

Not really... My point is more that if we go into either compile-time or design-time as a way of speeding up startup times and unlocking certain AOT-only scenarios, doing so via the model only (without looking at queries) may simply not be sufficient...

(hope I'm making sense)

@roji I think we will likely have to do both. However, there are two different things in play here:

Reducing the amount of work done at startup
Fast execution of queries on an AOT-only platform

The first is likely dominated by model building and isn't directly related to AOT. The second is specific to AOT and is likely dominated by interpretation of IL on query execution.

OK, makes sense. I'm guessing that means that just pure model building (executing conventions etc., unrelated to any query execution) is enough of heavy task that it's worth going into compiled models (or rather, serialized models?). I'm interested in how much of startup time is dominated by model building vs. query compilation though, we should measure at some point on a reasonable scenario.

@roji Historically start-up time in EF Core has been dominated by model building. In EF6 view generation was also a big problem. Query compilation could also be a problem but this is probably much less common than model building perf.


Fix UI overlay scale factor for readable display on iOS devices

Fixes #1141.  Adjusts UI Overlay scale to value appropriate for iOS retina displays.  Affects iOS project only.
See the following results:
iPhone 15 on iOS simulator:

iPad Air (5th gen) on iOS simulator:

Thx. Very much appreciated :)


Collecting data from Windows workloads

I am running the GKE managed collection in a cluster with a mixture of linux and windows nodes. I can see that the collector is only deployed onto the linux nodes which means there is no metric collection for any of the pods running on the windows nodes. Is there any way to get the collector to either run on windows or collect from those windows nodes?

Hey Mike,
Our binaries only work on Linux nodes. You could scrape Windows by running our self-deployed collector on a Linux node and configuring it to reach out to exporters running on Windows nodes.

Thanks I will look into that. It would be really useful if the managed operator could deploy and single instance of the collector which has a selector for Windows nodes rather than $(NODE_NAME)


0077 JavaScript Code Samples 2

Submitting a bounty to add more code samples and fix depreciated ones to capture more common tasks in JavaScript.

I suppose milestone 3 should be around $2500 since it's a bigger job as compared to the other milestones, I will not pursue it tho :)

I suppose milestone 3 should be around $2500 since it's a bigger job as compared to the other milestones, I will not pursue it tho :) . Same goes to milestone 5 @ ~$2000 as well.

Thanks @wojake! I will need budget confirmation first then will adjust the award prize. But yea those 2 should take more effort, even though we have Python version as guideline.


Web console: update dev dependencies

Description
This PR updates web-console dependency versions that are relatively safe and straightforward to upgrade. Some highlights:

TypeScript 4.2
Webpack 5
Jest 26
Prettier 2 (via awesome-code-style)

With the upgraded packages, npm install will now succeed on Node 14 without needing node-gyp.
And a couple of configuration changes:

Enable sourcemaps in development mode for nicer debugging in the browser
Set TypeScript module format to esnext to allow webpack to tree-shake

And finally, I removed some packages that were not being used.

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[x] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

Thank you for the dependency updates, what a breath of fresh air!
The CI failure in the e2e tests looks legit:

also with all the dependency updates please make sure to run the script script/licenses from the web-console directory. It should update the root license listing with the new versions of the modules per Apache requirements.

@vogievetsky Thank you, I updated the licenses. It looks like tslib >= 1.11.2 is now licensed under 0BSD, which does not require inclusion of the copyright header. (Druid formerly used 1.10, which was Apache 2.0 licensed).
And I think the e2e test failure is due to Travis using a really old version of Node for that one step since it doesn't run through mvn. I'm not a Travis expert, but I attempted to ask it for Node 10 to match the rest of the pipeline. We'll see if he listens.

Nice!

...

Nice first contrib. good start, keep it up!


Highlight function calls, variables and more

The first image below shows what the highlighting looks like with this patch. (In particular, issue #133 is partially addressed. I think it's possible to address that issue fully by following the approach taken in the builtin JavaScript extension.)
The second image below shows that this patch fails to highlight simple function names that appear in multi-line pipes. I haven't yet figured out a way to match such names since VSCode only checks one line at a time unless one uses begin and end (which require the presence of some kind of delimiters).
By the way, the theme file mixed tabs and spaces, and I took the liberty of converting it to spaces only. Sorry for polluting the pull request with this.

This is very nice. (I just have one comment to be fixed).

I think once this is merged in this is probably as far we can go, before going for the full deal: https://github.com/flix/vscode-flix/issues/122

Thanks for taking a look (again) and clearing up my misunderstandings. 🙂

Merged. Thanks!
If you want, I am happy to provide some guidance for #122. Obviously that one requires a bit more work, both in VSCode and in the Flix compiler.

Thanks a lot for the offer, Magnus! I don't know when I'll have time again, so I'm hesitant to make any promises at this point. But I'll try to read up on it when time permits. I'll have to get to grips with that LSP stuff at some point. 😉