FBinaryInstructions have compressed encodings

Yes, the compiler will generate them
Yes, they're as useless as they sound (the Bt and the upper bits of the B field are forced to zero, so you can only use them with the constants 0/64 to 15/64)
When compiled with fast math off...
kernel void yay(uint u [[thread_position_in_grid]], device float2* fout, device half2* hout, const device float* fin, const device half* hin) {
	fout[u] = float2(fin[u] * 0.f, fin[u] + 0.f);
	hout[u] =  half2(hin[u] * 0.h, hin[u] + 0.h);
}

   0: 72091004             get_sr           r2, sr80 (thread_position_in_grid.x)
   4: 0509480e00c01200     device_load      0, i32, x, r1, u4_u5, r2, unsigned
   c: 3800                 wait             0
   e: 1a018202             fmul32           r0, r1.cache, 0.0
  12: 2a05c202             fadd32           r1, r1.discard, 0.0
  16: 4501400e00c43200     device_store     0, i32, xy, r0_r1, u0_u1, r2, unsigned, lsl 1, 0
  1e: 85044c0e00c01000     device_load      0, i16, x, r0h, u6_u7, r2, unsigned
  26: 3800                 wait             0
  28: 16008100             fmul16           r0l, r0h.cache, 0.0
  2c: 2602c100             fadd16           r0h, r0h.discard, 0.0
  30: c500440e00c43000     device_store     0, i16, xy, r0l_r0h, u2_u3, r2, unsigned, lsl 1, 0
  38: 8800                 stop

Or with fast math on...
kernel void yay(uint u [[thread_position_in_grid]], device float2* fout, device half2* hout, const device float* fin, const device half* hin) {
	fout[u] = float2(fin[u] * (15.f/64.f), fin[u] + (15.f/64.f));
	hout[u] =  half2(hin[u] * (15.h/64.h), hin[u] + (15.h/64.h));
}

   0: 72091004             get_sr           r2, sr80 (thread_position_in_grid.x)
   4: 0509480e00c01200     device_load      0, i32, x, r1, u4_u5, r2, unsigned
   c: 3800                 wait             0
   e: 1a0182f2             fmul32           r0, r1.cache, 0.234375
  12: 2a05c2f2             fadd32           r1, r1.discard, 0.234375
  16: 4501400e00c43200     device_store     0, i32, xy, r0_r1, u0_u1, r2, unsigned, lsl 1, 0
  1e: 85044c0e00c01000     device_load      0, i16, x, r0h, u6_u7, r2, unsigned
  26: 3800                 wait             0
  28: 160081f0             fmul16           r0l, r0h.cache, 0.234375
  2c: 2602c1f0             fadd16           r0h, r0h.discard, 0.234375
  30: c500440e00c43000     device_store     0, i16, xy, r0l_r0h, u2_u3, r2, unsigned, lsl 1, 0
  38: 8800                 stop

lol, good catch


Resolves #5463

Summary of the changes / Why this improves CrateDB
This patch implements bitwise AND operator for integer types. Other types, like implemented in MySQL for example, see https://dev.mysql.com/doc/refman/8.0/en/bit-functions.html, are out of scope for this patch but perhaps can be added later as required.
Checklist

[ N] Added an entry in CHANGES.txt for user facing changes
[ Y] Updated documentation & sql_features table for user facing changes
[ Y] Touched code is covered by tests
[ Y] CLA is signed
[ Y] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Can one of the admins verify this patch?

@antbob Related to the comment about comparison operator vs. scalar function: the feature description at #5463 is a bit confusing/not completely clear, please apologize ;-)
Any suggestion how we could satisfy both use-cases?

@antbob Related to the comment about comparison operator vs. scalar function: the feature description at #5463 is a bit confusing/not completely clear, please apologize ;-)
Any suggestion how we could satisfy both use-cases?

It seems that the way you currently use Antlr parser is setup to treat bitwise AND as comparison operation only. So I would start there. I'm no expert on Antlr or SQL but it seems to me that you would wanna treat bitwise AND as either comparison op or scalar op depending on SQL context. What sucha change would involve practically I cannot say without spending more time digging into it further.
Anyways, I'm gonna close this PR bc it clearly does not address the issue properly and I do not have spare cycles right now to investigate and rework it accordingly. Thank you for your time and review!


Updated context.send to add flags

Responding to interactions should allow to set "flags" so users can decide whether its an ephemeral message or not.
More information: https://discord.com/developers/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-data-flags
About this pull request
Description of the pr
Changes
What changes were made?
Checklist

[ ] I've run the pre_push.py script to format and lint code.
[ ] I've checked this pull request runs on Python 3.6.X.
[ ] This fixes something in Issues.

Issue:

[ ] This adds something new.
[ ] There is/are breaking change(s).
[ ] (If required) Relevant documentation has been updated/added.
[ ] This is not a code change. (README, docs, etc.)

#359 is doing it already

Duplicate of #359 .


Package should support Ember 3.4.7

It seems like<EMAIL_ADDRESS>was released shortly after the most recent version of this add-on. For any users choosing to bump to 3.4.7 instead of 3.5 or later (probably not many) or Ember Add-on authors that are testing against a generic 3.4 version (probably many), this package should support 3.4.7.

Yep, definitely agree.

I wanted to take care of fixing this myself, but I'm not sure where the vendor/ember-native-class-polyfill/*.*.*/ files are generated.
If someone can let me know where that comes from (and presumably, how they are doctored) I'm happy to make the PR to close this issue.

Note: I think the lack of support here also explains why the tests are failing, since the 3.4.0 scenario in Ember Try is running against the unsupported 3.4.7

The polyfill branches are

3.4 https://github.com/emberjs/ember.js/pull/17167
3.5 https://github.com/emberjs/ember.js/pull/17168

It should be possible to rebase the current branch ontop of the latest patch release and rebuild. For the non legacy part of the polyfill, you have to remove all of the ES5 transforms. I can do this later today, but happy to merge if you have time.

I probably won't have time, to be honest. I have a bunch of work stuff on my plate for today.

Support for 3.4.7 added in v1.0.5!


Remove deprecated fields.

These prevents latest from being installed.

/assign @nak3 @ZhiminXiang

Will the auto TLS not enabled? Or it will still be enabled without these explicit configuration?

This
  meshConfig:
    defaultConfig:
      proxyMetadata:
        TERMINATION_DRAIN_DURATION_SECONDS: "20"

seems enough.

/hold

A PeerAuthentication seems required now. Let me test this.

/hold cancel


Change namespaces of Public API

This is a list of the names that need to change from sub-namespaces to the hpx namespace. So far the list consists of the following:

[x] hpx::traits::is_bind_expression
[x] hpx::traits::is_placeholder
[x] hpx::experimental::bind_back
[x] hpx::util::mem_fn (see #6067)
[x] hpx::util::invoke,  hpx::util::invoke_r (see #6048)
[x] hpx::util::invoke_fused (see #6052)
[x] hpx::util::basic_any NO NEED TO MOVE THAT
[x] hpx::chrono::high_resolution_clock NO NEED
[x] hpx::chrono::high_resolution_timer NO NEED
[x] hpx::chrono::steady_time_point NO NEED
[ ] all the names in hpx::execution namespace LEAVE AS LAST
[x] hpx::lcos::local::channel
[x] hpx::util::unlock_guard (see #6086)
[x] hpx::parallel::v1::reduce_by_key (experimental) (see https://github.com/STEllAR-GROUP/hpx/pull/6100)
[x] hpx::parallel::v1::sort_by_key (experimental) (see https://github.com/STEllAR-GROUP/hpx/pull/6100)
[x] all the names in header file task_block.hpp (experimental) (see https://github.com/STEllAR-GROUP/hpx/pull/6126)
[x] all the names in hpx::functional namespace NO NEED
[x] task_group (see https://github.com/STEllAR-GROUP/hpx/pull/6136)

More generic changes:

[ ] Remove our steady_time_point and steady_duration implementations as we have removed support for boost::chrono

Suggested changes for the each name.
--> hpx::is_bind_expression
--> hpx::is_placeholder
--> hpx::bind_back
--> hpx::mem_fn (already deprecated)
--> hpx::invoke, hpx::invoke_r (already deprecated)
--> hpx::invoke_fused (already deprecated)
--> No need to change
--> No need to change
--> No need to change
--> No need to change
--> Leave as the last step
--> No need to change
--> hpx::unlock_guard (already deprecated)
--> hpx::experimental::reduce_by_key (already deprecated)
--> hpx::experimental::sort_by_key (already deprecated)
--> hpx::experimental::task_block (already deprecated)
--> No need to change
--> hpx::experimental::task_group

Went through the list again, looks like we are only left with 2 points, the steady* and the execution.


RequireScope

AuthorizationPolicyBuilder' does not contain a definition for 'RequireScope' and no accessible extension method 'RequireScope' accepting a first argument of type 'AuthorizationPolicyBuilder' could be found (are you missing a using directive or an assembly reference?)
Besides getting this error on RequireScope, I would welcome some more explanation. What is it doing, and in what scenario should I use the RequireScope?
(Thanks for the excellent document, I migrated a large app in a couple of hours, with this explanation)

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

ID: 76f39eec-9dd1-6167-56ec-47b26e0b5063
Version Independent ID: f9f2b0f3-01eb-cf58-8767-194fe0fc0e44
Content: Migrate from ASP.NET Core 2.2 to 3.0
Content Source: aspnetcore/migration/22-to-30.md
Product: aspnet-core
Technology: aspnetcore-migration
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@blowdart  can you provide more info on  .RequireScope("MyScope")

No, because I don't know where it came from either.
Unless @javiercn says this is from some spa extension best to check who added that, and ask them

@HaoK  please review.

There is no such method in our APIs, so we probably should remove that from our migration guide, or at least point out that its specific to identity server so only a specific subset of our templates that are using that, its at the bottom of: (http://docs.identityserver.io/en/latest/topics/apis.html)


Fix bug in TensileCreateLibrary

In #1073 , asmKernels was changed to a generator to reduce memory usage. However, generators can only iterate once, asmArchs is always empty.
Merged two loops to resolve this issue.

========= 76 passed, 32 skipped, 1256 warnings in 19707.61s (5:28:27) ==========
py3: exit 0 (19707.90 seconds) /home/awang105/hipBLASLt/tensilelite> py.test -v --basetemp=/tmp/.tensile-tox/py3/tmp --junit-xml=/home/awang105/hipBLASLt/tensilelite/python_tests.xml --junit-prefix=py3 --color=yes -n 4 --prebuilt-client=/tmp/.tensile-tox/py3/client/0_Build/client/tensile_client Tensile/Tests -m common pid=1113533
py3: OK (19860.48=setup[14.29]+cmd[0.42,137.87,19707.90] seconds)
congratulations :) (19860.55 seconds)
[----------] Global test environment tear-down
[==========] 48206 tests from 13 test suites ran. (4220439 ms total)
[  PASSED  ] 48206 tests.
hipBLASLt version: 1000


DPL-043 Manifest upload causing duplications in EGA

When manifests are uploaded duplicate entries are being made in the EGA database (nearly always)
Example manifest (non sensitive data generated for testing)
2405stdy_manifest_17293_170621.xlsx
Duplicate entries (scraped from the EGA Webin page (https://www.ebi.ac.uk/ena/submit/sra/#home)
repeat_EGA_entries.xlsx
When 2405STDY10409901 is viewed in sequencescape_warehouse.samples ('old' warehouse) there are two accession entries EGAN00003219314 and then EGAN00003219315, both with the same timestamps.
James G's comments (from Slack 17/06/21)
"Suspect we’re creating and then updating samples, and generating an accession job for each action. I’m not quite sure why both accessions are succeeding and returning different number though, I’m assuming the EBI have a similar race condition

When we try to update them via Sequencescape EBI doesn’t know which one to update so returns “More than one object found with alias”

So pretty sure the problem is multiple delayed jobs, but weirdly on upload i'm not actually seeing any generated in dev after supposedly enabling the feature. Reason being that studies isn't populated on sample, so they are flagged as invalid. Can't see why this would be different in production...

Hmm, and looking at the code, I don't think the delayed jobs for accessionables is fetching the sample from the database, but is using the serialized copy in the job itself. This isn't ideal, as we're dependent on job order for ensuring the EGA version is the latest.

Hmm, so seeing dupe delayed jobs happening on sample update in prod. Doesn't mean that there aren't ones on create, just looking at what I've found.

Checking with Neil the plausibility. Neil's manifest example appears to have shown accession updating on creation, but was uploaded before the recent manifest changes, so perhaps the bug got introduced then.

Checking out the version prior to recent changes to see if studies are loaded on the samples correctly. It should be an easy fix, but a bit confused why its not been noticed.

Hmm, issue still exists before then...

Ooohh, barking up wrong tree! We're reloading from database, so my studies were invalid for some other reason. Okay. Can work with this now.


6D poses groundtruth in real_objects.zip

Dear authors,
thanks first for providing this useful and diverse dataset. In the paper you said you also save the 6D poses for the real_object dataset. What I found is the xxxxxx-meta.mat for each image and inside has 7-dim vectors for each marker and a 9-dim "joint_position". However I didn't find the translation and rotation matrix for each image. Could you explain what these values are and where you store the 6D pose groundtruth? Thanks!

Hello,
The 7-dim vectors for the marker is the pose of the marker. The first 3 numbers are translation. The last 4 numbers are quaternion.
To obtain the object pose, you can use this function to compute it:
https://github.com/IRVLUTD/fewsol-toolkit/blob/d458820457497fdba5729bc574e6744cff26fcf6/tools/image_loader.py#L146
meta['center'] = RT_centers[index] in the code is the object pose.

Hi @yuxng,
Thank you so much.


No more rustls?

I noticed during pull request 651 that rustls was commented out. This seems detrimental to me. Is there something wrong with rustls?

I still want it in, but new versions of tokio/hyper were required and hyper-rustls hasn't updated, that's all.

That's good news, I am looking to utilize rustls and was a bit concerned it had some flaws I was unaware of. Thank you for you fast response.


Custom Ammo types

Description
Add the ability to use different types of cartridges, armor-piercing, incendiary or explosive. (The player could create such types himself).
Configuration
  Reload:
    Trigger: <trigger serializer>
    Magazine_Size: <amount>
    Ammo_Per_Reload: <amount>
    Unload_Ammo_On_Reload: <true/false>
    Reload_Duration: <ticks>
    Start_Mechanics: <MechanicsSerializer>
    Finish_Mechanics: <MechanicsSerializer>
    Ammo:
      Out_Of_Ammo: <MechanicsSerializer>
      Ammo_Type_Switch:
        Trigger: <TriggerSerializer>
        Mechanics: <MechanicsSerializer>
      Ammo_Types: <path to another Ammo Types key>
        1_Ammo_Type:
          Symbol: <symbol>
          Item_Ammo:
            Bullet_Item: <ItemSerializer>
            Magazine_Item: <ItemSerializer>
            Ammo_Converter_Check:
              Type: <true/false>
              Name: <true/false>
              Lore: <true/false>
              Enchants: <true/false>
          Features:
            Damage: <amount>
            Give_Potion_Effect:s <true/false>
            Potion_Effects:
              - <PotionEffectType>-<Duration>-<Level>
              - <PotionEffectType>-<Duration>-<Level>-<Allow Particles>-<Extra Particles>-<Icon>
              - <etc.>
            Explosion: <true/false>
            Explosion_size: <amount> #How big is this explosion from a bullet
            Explosion_Damage: <amount>
            Explosion_Other: <true/false> #can other players take damage from the bullet explosion
            Explosion_Sound:
              - <sound>-<volume>-<pitch>
              - <sound>-<volume>-<pitch>-<delay>-<pitchNoise>
              - custom:<sound>-<volume>-<pitch>
              - custom:<sound>-<volume>-<pitch>-<delay>-<pitchNoise>
          Experience_As_Ammo_Cost: <experience per one ammo>
          Money_As_Ammo_Cost: <money per one ammo>
        2_Ammo_Type: <etc.>

Will add into addon along attachments


[Question]: ModuleNotFoundError: No module named 'minference.cuda'

Describe the issue
I encountered some issues when using minference in Python.
import minference
The problem is Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/workspace/MInference/minference/__init__.py", line 8, in <module>     from .models_patch import MInference   File "/workspace/MInference/minference/models_patch.py", line 7, in <module>     from .patch import minference_patch, minference_patch_vllm, patch_hf   File "/workspace/MInference/minference/patch.py", line 12, in <module>     from .modules.minference_forward import (   File "/workspace/MInference/minference/modules/minference_forward.py", line 20, in <module>     from ..ops.pit_sparse_flash_attention_v2 import vertical_slash_sparse_attention   File "/workspace/MInference/minference/ops/pit_sparse_flash_attention_v2.py", line 10, in <module>     from ..cuda import convert_vertical_slash_indexes ModuleNotFoundError: No module named 'minference.cuda'
enviornment :
Python 3.10.14
minference 0.1.4.post3
triton 2.1.0
torch 2.3.0
CUDA 11.8
vllm 0.4.2+cu118
flash-attn  2.5.8

Hi @lai-serena, thanks for your feedback.
It looks like the build was unsuccessful. You can try installing it using the following method:
pip uninstall minference -y
MINFERENCE_FORCE_BUILD=TRUE pip install minference --no-cache-dir

or build from source,
``bash
git clone https://github.com/microsoft/MInference/
cd MInference
pip install -e .

pip install -e .  works for me. Thanks!


Cache miniconda installations on travis?

I.e. for each build, $HOME/miniconda would be extracted from the cache, then conda install dependencies would run (which will only update things that have changed), then the cache would be updated.
In many ways, this could be a better test than installing from scratch, since most users will be updating existing conda installations/environments rather than starting from scratch.
Installing miniconda and dependencies from scratch every time takes up a lot of the total build time for many projects (particularly the smaller projects).

I'm all for it, and have been wondering whether that was possible several times over the past few days while watching builds spend most of their time fetching miniconda.  If it's practical, please please do it!

Caching does indeed seem to speed things up (usually cache store/fetch and update dependencies seems to take about 1-1.5 minutes, while creating a conda installation from scratch can take much longer).
However, caching will inevitably come with some complications. Some of those will be ones faced by users anyway, while some will come from managing the cache(s) in general...

That sounds as expected; why close this?

Sorry, I forgot to say that it's implemented (e.g. in datashader WIP packaging PR),
which is why I closed it. It will be part of the documentation here (probably as example Travis config, or link to example), along with some other ci system specific things.

Ah, now that makes sense, thanks!


Recreating how ordes are placed by removing cart orders

Refactored the UserRelatedField to a UserSerializer that is the same for all API endpoints.
Added an endpoint where a logged-in user can retrieve its details (/users/me).
Moved the .loader CSS class to tosti.
Removed the PlaceOrderView in favor of buttons on the Order list page.
Refactored start_date and end_date to start and end in Shifts.
Added order buttons to the Order list page.
Removed the ability to add multiple user orders at once within the orders app code.
Removed the CartOrderAPIView together with the Cart.
Removed some duplicate API fields from order and shift endpoint.

Closes #208

I think this is far from actually mergable but I would appreciate it if you gave some feedback now so that I can take that into account before actually merging. You could also alter the interface a bit if you want.

these should be centered, the text should be larger and the icon should be added. Also, the whole block should be clickable, not only the add button (though there should be an add-button)
When placing an order, the toast in the upper right corner should not only say "an order was placed" but also what you actually ordered.

these should be centered, the text should be larger and the icon should be added. Also, the whole block should be clickable, not only the add button (though there should be an add-button). If you want, I can re-design this
When placing an order, the toast in the upper right corner should not only say "an order was placed" but also what you actually ordered.

This has been changed. I would appreciate it if you changed the interface a bit 😝

Waiting for new data is now done correctly, OrderSerializer and ProductSerializer are also adjusted to support a POST to the OrderListCreateAPIView that lists the required product under the product and not under the product_id.

@KiOui the javascript crashes on orders with no order id, while this is possible


Consider upgrading to jwt-go 3.0.0

Hi Aeneas!
So, i'm still following the development of all your libraries and we've just now started to implement our interfaces against fosite/hydra. It came to a quick halt when we realized that fosite relies upon v2.7.0 of jwt-go, and that we must use 3.0.0 of jwt-go. We also use glide and this is causing a clash since jwt-go have introduced a breaking change by replacing the map[string]interface{} to a jwt.Claims interface (essentially exactly like your jwt_claims.go).
Do you want help fixing this change (more or less just upgrade to 3.0.0 of jwt-go and create a new type that implements the Claims interface in fosite) or is this on your backlog?
Regards
Alexander W

@leetal yes, I welcome if you could help me with upgrading to 3.0. This has been a pain ever since they broke bc. :)


Complete: Mihir: Tasks 97-101: OpenBookQA and CLUE datasets

@Mihir3009, wondering if you can review these?

Update Readme summary like this:

Task 97: Given a fact, generate a question that can be answered using given the fact
Task 98: Given a fact and question, generate an answer to the question
Task 99: Given a fact and question, generate three incorrect answers to the question
Task 100: Given a question and answer, generate a fact statement
Task 101: Given a Chinese passage, generate a question based on the passage
Task 98:

Change definition like this:

In this task, you are given a fact statement and question based on the fact. Your task is to generate the correct answer for the question. The answer needs to be generated using a context fact statement.
Task 99:
Why three incorrect answers? Why not one at a time?
Task 100:

Change category to "Sentence Generation" (change file name accordingly)
Let's change the definition like this:

In this task, you are given a question and a corresponding answer. Your task is to generate a fact statement that is useful in answering the given question.

Add explanation in positive examples

Task 101:

While saving JSON file use this, this will save Chinese text:
json.dumps(your_json_string, indent=4, ensure_ascii=False)

Add language indicator to the schema:

"Input_language": language of the input/instructions
"Output_language": language of the responses/output
"instruction_language": ["en"]
We can specify these languages via their two-digit ISO 639-1 code.

Change definition:

Given a passage in simplified Chinese, generate a reading comprehension question. The question should be unambiguous and the answer to this question should be in the passage.

@ebell495, can you address reviewer comments so that I can grade your HW?

I've pushed my changes to address their comments.

@swarooprm I am happy with this PR. Looks good to me.

Your HW2 is complete now.
Would you like to submit the same tasks to our big project repo https://github.com/allenai/natural-instructions-expansion/pulls? You just need to fork that repo, rename tasks starting from the latest number in the repo and create PR there. This way, you can be part of our research on "learning from instructions instead of learning from examples (conventional machine learning)". This is purely optional and your HW2 grade does not depend on this @ebell495

@ebell495, Just a reminder that, if you plan to submit these tasks to the main Github repo and join our research project, Monday (27th Sept) is the deadline. Again, this is optional and independent of your HW2 grade.


Obtain IRS publication 583 (Tax Calendar for Small Business)

Completed and saved in Google Drive https://drive.google.com/drive/folders/1oBefslx-WxMxBQT8rKrd5BATm8Bmu-mo


[Paper] Allow the box shadow color to be changed

This allows dark or custom themes to change the box-shadow color of paper elements

If you think the code is okay now, I can squash the commits to have a cleaner merge ;)

I squashed everything into one small commit to have a cleaner log ;)

@tibdex Merci!


Cant schedule workouts - Exception in thread "main" java.util.concurrent.ExecutionException: Boxed Error

Hi, im trying use your program to schedule some training plan. Just copy & paste example from this page ( 2w plan ) into Libre office and save as CSV ( added as attachment ) giving me that result.
d:\DOWNLOAD\quick-plan-0.3.1\bin>quick-plan.bat schedule -s 2018-12-01 -e pschonmann TEST.csv

[WARN] [11/29/2018 23:01:34.631] [quick-plan-akka.actor.default-dispatcher-5] [akka.actor.ActorSystemImpl(quick-plan)] Illegal header: Illegal 'expires' header: Illegal weekday in date 1997-07-26T05:00:00: is 'Mon' but should be 'Sat'

Creating workouts:
Successfully logged in to Garmin Connect
Logged out and closed connection
Exception in thread "main" java.util.concurrent.ExecutionException: Boxed Error
        at scala.concurrent.impl.Promise$.resolver(Promise.scala:83)
        at scala.concurrent.impl.Promise$.scala$concurrent$impl$Promise$$resolveTry(Promise.scala:75)
        at scala.concurrent.impl.Promise$KeptPromise$.apply(Promise.scala:402)
        at scala.concurrent.Promise$.fromTry(Promise.scala:138)
        at scala.concurrent.Promise$.failed(Promise.scala:124)
        at scala.concurrent.Future$.failed(Future.scala:620)
        at com.github.mgifos.workouts.GarminConnect.$anonfun$createWorkouts$4(GarminConnect.scala:71)
        at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:304)
        at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:37)
        at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
        at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
        at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)
        at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
        at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:81)
        at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:91)
        at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:40)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:43)
        at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
        at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: java.lang.Error: Cannot create workout
        ... 15 more

TEST.zip

Oh, worked! Seems account was locked :(

I managed to reproduce it by using my username instead of my email address. I'll close this issue,  but some validation could be handy here in the future.


Fix the bug caused when pointers is an unordered array.

Codecov Report
Base: 37.88% // Head: 36.64% // Decreases project coverage by -1.24% :warning:

Coverage data is based on head (c35b8c4) compared to base (8159297).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1291      +/-   ##
==========================================
- Coverage   37.88%   36.64%   -1.25%
==========================================
  Files         348      348
  Lines       16648    16645       -3
  Branches     2620     2619       -1
==========================================
- Hits         6307     6099     -208
- Misses       9755     9997     +242
+ Partials      586      549      -37

Impacted Files
Coverage Δ

packages/core/src/input/pointer/PointerManager.ts
24.37% <0.00%> (+0.35%)
:arrow_up:

packages/core/src/RenderPipeline/RenderContext.ts
28.57% <0.00%> (-71.43%)
:arrow_down:

...ges/core/src/RenderPipeline/BasicRenderPipeline.ts
20.16% <0.00%> (-33.07%)
:arrow_down:

packages/core/src/Camera.ts
24.02% <0.00%> (-22.91%)
:arrow_down:

packages/rhi-webgl/src/WebGLRenderer.ts
37.68% <0.00%> (-21.02%)
:arrow_down:

...ckages/core/src/shadow/CascadedShadowCasterPass.ts
14.20% <0.00%> (-16.40%)
:arrow_down:

packages/core/src/RenderPipeline/SpriteBatcher.ts
6.66% <0.00%> (-14.67%)
:arrow_down:

packages/core/src/base/Util.ts
16.21% <0.00%> (-8.11%)
:arrow_down:

packages/core/src/RenderPipeline/RenderQueue.ts
2.06% <0.00%> (-7.59%)
:arrow_down:

packages/core/src/shader/ShaderMacroCollection.ts
37.33% <0.00%> (-6.67%)
:arrow_down:

... and 10 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.


File upload using proxy and express

It seems that file upload from the express app using proxy is not working.
We do have used the body parser and have not used the multer in express app.
And on file upload, the source app throws error that the file is missing.
However the file upload in source app without proxying works
It seems to be that we are missing something while uploading the file using proxy app. Could you please help with that?
Thanks,
Raghu

Please use StackOverflow. I think that would be a better place to troubleshoot your setup.
Thanks.
How to Ask Good Coding Questions That Get Great Answers...


isCached issue

I'm using this to cache my results data and console log (isCached)

However, I keep getting this error:
Error fetching results: TypeError: aggregation.pipeline is not a function
at generateCacheKeyFromPipeline (test\node_modules\speedgoose\lib\src\utils\cacheKeyUtils.js:15:27)
at prepareAggregateOperationParams (test\node_modules\speedgoose\lib\src\utils\queryUtils.js:47:180)
at mongoose.Query.isCached (test\node_modules\speedgoose\lib\src\extendAggregate.js:12:58)
at test\server.js:608:48
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Any ideas?

Thanks for this finding.
Fixed in https://github.com/arqo123/speedgoose/pull/74
New version 2.0.9


[BUG] CSV to Editor failed

My simple CSV content:
111,222,333
444,555,666
777,888,999

Select these lines, invoke Table Editor. It responsed:

Obsidian: v0.14.9
Table Editor: latest version

Looks like only '|' delimiter is getting parsed in the latest version. Will fix it

Can you check and confirm this in the latest version?

It's OK now. Thanks.


Compiled module was created by a different version of the compiler '<IP_ADDRESS>'

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
After updating to macOS 15.0 Sequoia, updating Xcode and trying to re-build my project, I'm getting the following error:
Compiled module was created by a different version of the compiler '<IP_ADDRESS>'; rebuild 'Supabase' and try again: /Users/antoni/Library/Developer/Xcode/DerivedData/[project-name]/Index.noindex/Build/Products/Debug-iphoneos/Supabase.swiftmodule/arm64-apple-ios.swiftmodule

To Reproduce

Create project in macOS 15.0 Sequoia in Xcode 16.0.
Add supabase-swift to that project.
Select target device with iOS 18.0.
See error

Expected behavior
Should just build without errors on latest macOS/Xcode versions.
System information

OS: macOS 15.0 Sequoia, Xcode 16.0
Version of supabase-swift: 2.18.0

Additional context
I'm pretty sure this is solvable by just rebuilding the project without any changes using the latest Xcode?

Just realised, this issue should be fixed if #468 is merged.

Hi @bring-shrubbery, the library should work fine with macOS 15.0 Sequoia and Xcode 16.0.
Please, try to clean your DerivedData folder and do a clean build of your project.

Hey @grdsdev
You're correct, after force-cleaning DerivedData it worked! Thanks for help, and sorry for unnecessary issue 🙏

it does not work for me, clean the DerivedData folder and do a clean build

@Wangggym that isn't Supabase package.


Initialization and default values

Using GlobalStore example for AsyncStorage in my RN app, I've some problems with having centralized handling for simple settings, as the locale for the app.
I must wait for the user setting for its I18n language to be read from async storage, and just then build its menu, etc.
I 've wrote something like this:
const localeStore = new GlobalStore<string, any>('default', {
  asyncStorageKey: 'locale',
});

const useLocaleStore = localeStore.getHook();

const DataContextWrapper = (props: any): any => {
  // settings
  const locale = useLocaleStore();
  const [localeValue, _, localeMeta] = locale;
  const [localeReal, setLocaleReal] = useState<string | undefined>();

  useEffect(() => {
    if (localeMeta.isAsyncStorageReady) {
      setLocaleReal(
        localeValue === 'default' ? getDefaultLocale() : localeValue
      );
    }
  }, [localeValue, localeMeta]);

...
}

On app first install, when there is no setting at all on the Async StorageisAsyncStorageReady is always false.
I've seen the testing of it on the sources, and found this:
https://github.com/johnny-quesada-developer/react-native-global-state-hooks/blob/f4f9fed5016ac3dd4a5741f795f72e13dd0e7aae/%40tests/__test__/GlobalStoreAsyc.test.ts#L7
It seems the test is putting a default value on this fakeAsyncStorage, which is not something I can easily do in my code.
I can't find a way to make this sequence right: I need isAsyncStorageReady: true  and the "default" value to be provided on first app install
Any help would be nice.

Hi @jacargentina ,
Thanks for reaching out! I understand your situation and will take a closer look at the code you shared to see if there's a way to make it work as intended. I will review your code today and let you know if I have any suggestions or solutions for your problem.
Thanks again for using our library and feel free to let me know if you have any further questions or concerns.

Hello Again @jacargentina ,
I hope you're doing well. I wanted to address your question about the GlobalStore class and the isAsyncStorageReady flag. Just to clarify, the flag is designed to automatically populate after the first data is retrieved from the asyncstorage. If the async storage is not available or if there is no data stored in it, the state will use the default value instead. The purpose of this flag is to differentiate between using the default value and using the stored value.
If you're still experiencing difficulties, please don't hesitate to let me know. I'm happy to take another look or provide additional resources if needed.
Thank you for reaching out, and I hope we can find a solution to your issue soon.
Best regards

Hi Javier,
Based on your explanation, it seems like you want to avoid loading the English songs when the app starts in order to save on resources and improve performance. You could use the isAsyncStorageReady to determinate whenever or not read the sounds and display an ActivityIndicator instead.
I updated the example of the GlobalStore with the AsyncStorage, here you can see a super simple example of how I implemented, Im using and ActivityIndicator based on the isAsyncStorageReady .
https://user-images.githubusercontent.com/62082152/227571041-c86ca372-5ba0-4f68-b390-278d80dc2e40.mov
Here you also have code example: todo-list-with-global-hooks.
I hope this information is gonna help you, otherwise dont hesitate in reach out back.

Thanks a lot @johnny-quesada-developer  for taking the time to see my case!
I'll try to play with your example repo and see if I'm using the lib wrong, and get back here to post my results

Hey @johnny-quesada-developer
I've tried on my app https://github.com/jacargentina/iResucito; modified it to use expo, and it seems to work.
So I think there is something related to my native "without expo" app, but I'm having a hard time to find the problem. If you have some time and want to clone and debug it? I understand if not.
Anyway, I will continue looking for it cause I love your library for handling these global states

@johnny-quesada-developer
This repo is an empty react-native app (no expo) which has the minimal reproduction case. Can u take a look?
https://github.com/jacargentina/AwesomeProject

Hi @jacargentina I'll take a look 👍

Hi @jacargentina ,
I apologize for the delay in my response. It has been a busy week. I took a careful look at the repository you shared and the problem seems to be related to how React works.
I updated the example in the documentation to include a small improvement in the GlobalStore with AsyncStorage. Instead of using :
if (storedItem === null) return;

I used the following:
if (storedItem === null) {
  const isPrimitiveState = isPrimitive(this.state) && !isDate(this.state);

  // This forces React to re-render the component when the state is an object
  return setState(isPrimitiveState ? this.state : {...this.state});
}

This will force a re-render when the state is not primitive, which is actually the main issue in your example. React performs the following validation when the GlobalStore reaches the AsyncStorage and tries to set the state value:
Object.is(oldState, newState).

If this execution block returns true, React will avoid re-rendering the component since the state is the same.
In this case, since we need to know when we are working with the AsyncStorage value and not the default one, you could simply use an object as the store value instead of a primitive string:
Insead of:
const localeStore = new GlobalStore('default', {
    asyncStorageKey: 'locale',
});

use:
const localeStore = new GlobalStore(
  {
    locale: 'default',
  },
  {
    asyncStorageKey: 'locale',
  },
);

Then, inside your component, your code will look basically the same:
// From:
const [locale, setLocale, { isAsyncStorageReady }] = useLocaleStore();

// To, we just use destructuring to get the value:
const [{ locale }, setLocale, { isAsyncStorageReady }] = useLocaleStore();

That's it! Since the store value is an object, once we reach the AsyncStorage and the state becomes a new object, React will re-render and you'll have all the necessary information to continue.
I hope this helps. If you have any further questions, don't hesitate to ask.

Hi @johnny-quesada-developer  Thanks a lot again for taking time on this.
I partially understand it; "locale" is "default" by default; then async storage reads the "default" again, so the value is the same.
BUT, then the problem is why isAsyncStorageReady  is not going from false to true ? Maybe you can put more light on my understanding on this.
Again, thank you a lot!

UPDATE: also, with the new GlobalAsycStore.ts (BTW it is missing an "n" letter) I'm having trouble with storing an array, where it has the empty array as the initial value.
const brothersStore = new GlobalStore<BrotherContact[], any>([], {
  asyncStorageKey: 'contacts',
});
const useBrothersStore = brothersStore.getHook();

TypeError: Invalid attempt to spread non-iterable instance.
In order to be iterable, non-array objects must have a [Symbol.iterator]() method.

Hello @jacargentina ,
I hope you are doing well. Thank you for your previous message... of course, it will be a pleasure trying to help:
Regarding the first topic, I want to clarify that the metadata was not designed to be reactive, as creating another state just for the purpose of reactivity would be unnecessary in most cases. However, the metadata will be updated every time the hooks are invoked.
As for the second topic, using non-primitive values as state is recommended because React performs a memory comparison to determine if the state has changed, which is not possible with primitive data types such as strings, numbers, booleans, nulls, and symbols.
'' === '' // true
true === true // true
1 === 1 // true
{} === {} // false case they are different objects
[] == [] // false

By using non-primitive values, you should not experience any issues with reactivity.
Lastly, I apologize for the oversight in the code, and I have replaced the destructuring for a clone function:
{ ...this.state } to clone(this.state)

The clone function will performs a deep clone of the state, ensuring that all objects are brand new and triggering React rendering.
If you have any further questions or concerns, please do not hesitate to let me know.
Best regards, happy easter!

Thanks a lot, I think this can be closed now

Thank you you for the feedback 👍💪 @jacargentina

Could the way to do this be added to the docs?
I have been hunting for a way to do this for a while now

Could the way to do this be added to the docs?
I have been hunting for a way to do this for a while now.
Love the package by the way!
Edit: Ignore me. There is a great explanation here.

I'll take care of that, thank you so much for the feedback.

Hi @jacargentina , @chrisvasey ,
The last version of the package 4.0.0 was released, please take a look into the documentation:

async-storage-with-global-state

The classes approach still present in the library but a couple of functions for creating global state and custom global state were added with the intention or simplify some task like the one you guys were describing.
Now you can create global states with a functional approach.
import { createGlobalState } from 'react-native-global-state-hooks';

export const useCount = createGlobalState(0);

In the same way, you can create a custom builder that allows you to inject additional functionality, such as asyncStorage synchronization, please take a look:
import { formatFromStore, formatToStore, createCustomGlobalState } = 'react-native-global-state-hooks'

// Optional configuration available for the consumers of the builder
type HookConfig = {
  asyncStorageKey?: string;
};

// This is the base metadata that all the stores created from the builder will have.
type BaseMetadata = {
  isAsyncStorageReady?: boolean;
};

export const createGlobalState = createGlobalStateWithDecoupledFuncs<
  BaseMetadata,
  HookConfig
>({
  /**
   * This function executes immediately after the global state is created, before the invocations of the hook
   */
  onInitialize: async ({ setState, setMetadata }, config) => {
    setMetadata((metadata) => ({
      ...(metadata ?? {}),
      isAsyncStorageReady: null,
    }));

    const asyncStorageKey = config?.asyncStorageKey;
    if (!asyncStorageKey) return;

    const storedItem = (await asyncStorage.getItem(asyncStorageKey)) as string;

    // update the metadata, remember, metadata is not reactive
    setMetadata((metadata) => ({
      ...metadata,
      isAsyncStorageReady: true,
    }));

    if (storedItem === null) {
      return setState((state) => state, { forceUpdate: true });
    }

    const parsed = formatFromStore(storedItem, {
      jsonParse: true,
    });

    setState(parsed, { forceUpdate: true });
  },

  onChange: ({ getState }, config) => {
    if (!config?.asyncStorageKey) return;

    const state = getState();

    const formattedObject = formatToStore(state, {
      stringify: true,
    });

    asyncStorage.setItem(config.asyncStorageKey, formattedObject);
  },
});

That's it, now you'll have a custom builder and you could use it just like this:
For creating new global state with asyncStorage integration:
const useLocale = createGlobalState('default', {
  config: {
    asyncStorageKey: 'locale',
  },
});

Inside your components:
const [locale, setLocale, { isAsyncStorageReady }] = useLocale();

return (<>
  <Text>{isAsyncStorageReady ? locale :  'Loading...'}</Text>
<>);

@jacargentina, thank you for reporting the issue with primitive data types. As you can see in the example, the situation has been addressed. Now, the global hooks allow you to force the update of the component, removing the necessity of using objects just to create a different memory reference.
Please let me know if there is anything else I could help.


Farming contract busted

pretty much is how it looks. Can constantly do +fc medium to change the fc i’m on. No clue if they’ll stack if i keep doing +fc medium.
Just thought i’d share this
note: havent tested with easy or hard. Also havent tested it on bso. Thank you

resolved


NimBLE: Can it be used with the v3.2.2 stable release? (IDFGH-1693)

Hello -
We've done a considerable amount of NimBLE testing using the feature/nimble_preview branch. NimBLE works quite well there and we would like to migrate to NimBLE in our projects. That said, for customer work we use the ESP-IDF v3.2.2 stable release branch, which we clone following the instructions provided in the Getting Started documentation:
cd ~/esp
git clone -b v3.2.2 --recursive https://github.com/espressif/esp-idf.git

Unfortunately for us, NimBLE is not available in this stable release. We did try a different method to download a v3.2.2 tag and found that NimBLE sources appear to be included:
cd ~/esp32
git clone --recursive https://github.com/espressif/esp-idf.git
cd esp-idf
git checkout v3.2.2
git submodule update

Comparing the two trees, it seems that the v3.2.2 checkout is essentially identical to the branch checkout, but adds new modules, including NimBLE. Is there a "safe" way to integrate NimBLE with the stable release branch? We prefer to use a stable branch that won't be updated by Espressif.
Regards,
Brian

@bfriedkin Ideally, neither release/v3.2 nor v3.2.2 tag should add NimBLE submodule (and hence sources) as this support has been added from 4.0 onwards. Can you please check if you see nimble folder as GIT controlled using  git status?

That said, for customer work we use the ESP-IDF v3.2.2 stable release branch,

What are the timelines for your customer release? Also, are you going to move to the next stable 3.x version (when released)?

@dhrishi -
I tried checking out the v3.2.2 tag again into a new location using the following commands:
cd ~/esp32
git clone --recursive https://github.com/espressif/esp-idf.git
cd esp-idf
git checkout v3.2.2
git submodule update --init

After the checkout I see nimble files in my ESP-IDF. For example:
Brians-MacBook-Air:src brianfriedkin$ pwd
/Users/brianfriedkin/esp32-nimble/esp-idf/components/bt/host/nimble/nimble/nimble/host/src
Brians-MacBook-Air:src brianfriedkin$ git log ble_gap.c
commit 936e538ffb14998326c45a32f2e5a32fa73b973b
Author: Hrishikesh Dhayagude<EMAIL_ADDRESS>Date:   Tue Jun 4 22:16:02 2019 +0800

    NimBLE-component: Add support to disable/deinit NimBLE host and port
...

How does this method for checking out the v3.2.2 version differ from the recommended git clone of the v3.2.2 branch? I see the nimble files in one but not the other. I can try building our BLE apps against this v3.2.2 version later this week to see if things work as expected.
As for our timeline, we completed our nimble integration a few months ago using the feature/nimble-preview branch. We are ready now to migrate to an ESP-IDF that includes nimble in a stable release. Performance seems good and nimble requires less RAM, which is important to us. We just updated our customer projects to 3.2.2 from 3.1. Jumping to 4.0 would be challenging, but we had looked briefly at 3.3 before settling on the 3.2.2 stable release.
Regards,
Brian

@bfriedkin Thanks for the overall feedback.
Shouldn't you be looking at:
/Users/brianfriedkin/esp32/esp-idf/
instead of
/Users/brianfriedkin/esp32-nimble/esp-idf/
You won't find NimBLE there :-)
I cannot assure you that NimBLE will be added in v3.2.2. Although, we will try to include it to a latest ESP-IDF stable release (something like 3.3.x). Again, this is not confirmed and I do not have concrete timelines for that.

@dhrishi -
Thank you for the follow. Sorry for the confusion. I created a esp32-nimble directory just to contain a fresh checkout of the v3.2.2 tag. When I build I rename that directory to esp32.
Getting back to my original question, I see NimBLE sources when I checkout the v3.2.2 tag but not the branch. I will try to build from the tag to see if it works. It looks like the 3.2.2 branch is a subset of the 3.2.2 tag. Because the 3.2.2 branch is a stable release and the 3.2.2 tag adds NimBLE, is it "safe" to assume that the tag is also stable but additionally includes the NimBLE component we require? Are the NimBLE sources different comparing what is included in the 3.2.2 tag to the 4.0 release(s)?
Good to know that NimBLE is targeted for the 4.x releases, but it could potentially be included in the next 3.3.x stable release. We would definitely appreciate that.
Regards,
Brian

@bfriedkin As I mentioned before, 3.2.2 tag won't add NimBLE as it has been added after that. I tried the steps as below:
git clone --recursive https://github.com/espressif/esp-idf.git
cd esp-idf
git checkout v3.2.2
git submodule update --init

After this, NimBLE sources will still be seen but they are not GIT controlled.

They will be seen as they were applicable when you first cloned the esp-idf (as by default it clones the master branch). git status will show components/bt/host/ as untracked, components/bt/host/nimble/nimble being its part.

git log components/bt/host/nimble/nimble/nimble/host/src/ble_gap.c in esp-idf folder won't give you any output. Doing git log inside the NimBLE component (as you did above) won't be the right thing as the submodule (part of master branch) will still show you the GIT history but it would be untracked for the current tag.

You can manually remove components/bt/host folder and see git diff. There won't be any diff

@dhrishi -
Thank you for taking the time to provide additional details. Now it makes sense to me.
Regards,
Brian

@bfriedkin

but it could potentially be included in the next 3.3.x stable release. We would definitely appreciate that.

I will let you know if (and when) this happens :-)

@bfriedkin We have ported NimBLE to v3.3. The release v3.3.1 should be out in a few weeks.
For the time being, you can use the latest release/v3.3 branch to test it out.

@dhrishi -
Excellent. Thank you for porting NimBLE to v3.3. Just to confirm, the code would be available and GIT controlled if we check out the branch as follows?
git clone -b v3.3 --recursive https://github.com/espressif/esp-idf.git

Thanks,
Brian

@bfriedkin Yes. That's right.
$  git clone -b release/v3.3 --recursive https://github.com/espressif/esp-idf.git
$ cd esp-idf
$ git submodule (You will see NimBLE submodule at components/nimble/nimble)
--
--
 8326807c5e580c3bb8ad13d1e80819aa0029004e components/nimble/nimble (remotes/origin/nimble-1.1.0-idf-v3.3)
--
--


wildignorecase is incompatible with autofs

Steps to reproduce

Set up autofs at e.g. /net. (Note: Specifically an "indirect" autofs root, the default kind that's used by the autofs daemon, not the "direct" kind provided by systemd.)
In indirect mode, the auto-mounted filesystems are children of the specified root (e.g. /net as an autofs produces /net/foo, /net/bar, and so forth), and by default they are not visible until accessed and mounted. (That's to avoid having ls /net trigger potentially dozens of mounts... and also because autofs supports a "wildcard" mount declaration, which naturally is impossible to list.)

Enable :set wildignorecase in Vim.

Attempt to tab-complete a path underneath a not-yet-mounted autofs location, e.g. ensure that ls /net does not list /net/ember (unmount if necessary), then attempt to :e /net/ember/home/grawity/.bash[tab][tab][tab]. The tab-completion does not return any results.

Expected behaviour
Vim attempts to list each directory from left to right (i.e. it lists / to find /net; then it lists /net to find /net/foo, then it gives up because that isn't visible yet.
Instead, Vim should either do a direct stat() of the final path, or direct stat() of each component, or something like that; i.e. assume that the previous components maybe were already specified in correct case, and only fall back to scanning directories if stat() find anything. Alternatively, listing each directory from right to left (instead of left-to-right) would also work, as accessing /net/foo/home/user would trigger the automount anyway.
Version of Vim
9.0.2121
Environment
Operating system: Linux
Logs and stack traces
No response

and it works with :set nowildignorecase?


Advanced Training Options - Optimization Metrics / Exclude algorithms

In the Model Buidler training tab, provide a dialog for "Advanced Training Options", similar to the existing "Advaced Data Options" in the data tab. In this dialog, a user should be able to:

Select which metric they want to optimize for related to the scenario they've chosen (i.e. Value Prediction = R-Squared, Data classification = Micro-accuracy)
Choose which algorithms to exclude from training

@zewditu - UI
@LittleLittleCloud - Backend

This issue is blocking #60 @luisquintanilla to provide design by EOW.

To-Do's
@luisquintanilla

[ ] Provide copy for each of the scenarios in the Trainers Tab.

@LittleLittleCloud

[ ] Provide list of trainers used for Data Classification and Value Prediction scenarios.
[ ] Confirm image classification uses the same metrics as classification.
[ ] Confirm forecasting metrics used are the same as regression (value prediction). Does forecasting use R-Squared as one of the optimization metrics?

@zewditu

[ ] Confirm whether Azure ML supported scenarios (image classification / object detection) allow for setting the evaluation metric.

Proposed Design

Copy
Optimizing Metric Tab

Note: For each of the scenarios, set the default to the metric being used today.

Heading: Choose the metric that will be used to find the best-performing model.
Subheading: When should I use each metric?
Data classification
Binary Classification

Note: This is determined based on whether the label column is boolean.

Accuracy - The closer to 1.00, the better.

The ratio of number of correct predictions to the total number of input samples.

Area under the curve (AUC) - The closer to 1.00, the better.

The area under the curve created by sweeping the true positive rate vs. the false positive rate.

Area under the curve of a Precision-Recall curve (AUCPR) - The closer to 1.00, the better.

Useful measure of success of prediction when the classes are imbalanced (highly skewed datasets).

F1-score - The closer to 1.00, the better.

It's the harmonic mean of the precision and recall.

Multiclass Classification

Micro-Accuracy - The closer to 1.00, the better.

Aggregates the contributions of all classes to compute the average metric. Doesn't take into account class membership.

Macro-Accuracy - The closer to 1.00, the better.

The average accuracy at the class level. Takes into account class membership.

Logarithmic loss (Log-Loss) - The closer to 0.00, the better.

The performance of a classification model where the prediction input is a probability value between 0.00 and 1.00.

Logarithmic loss reduction (Log-Loss Reduction) - Ranges from -inf and 1.00, where 1.00 is perfect predictions and 0.00 indicates mean predictions.

The advantage of the classifier over a random prediction.

Value prediction

R-Squared - The closer to 1.00, the better quality.

How close the actual data values are to the predicted values.

Mean Absolute Error (MAE) - The closer to 0.00, the better quality.

The average of all the model errors, where model error is the absolute distance between the predicted value and the actual value.

Mean Squared Error (MSE) - It is always non-negative, and values closer to 0.00 are better.

The squared average of all model errors, where model error is the absolute distance between the predicted value and the actual value.

Root Mean Squared Error (RMSE) - It is always non-negative, and values closer to 0.00 are better.

The squared root of the mean squared error of all model errors, where model error is the absolute distance between the predicted value and the actual value.

Image classification
Same as data classification. Disable for cloud scenario. Azure ML environment does not allow to specify metric.
Recommendation
Same as value prediction.
Object Detection
Disabled for now. Azure ML scenario does not allow to specify metric.
Forecasting
Same as value prediction.
Trainers Tab
Heading: Choose the trainers to explore during training.
Subheading: Which trainer should I use?
Data classification
Value prediction
Image classification
Disabled for now: ImageClassification and Azure ML are the only options depending on the environment (Local vs. Cloud).
Recommendation
Disabled for now. MatrixFactorization is the only option
Object Detection
Disabled for now. Azure ML is the only option.
Forecasting
Disabled for now. ForecastBySsa is the only option.

For  Image classification : Accuracy, Average Precision Score Weight, AUC weighted , normalized macro recall
OD: we only have one MeanAveragePrecision.

One thing want to confirm one thing ,  when we say " Image classification metrices are the same as data classification",  are we talking about the muti-classification  one?

One thing want to confirm one thing , when we say " Image classification metrices are the same as data classification", are we talking about the muti-classification one?

Good question. I think it's multiclass. @LittleLittleCloud do you know?

@LittleLittleCloud can you please take a look at the descriptions I provided for the trainers to make sure I accurately captured the main points.


nft origination error

Getting the following error trying to create a collection on ghostnet:
nft origination error {
"method": "GET",
"url": "https://rpc.ghostnet.teztnets.xyz/chains/main/blocks/head/context/constants",
"cause": {
"message": "request to https://rpc.ghostnet.teztnets.xyz/chains/main/blocks/head/context/constants failed, reason: getaddrinfo ENOTFOUND rpc.ghostnet.teztnets.xyz",
"type": "system",
"errno": "ENOTFOUND",
"code": "ENOTFOUND"
},
"name": "HttpRequestFailed",
"message": "GET https://rpc.ghostnet.teztnets.xyz/chains/main/blocks/head/context/constants FetchError: request to https://rpc.ghostnet.teztnets.xyz/chains/main/blocks/head/context/constants failed, reason: getaddrinfo ENOTFOUND rpc.ghostnet.teztnets.xyz"
}
GET https://rpc.ghostnet.teztnets.xyz/chains/main/blocks/head/context/constants FetchError: request to https://rpc.ghostnet.teztnets.xyz/chains/main/blocks/head/context/constants failed, reason: getaddrinfo ENOTFOUND rpc.ghostnet.teztnets.xyz

Most likely Tezos  node you are trying to connect is temporary unavailable.
Try to connect to a different node.

How do I change nodes with tznft? Using the set-network command doesn't seem to allow swapping ghostnet nodes.

How do I change nodes with tznft? Using the set-network command doesn't seem to allow swapping ghostnet nodes.

there is no CLI command, but you can manually edit generated tznft.json config file.
You need to either update "providerUrl" value for "testnet" json object or alternatively copy and rename "test" node and change "providerUrl".
tznft should be able to see new networks added to tznft.json file.

Worked great, thank you!


PackageReferenceRollbackException during AzureWebJobsStorage dependency configuration process

VS 2022 17.3.3
Connecting to the AI dependency was smooth, but when connecting to the storage account for AzureWebJobsStorage in the publish profile, it gives the following exception below. Clearing all Nuget caches under Tools => Options did not fix the issue.
.csproj:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <AzureFunctionsVersion>v4</AzureFunctionsVersion>
    <OutputType>Exe</OutputType>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.21.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.CosmosDB" Version="3.0.9" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.0.13" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.3.0" OutputItemType="Analyzer" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.8.0" />
  </ItemGroup>
  <ItemGroup>
    <None Update="host.json">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </None>
    <None Update="local.settings.json">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
      <CopyToPublishDirectory>Never</CopyToPublishDirectory>
    </None>
  </ItemGroup>
</Project>

Connecting to Azure Storage dependency storage1 in the project...
Adding AzureWebJobsStorage to store AzureAppSettings...
Adding AzureWebJobsStorage:blob to store AzureAppSettings...
Adding AzureWebJobsStorage:queue to store AzureAppSettings...
Adding permissions for app service...
Ensuring the app service has permissions to access resource 'xxxxxxxxxxxxxxxxeastus'...
Installing NuGet packages to project...
Installing package 'Azure.Storage.Blobs' with version '12.3.0'.
ErrorNuGet.PackageManagement.PackageReferenceRollbackException: Package restore failed. Rolling back package changes for 'API.Providers'.
at NuGet.PackageManagement.NuGetPackageManager.d__89.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.PackageManagement.NuGetPackageManager.d__86.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.PackageManagement.NuGetPackageManager.d__53.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.PackageManagement.NuGetPackageManager.d__52.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.VisualStudio.Implementation.Extensibility.VsPackageInstaller.d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at NuGet.VisualStudio.Implementation.Extensibility.VsPackageInstaller.d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at NuGet.VisualStudio.Implementation.Extensibility.VsPackageInstaller.d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
at NuGet.VisualStudio.Implementation.Extensibility.VsPackageInstaller.InstallPackage(String source, Project project, String packageId, String version, Boolean ignoreDependencies)
at Microsoft.WebTools.Shared.VS.NuGet.NuGetPackageManager.d__42.MoveNext()
ErrorFailed to configure NuGet packages.
ErrorFailed to configure dependency Azure Storage storage1.

Progress... manually adding the azure storage nuget packages allowed adding of the storage service dependency:
  <ItemGroup>
    <PackageReference Include="Microsoft.Extensions.Azure" Version="1.0.0" />
    <PackageReference Include="Azure.Storage.Blobs" Version="12.13.1" />
    <PackageReference Include="Azure.Storage.Files.Shares" Version="12.11.0" />
    <PackageReference Include="Azure.Storage.Queues" Version="12.11.1" />
    <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.21.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.CosmosDB" Version="3.0.9" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.0.13" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.3.0" OutputItemType="Analyzer" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.8.0" />
  </ItemGroup>

However, now publishing the consumption func app to Azure fails with:

Publish has encountered an error.
Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.
A diagnostic log has been written to the following location:
"C:\Users...\AppData\Local\Temp\tmpB14D.tmp"

Content of diagnostic log:

8/30/2022 10:00:24 PM
System.AggregateException: One or more errors occurred. ---> Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.
--- End of inner exception stack trace ---
---> (Inner Exception #0) Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. <---
Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.
===================

Content of output log:

The attempt to publish the ZIP file through https://xxx.scm.azurewebsites.net/api/zipdeploy failed with HTTP status code Unauthorized

Following this suggestion to delete/recreate the publish profile and restarting the func app solved the issue.
Leaving this here in case someone falls down this rabbit hole ...


Plotting crashes RTVS when Plot Window is not initially visible

Repro steps:

Open RTVS
Ensure that Plot window is not visible or active (i.e., it can be in a tab that is not at the forefront)

Get this result:

This is a dupe of #2375.


ServiceWorker does not allow 'file://' origin

I am trying to intercept image load request from my HTML to https requests. Specifically my app has a URL "images/test.png" in the HTML and electron tries to load that with a file scheme  "file:///images/test.png". I would like to rewrite this request to https://mydomain.com/images/test.png
For this I was trying to use a service worker since they allow to intercept the network requests and modify the URL.
The problem is that electron (well chromium) does not allow "file://" origin. Chromium states that Service Workers require a secure origin, such as HTTPS.
The exact error is:
"Failed to register a ServiceWorker: The URL protocol of the current origin ('file://') is not supported."
Is there a way to get around that with electron?
A somewhat related Chromium submit is https://codereview.chromium.org/1191793003/#ps40001

We can provide a webFrame.registerURLSchemeAsAllowingServiceWorkers API for this.

It seems as if many Chrome APIs are moving to HTTPS-only, it'd be great to have a single "registerURLSchemeAsPrivileged" method to encompass all of these features instead of having to one-off all of them

It seems as if many Chrome APIs are moving to HTTPS-only, it'd be great to have a single "registerURLSchemeAsPrivileged" method to encompass all of these features instead of having to one-off all of them

:+1:

registerURLSchemeAsPrivileged sounds good, but should it allow file and like scheme or we can just allow custom schemes which are registered as standard ? Otherwise will file like schemes elevated as privileged lead to origin issues ?

@deepak1556 A simpe wrapper around blink APIs should be enough, we don't need to make the API do too much things unless it is proven that we have to.

Thanks. So until we have this new API Service Workers cannot be used since only https is supported by Chrome, correct? Service a worker via https on a web server won't work either due to cross origin.

Any updates here?
Currently I receiving this error on the console, if I try to register a service worker from a filepath: error when registering sw DOMException: Failed to register a ServiceWorker: A bad HTTP response code (-1) was received when fetching the script.
I tried to register the file protocol at every method, but still no luck so far
electron.webFrame.registerURLSchemeAsPrivileged('file');
electron.webFrame.registerURLSchemeAsSecure('file');
electron.webFrame.registerURLSchemeAsBypassingCSP('file');

app.on('ready', () => {
    electron.protocol.registerServiceWorkerSchemes(['file:']);
});

Has anybody been able to successfully register a service worker via file:///?

@PhilJ 'file' scheme has been registered to enable service worker by default from v0.36.0 . which version of electron are you on ?
Have verified working with https://github.com/GoogleChrome/samples/tree/gh-pages/service-worker . Could you provide sample app in case it doesn't work for you, thanks!

Thanks for your response and the test case. I'm using Electron 0.36.1, so the file protocol should be supported for service workers.
I reduced the problem to the simple registration of an service worker and it still fails on my machine, even though it is fully covered by your test case. sw.js exists under this path (when i copy the path from the error to a browser instance the file is loaded). However this is not relevant for the error, it does not change if I remove the worker file.
// client/index.html
<script>
navigator.serviceWorker.register('sw.js', {scope: './'})
.then(function () {
  console.log('sw registered')
})
.catch(function (error) {
  console.log('error when registering sw', error)
});
</script>

// client/sw.js
self.addEventListener('fetch', function (event) {
  console.log(event);
});

// main.js
app.on('ready', () => {
    mainWindow = new BrowserWindow({ width: 1200, height: 1000 });
    mainWindow.loadURL(`file://${__dirname}/client/index.html`);
});

On the console I receive an error, that the registration failed. The network monitor shows a strange error, I guess the browser must have somehow blocked the request.

Any idea what could be different about my environment, that causes this behaviour?

@PhilJ could you try clearing sw storage data using session.clearStorageData and retry.

@deepak1556 I also have this kind of problem with 0.36.0. Also reported issue #3897

@deepak1556 after session.clearStorageDate I have the same message:

Failed to register a ServiceWorker: No URL is associated with the caller's document

@PhilJ In my case the problem was in the old version of electron-prebuilt

The problem for me was caused by electron-compile, which still suffers by that issue. I'm now using gulp for build an service workers work like a charm now.

The problem for me was caused by electron-compile, which still suffers by that issue.

Can you file a bug for this?

Maybe replacing request.url could be a solution (temporary)?
var request = new Request(urlWithCacheBusting,               {credentials: 'same-origin'});  request.url = urlWithCacheBusting.replace(/file:\/\/\/(.*):\//, '');


MeSH Voting Working, Updated Selenium Testing

Somehow this also includes Neel's Pull Request. It also works without updating backend functionality.

Awesome. I want to merge this, but I don't want to merge in the statistical features yet. If there's a way to separate the UI change into a separate request, we can merge that, or we can just wait for a bit until this statistics feature is finished.

Hey, I'd highly, highly recommend that you put some of these commits in a separate pull request, or else this is likely going to take a long time to review.

Gotchu, right now, I'm just running through some trials to see what lets SauceLabs make this work. When it's ready to merge, I'll set up another PR.


BUG: Browser Compatibility

Live Website WebUnconfID its not working on Firefox (Teste by Me)
firefox version : 61.0.1 (64-bit) (Linux | Ubuntu)

@ri7nz Firefox need to flag web component on Firefox. related with #44
Check https://caniuse.com/#feat=custom-elementsv1

@tyohan  thank you so much. This is the issue can be closed


Detect shady links

My idea of this task is to implement a new warning responsible of detecting shady links in Literals. I have been inspired by one of the detection of guarddog from DataDog.
They use the following RegEx:
(http[s]?:\/\/.*\.(link|xyz|tk|ml|ga|cf|gq|pw|top|club|mw|bd|ke|am|sbs|date|quest|cd|bid|cd|ws|icu|cam|uno|email|stream)\/)
Maybe we need to conduct additional research on the subject (maybe there is some study we may want to read to improve the detection?).

A .json with a list of unsafe domain: https://hole.cert.pl/domains/domains.json (not really related to the subject but it's interesting).


DECIMAL TO BINARY CONVERSION USING STACK IN C (GSSOC'21)

DECIMAL TO BINARY CONVERSION USING STACK IN C
🚀 Feature
Have you read the Contributing Guidelines on Pull Requests?
Yes !
AIM :: DECIMAL TO BINARY CONVERSION USING STACK IN C
Motivation
As i didn't found DECIMAL TO BINARY CONVERSION USING STACK IN C, So i am willing to contribute it...
Pitch
Hi I am GSSoC'21 participant,
"I am looking to work on the DECIMAL TO BINARY CONVERSION USING STACK IN C"
I will write the clean and optimized code , by keeping best case time and space complexity in mind and
I will use C language.

/assign


Mldb 2150 fetcher http return error

Let me look at it properly before merging please

@jeremybarnes I made some changes. Please rereview.


Issues building afl-clang-fast with llvm 4.0.0

In my attempted runs of aflgo, I've either gotten tripped up at one of two places, building afl-clang-fast in aflgo/llvm_mode or building the sample project. I've attempted to go through the guide with clang 4.0/4.1/8.0 all with the gold plugin build turned on and pointed at ld.gold. In my experience when running clang 4, I get an error (shown below). If I run with clang4.1 it builds, but then it refuses to build the example project. If I build with 8.0, everything seems to work but there are no results from the CFG extraction and no function targets. (I also tried running the example on a different program with the 8.0 build I wasn't having results there either.)
So my questions are, do you know how I can fix the aflgo/llvm_mode with	clang 4.0, and if not, should this project be able to work with clang 8?
Thanks
Stack dump:
0.      Program arguments: /home/kisamefishfry/llvm4/llvm-project-llvmorg-4.0.0/build/bin/clang-4.0 -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -disable-free -main-file-name test-instr.c -mrelocation-model static -mthread-model posix -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -momit-leaf-frame-pointer -dwarf-column-info -debug-info-kind=limited -dwarf-version=4 -debugger-tuning=gdb -resource-dir /home/kisamefishfry/llvm4/llvm-project-llvmorg-4.0.0/build/bin/../lib/clang/4.0.0 -D _FORTIFY_SOURCE=2 -D AFL_PATH="/usr/local/lib/afl" -D BIN_PATH="/usr/local/bin" -D VERSION="2.52b" -D __AFL_HAVE_MANUAL_CONTROL=1 -D __AFL_COMPILER=1 -D FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION=1 -D __AFL_LOOP(_A)=({ static volatile char *_B __attribute__((used));  _B = (char*)"##SIG_AFL_PERSISTENT##"; __attribute__((visibility("default"))) int _L(unsigned int) __asm__("__afl_persistent_loop"); _L(_A); }) -D __AFL_INIT()=do { static volatile char *_A __attribute__((used));  _A = (char*)"##SIG_AFL_DEFER_FORKSRV##"; __attribute__((visibility("default"))) void _I(void) __asm__("__afl_manual_init"); _I(); } while (0) -internal-isystem /usr/local/include -internal-isystem /home/kisamefishfry/llvm4/llvm-project-llvmorg-4.0.0/build/bin/../lib/clang/4.0.0/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -O3 -Wall -Wno-pointer-sign -fdebug-compilation-dir /home/kisamefishfry/Documents/Research/aflgo/llvm_mode -ferror-limit 19 -fmessage-length 120 -funroll-loops -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -load ../afl-llvm-pass.so -o /tmp/test-instr-37dd8a.o -x c ../test-instr.c
clang-4.0: error: unable to execute command: Segmentation fault (core dumped)
clang-4.0: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 4.0.0
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin
clang-4.0: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
clang-4.0: error: unable to execute command: Segmentation fault (core dumped)
clang-4.0: note: diagnostic msg: Error generating preprocessed source(s).
Makefile:98: recipe for target 'test_build' failed
make: *** [test_build] Error 254```

Hi @pattersonz,
Can you provide me some information about your tested program and the targets so that I can try to run AFLGo on my laptop? I did not try AFLGo with clang 8.0, but it seems that AFLGo works stably with clang 4.0.0.
Best.

@strongcourage ,
Yes, so this error is actually occurring on:

cd llvm_mode
make clean all

In step 3 of "How to instrument a Binary with AFLGo" The above text that I shared was the end of the output from the console. We would prefer to get this working with clang-4.0 if possible.

I see, so you cannot run make clean all in /llvm_mode and it failed the run the simple program test-instr.c.
It is probably due to this commit: https://github.com/aflgo/aflgo/commit/0f18be9fef2348aea81ee35d0bdd371dc1db9633
You can revert to the original Makefile, and check again.

So, I did get a new error, this was the output:
rm -f *.o *.so *~ a.out core core.[1-9][0-9]* test-instr .test-instr0 .test-instr1
rm -f ../afl-clang-fast ../afl-llvm-pass.so ../afl-llvm-rt.o ../afl-llvm-rt-32.o ../afl-llvm-rt-64.o ../afl-clang-fast++
[*] Checking for working 'llvm-config'...
[*] Checking for working 'clang'...
[*] Checking for '../afl-showmap'...
[+] All set and ready to build.
clang -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DVERSION=\"2.52b\"  afl-clang-fast.c -o ../afl-clang-fast
ln -sf afl-clang-fast ../afl-clang-fast++
clang++ `llvm-config --cxxflags` -Wl,-znodelete -fno-rtti -fpic -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DVERSION=\"2.52b\" -Wno-variadic-macros -shared afl-llvm-pass.so.cc -o ../afl-llvm-pass.so `llvm-config --ldflags`
afl-llvm-pass.so.cc:269:9: error: unknown type name 'TerminatorInst'
        TerminatorInst *TI = BB.getTerminator();
        ^
afl-llvm-pass.so.cc:428:11: error: unknown type name 'TerminatorInst'
          TerminatorInst *TI = BB.getTerminator();
          ^
2 errors generated.
Makefile:84: recipe for target '../afl-llvm-pass.so' failed
make: *** [../afl-llvm-pass.so] Error 1

As discussed in https://github.com/aflgo/aflgo/issues/40, you could try LLVM 4.0.1. But it works fine on my machine Ubuntu 16.04 with LLVM 4.0.0. You couild follow the build instruction to install LLVM/clang.
$ ./afl-clang-fast --version
aflgo-compiler (yeah!) 2.52b
clang version 4.0.0 (tags/RELEASE_400/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin

Sorry, I misread your advice, after reverting the Makefile to the original, I am still getting the same console output.

So, I was able to get around this issue on a different machine, so it must be some messed up environmental things on my side.


pull in related models

I would like to pull in related models.
$users = Searchy::users('id', 'name', 'email')->with('profile')->query($q)->get();
// or
$users = Searchy::users('id', 'name', 'email')->query($q)->get();
$users->load('profile');

Do you mean to map it to an Eloquent Model? If so, see 8566a0 and let me know if that solves your problem.


Errors don't change on editing the file

Errors only show up when loading vscode for the first time. Consequent editing of the file doesn't seem to update the diagnostic info.
On opening vscode

On fixing the issue (expecting it to show the next error which is unused params)

Do you have running bsb -w process?

Yes. bsb from my node_modules is running

I had the same problem with vim-rescript (which uses rescript-vscode internally). In both those cases I get a prompt to start build after which I see a bsb process running in the background.
Version: 1.0.0

Hello! Which bs-platform version?

bs-platform: 8.3.3

Can you show me your lib/bs/.compiler.log?

lib/bs/.compiler.log
#Start(1607195542405)
#Done(1607195542441)

Thanks. And I'm assuming you can repro this deterministically?

I creates a blank (bs-platform + gentype) project with 1 rescript file and the plugin worked. But then I created a new angular project with ng new testproj and the issue showed up again. It seems to be running into issues with angular or maybe typescript dependencies.

Not sure what you mean; our plugin doesn't work on angular files?

I meant rescript file inside an angular project

I've pushed a fresh angular project with one rescript file src/File.res that I could reproduce the issue with. The repo is at phenax/bug-repro-rescript-vscode

Screenshots from vscode
Valid error

After fixing the issue

Screenshots from nvim (rescript-lang/vim-rescript with coc)
Valid error

After fixing the issue

I have the same issue with plain Rescript (created with --theme node). Compiler log does show the error but VSCode does not.

@marcoemrich did you save the file?
I think I read somewhere the language server only works on saved files.

Yes - I use "save on focus lost", but also did save manually

and have configured "format on save" - this was in the readme

interestingly - the formatting part works!

I can confirm that the initial error shows up in the Problem tab if the file has errors when you open it but not subsequent errors. Nor does the initial error clear out when you fix the problem. The lib/bs/.compiler.log is correct at every step--it's just not being reflected via the rescripts-vscode extension. Everything works correctly if I just use bsb -w in a terminal window.

@phenax I just pulled your project locally and can't reproduce:

git clone your example project
npm install
bsb -make-world -w in one terminal
ng serve in another terminal

The errors in VSCode seem to update? Did you follow any other steps?

@IwanKaramazow. Pretty much the same steps except for the last one. I cloned the repo, ran npm install then opened the project directly. It prompted me to start the build which I clicked on.

Ok, what OS are you using? Did you open the project in the root of the folder?

@phenax thanks, just as a debug point running bsb -w in the terminal before you open vscode gives the same thing?

Yes. It behaves the same way.

@phenax We released a new version (1.0.4) that contains a fix. Can you confirm that this solves your issue?

@phenax We released a new version (1.0.4) that contains a fix. Can you confirm that this solves your issue?

I am not sure if this is the same problem, but Problems window get out-of-sync with compiler from time to time. VS Code restart helps.
Here what Problems window shows for me:

This is what terminal output is:

and this is what compiler log is:
#Start(1614116066457)

  Warning number 21
  /home/misha/projects/productionmason/web/packages/shared/tests/Exn_Test.res:24:7-9

  22 ┆     }
  23 ┆   `)
  24 ┆   c()
  25 ┆   None
  26 ┆ } catch {

  this statement never returns (or has an unsound type.)

  We've found a bug for you!
  /home/misha/projects/productionmason/web/packages/shared/src/commands/OrderCommands.res:26:3

  24 ┆ let a = t.apolloClient.mutate(~mutation=module(OrderCommands_Graphql.C
       reateConversation), ())
  25 ┆
  26 ┆ a->AsyncResult.mapOk(x => {
  27 ┆   Ok(x.data.insert_conversations_one->Option.getExn->OrderCommands_Gra
       phql.Conversation.toDomain)
  28 ┆ })

  This has type:
    Js.Promise.t<
  Belt.Result.t<
    ApolloClient__Core_ApolloClient.FetchResult.t__ok<
      Schema.OrderCommands_Graphql.CreateConversation.t,
    >,
    ApolloClient__Core_ApolloClient.ApolloError.t,
  >,
>
      (defined as
      Js_promise.t<
  Belt.Result.t<
    ApolloClient__Core_ApolloClient.FetchResult.t__ok<
      Schema.OrderCommands_Graphql.CreateConversation.t,
    >,
    ApolloClient__Core_ApolloClient.ApolloError.t,
  >,
>)
  Somewhere wanted:
    CommonBase.AsyncResult.t<'a, [> #Exn(exn)] as 'b> (defined as
      Promise.t<CommonBase.AsyncResult.result<'a, 'b>>)

#Done(1614116066469)

This was a while ago. Please reopen if still valid.


Fix: Fix case when a derived property changes the dependent properties are not logged in the debugger

Description
For e.g when a Text widget's text property has {{Datepicker1.selectedDate}} and if the date is changed in the datepicker, the debugger logs where not showing the value of Text.text(as this is depending on Datepicker1.selectedDate this should have been logged.)
Related to  #4760
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Jest test case
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
// Code coverage diff between base branch:release and head branch: fix/log-deps

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
app/client/src/components/editorComponents/Debugger/helpers.tsx
81.48 (0.35)
80 (2.22)
38.46 (0)
82.61 (0.39)

/ok-to-test sha=eb55cb9

/ok-to-test sha=be490e3


WebApp:az webapp deployment source config-local-git

Try this command:
##The webappName exist
$webappname=mywebappName
echo Git deployment URL: $(az webapp deployment source config-local-git --name $webappname --resource-group AzureTutorial --slot staging --query url --output tsv)
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp deployment source config-local-git
Errors:
The command failed with an unexpected error. Here is the traceback:
Unable to build a model: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get', DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
    found_value = key_extractor(attr, attr_desc, data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
    return attribute_key_case_insensitive_extractor(key, None, working_data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
    return data.get(found_key)
AttributeError: 'str' object has no attribute 'get'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 620, in body
    data = deserializer._deserialize(data_type, data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1446, in _deserialize
    raise_with_traceback(DeserializationError, msg, err)
  File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
    raise error.with_traceback(exc_traceback)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
    found_value = key_extractor(attr, attr_desc, data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
    return attribute_key_case_insensitive_extractor(key, None, working_data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
    return data.get(found_key)
msrest.exceptions.DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 1653, in enable_local_git
    site_config, slot)
  File "/opt/az/lib/python3.6/site-packages/azure/mgmt/web/v2020_09_01/operations/_web_apps_operations.py", line 14662, in create_or_update_configuration_slot
    body_content = self._serialize.body(site_config, 'SiteConfigResource')
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 623, in body
    SerializationError, "Unable to build a model: "+str(err), err)
  File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
    raise error.with_traceback(exc_traceback)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 620, in body
    data = deserializer._deserialize(data_type, data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1446, in _deserialize
    raise_with_traceback(DeserializationError, msg, err)
  File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
    raise error.with_traceback(exc_traceback)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
    found_value = key_extractor(attr, attr_desc, data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
    return attribute_key_case_insensitive_extractor(key, None, working_data)
  File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
    return data.get(found_key)
msrest.exceptions.SerializationError: Unable to build a model: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get', DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp deployment source config-local-git --name {} --resource-group {} --slot {} --query {} --output {}

Expected Behavior
Environment Summary
Linux-5.4.0-1047-azure-x86_64-with-debian-10.2 (Cloud Shell)
Python 3.6.10
Installer: DEB

azure-cli 2.23.0

Extensions:
ai-examples 0.2.5
ssh 0.1.5

Additional Context

route to service team

@panchagnula . looks like this is similar issue as #18075 . It is Deserialization failure for SiteConfigResource model. here is the code block for the same.
I think this is a breaking change form SDK update.


Source tarball missing on pypi for 0.3.1

I'm not sure whether it's intentional, but the last source tarball on pypi is 0.3.0 - could you add one for 0.3.1 as well please?

This was intentional, but I uploaded a source tarball now. Just curious, why a source tarball?

Thank you!
I've created a spack package for it (one of our packages depends on it, other people might find it useful too) and they generally prefer source tarballs. Now I can add 0.3.1 as well.


Warm start solution silently discarded when has_int=false

ref https://github.com/JuliaOpt/CPLEX.jl/pull/114

Closing since we won't be fixing this. The new MOI wrapper caches warm-starts and adds them immediately prior to optimize.


Display dappUrl instead of url when the live app is dapp

📝 Description
Display dappUrl instead of url when the live app is dapp.
❓ Context

Impacted projects: ledger-live-desktop
Linked resource(s): ``

✅ Checklist

[ ] Test coverage
[ ] Atomic delivery
[ ] No breaking changes

📸 Demo

Check POAP url for example.

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Seems the Library tests also failed on develop. So not related to this PR.
https://github.com/LedgerHQ/ledger-live/runs/14432379285