generator seems to be memory leak(tf.1.3 keras:2.0.9)

I'm training large image data set(3608930, 244 x 244)  for InceptionResNetV2 or Xception by using ft_generator or sequence.
I use multi_gpu_model(5 gpu). So I make batch_size 45gpuNum. Batch Memory 2442443 4byte  455 = about 153M.
As trainging goes by, memory monotonically increases by about 15 M like below.
Why 15M( 10% of 150M) monotonically increase? 15*55522= about 821 G. So I can't train  data fully. But using datagen.flow_from_directory don't increase. Why?  My generator has problem?
Any ideas welcome.
On each batch, memory increase by about 15N
734/55522 [..............................] - ETA: 53:06:05 - loss: 1.7416 - categorical_accuracy: 0.6141   67215272
735/55522 [..............................] - ETA: 53:06:01 - loss: 1.7416 - categorical_accuracy: 0.6140   67233632
736/55522 [..............................] - ETA: 53:05:58 - loss: 1.7408 - categorical_accuracy: 0.6142   67253048
737/55522 [..............................] - ETA: 53:05:56 - loss: 1.7399 - categorical_accuracy: 0.6144   67268764
738/55522 [..............................] - ETA: 53:05:52 - loss: 1.7397 - categorical_accuracy: 0.6145   67285804
Below is fit_generator
class MemoryCallback(Callback):
    def on_batch_end(self, epoch, log={}):
        print("  ",resource.getrusage(resource.RUSAGE_SELF).ru_maxrss)

parallel_model.fit_generator(generator=myGenerator(trainIndex),steps_per_epoch=int(len(trainIndex)/(batch_size))
                             ,epochs=5 ,verbose=1
                    ,callbacks=[cSVLogger,checkpointer,MemoryCallback]
                             ,validation_data=myTestGenerator(testIndex),validation_steps=int(len(testIndex)/(batch_size))
                             ,class_weight=classWeight
                    ,initial_epoch=0
                    ,max_queue_size=1
                    ,shuffle=False
                    ,workers=1
                   )

Below is my generator. inputValue is image list.
@threadsafe_generator
def myGenerator(trainIndex):
    cnt=0
    ckValue=int(len(trainIndex)/(batch_size))
    while 1:
        for idx,x in enumerate(range(ckValue)):
            returnA=[]
            returnB=[]

            for y in trainIndex[idx*batch_size:(idx+1)*batch_size]:
                returnA.append(img_to_array(inputValue[y])/255)

                categoryOne=[0]*len(word2IntClassValue)
                categoryOne[word2IntClassValue[lableValue[y]]]=1
                returnB.append(categoryOne)

            yield np.array(returnA),np.array(returnB)
            returnA=[]
            returnB=[]

I assume the MemoryCallback returns the RAM utilization on this machine. Do you actually run out of memory when you train with the whole dataset or you estimate that you will crush due to the increase?
At first glance I don't see something that could cause a memory leak in your generator. Keep in mind that garbage collection can be an expensive process and might be delayed if you have lots of memory in your system. If you don't experience any out-of-memory issues don't worry about it as the GC is likely to cleanup the memory at one point. Alternatively you can try calling manually the gc.collect(). Most of the times this practice is discouraged but in few cases it might be helpful.
If you have more time to invest on this, you can also rewrite the generator to avoid allocating so much memory every time. This can be done by preallocating the memory out side of the loop (assuming fixed batch sizes that might not be the case; still possible with extra efford). I also assume that the pasted code is a simplified snippet and that in your actual implementation you handle concurrency safely.

Thanks for your comment.
But Actually I crushed due to memory problem. I use AWS p2. 8xlarge. And fit_generator start with 80G, but as train goes by, batch 2974/7152's memory 378G. And gc is not helpful in this situation.
But I'll try your opinion that preallocating memory. Thanks


Typo or extra word

Looks like the "and" is not needed for this sentence from this page ( or something is missing after the and):
The Get connected sample app for Microsoft Teams provides a simple way to connect and with people in your organization with similar skills.

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

ID: dc9f873e-6664-108b-4183-6e931cd42678
Version Independent ID: 01593f9a-1ecb-a451-ceff-7f8a094eae27
Content: Get connected sample app (preview) - Power Apps
Content Source: powerapps-docs/teams/get-connected.md
Service: powerapps
GitHub Login: @msftsamperl
Microsoft Alias: saperlmu

Thanks for your comment, @steve-parker-by. This issue has been assigned to the doc author for review.

Thank you for your feedback. Documentation has been fixed, and the changes will be visible soon.


Various quality of life improvements

When working on this project I noticed that I spend way too much time setting up the development environment and fixing code style issues.
To improve the workflow i propose the following changes:

Adding a .editorconfig file to ensure consistency across all IDEs
Adding a .gitpod.yml config file to allow quickly starting a ready-to-use dev environment

Great work!


Add pluggy to install_requires and move pytest to tests_require

Per the discussion in https://github.com/riscv-software-src/riscv-isac/issues/64. The last commit also puts requirements.txt in alphabetical order, though that will also confuse git blame and merges past this point; feel free to take it or not.

Will require an update to the changelog to merge this.

@neelgala Sure, here you go. Sorry I missed the changelog comment—do I need to write anything?


gulp based ng2 starters

Hey,
I tried but I am not working with gulp\systems.js as you do
can you create a simple branch for https://github.com/pkozlowski-opensource/ng2-play
with ng2-translate working?
I was thinking about branches with one commit, one branch per module
because usage of ng2-modules will produce a lot of questions :)
like this: https://github.com/valor-software/ng2-bootstrap/issues/18

Ok so I had a hard time trying to figure out what was the problem, and it's just that ng2-play uses an old SystemJS version that has a bug where the defaultExtension doesn't work in subfolders: https://github.com/systemjs/systemjs/issues/805
Anyway, once I updated this and switched from system-csp-production to system.src (that can load all types of modules, not just systemjs modules), it worked easily: https://github.com/ocombe/ng2-play/tree/ng2-translate-test

Awesome :+1:


What happened?

Is this dead? Should I fork?

Has emoji 15.1 been implemented?

Silence.

@Secret-chest I see that you have forked this repo. Are you actively maintaining it?

No. I want to see if there's something.

@Secret-chest Very well. Thanks for letting me know!

@Secret-chest Very well. Thanks for letting me know!

I might start maintaining because I'm making a Linux distro and none of the emoji fonts looks nice enough.

I might start maintaining because I'm making a Linux distro and none of the emoji fonts looks nice enough.

Please do! I would love to have an updated version of this emoji set to use on Android!

I will when I have time.

Great! I'll be on the lookout for it! 😁

When I can, not now. Would you mind if I replace smiley emoji with the Android 6 version, or do I maintain two branches?

When I can, not now. Would you mind if I replace smiley emoji with the Android 6 version, or do I maintain two branches?

I would not mind, the different poses made the blobs extra expressive.

When I can, not now. Would you mind if I replace smiley emoji with the Android 6 version, or do I maintain two branches?

Yup! No problem! I understand life gets busy sometimes. I'm cool with bringing back the Android 6 version!

Add Unicode 16.0

I will try

Understand I'm busy, though

Used pleading face to eyebags

Used pleading face to eyebags

i made mine, check issues.


Removes Export to CSV button

https://www.hawaii.edu/jira/browse/GROUPINGS-1089
Groupings-1089
Test Checklist

[x ] Unit Tests Passed:
[x ] Jasmine Tests Passed:
[x ] General Visual Inspection:

I think we should be careful to make sure that the export to csv is not needed before removing it. In terms of code this is fine.

This should be fine as the export to csv button is still present on the application, just not in modal so it does not fully remove the functionalities of exporting to csv format. This ticket seemed to have just been on visuals mismatching on both branches.


go fmt provider json format

In many case, we want to print data infomation in json format. For simplicity, can fmt provide json format verb?

Go fmt formats go code as source code. What is the value of emitting the go ast as json? What problem would that allow you to solve?

@davecheney I think he ment the fmt package and wnats something like fmt.Printf("%json", v)
That does something like:
b, err := json.Marshal(v)
if err != nil {
	fmt.Println("error:", err)
}
fmt.Printf("%s", string(b))


Fix animation player crashing when caching disabled tracks

A misplaced vector write was causing a crash when iterating the node_cache of an animation when at least one of the tracks is disabled.
This fixes #62487

Thanks!


Error on Predicting on Single Date

Trying to Predict FINRL on a single date errors out with "Length mismatch: Expected axis has 0 elements, new values have 1 elements". For example : if trade date is between 2022-05-02 and 2022-05-02, i.e trying to predict outcome for 2nd of May errors out with the above error.

Which notebook are you using? Is it minute level trading data?

Which notebook are you using? Is it minute-level trading data?

It is not minute level data it is day data, I have been using the steps provided in the "FinRL_StockTrading_NeurIPS_2018.iynb" but with a custom made stock list. Same parameters and the PPO algorithm from stablebaselines3


TickTime can only format datetime64[ns], not other scales

>>> int(np.datetime64("now", "ns"))
1531768357000000000
>>> int(np.datetime64("now", "us"))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: int() argument must be a string, a bytes-like object or a number, not 'datetime.datetime'

This breaks TickTime's tp_call(), which can't convert such arguments.

Also, unit tests are wholly inadequate.


Bot cannot send offer when a weapon include in the payment.

The bot cannot send trade offer when a 0.05/weapon include in the payment,
For example, my bot listed a robot part for 1.05, he couldn't send the offer, only for parity numbers of robots part and then weapons won't be included on the trade.

Yes I know I am big sorry - the bot can't send offers with weapons


Fix punctuations

Fixes #28228
Context

Contributor Checklist

[x] Review Contribution Guidelines.
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@helfese, can you make the same changes to notes-template.md for this PR to be merged. Our system needs the files to be in sync.

Template updated in: https://github.com/gradle/gradle/pull/28321/

Try to update the branch, as the GHA pipeline was broken, and the fixes were not merged.

The merge queue build has started. Click here to see all failures if any.


Snakecase helper adds an unwanted _ at the start

When a string start with an Upper char the snakecase helper adds an unwanted _ in the beggining, it should just replace by the lower char
current:
"HelloWorld" -> "_hello_world"
desired:
"HelloWorld" -> "hello_world"

https://github.com/Web3-Builders-Alliance/soda/blob/6d1c6b53f4235a4f7915d8a364744c83a4dbf7e8/crate/src/helpers.rs#L5

fixes #133


Papers on Cultural Evolution and LLMs

Hello,
We've been working on papers related to cultural evolution, and I thought they might be of interest to those studying the intersection of culture and LLMs. You can find our work here: Cultural evolution in populations of Large Language Models, When LLMs Play the Telephone Game.
However, I’m not sure if we’re using the term "culture" in the same way !
Thanks for the cool repo anyway (:

Thank you for bringing this up! I’m currently working on the newer version of this repository, and I will definitely check out your paper and include it where relevant. Appreciate your contribution and insights!


Allow kvm storage plugin to customize diskdef, add geometry

Description
This PR allows KVM storage plugin an opportunity to customize the libvirt disk XML.
The new interface method customizeLibvirtDiskDef facilitates plugin-specific config without having to add new methods for each specific thing that may need customizing. Existing plugins should be unaffected because of default implementation in interface.
Additionally, this adds the capability to define geometry in the libvirt disk definition.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9051

@blueorangutan test

@sureshanaparti a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-9591)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 59451 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8839-t9591-kvm-centos7.zip
Smoke tests completed. 126 look OK, 3 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_attach_and_distribute_multiple_volumes
Failure
37.68
test_attach_multiple_volumes.py

test_01_verify_ipv6_vpc
Error
680.82
test_vpc_ipv6.py

test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL
Failure
631.02
test_vpc_redundant.py

test_02_redundant_VPC_default_routes
Failure
1510.79
test_vpc_redundant.py

test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers
Failure
481.93
test_vpc_redundant.py

test_05_rvpc_multi_tiers
Failure
554.30
test_vpc_redundant.py

test_05_rvpc_multi_tiers
Error
554.32
test_vpc_redundant.py

@blueorangutan test alma9 kvm-alma9

[SF] Trillian test result (tid-9626)
Environment: kvm-alma9 (x2), Advanced Networking with Mgmt server a9
Total time taken: 48870 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8839-t9626-kvm-alma9.zip
Smoke tests completed. 129 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@blueorangutan test matrix

@borisstoyanov a [SL] Trillian-Jenkins matrix job (centos7 mgmt + xenserver71, rocky8 mgmt + vmware67u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-9640)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 52787 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8839-t9640-xenserver-71.zip
Smoke tests completed. 128 look OK, 0 have errors, 1 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

all_test_human_readable_logs
Skipped
---
test_human_readable_logs.py

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 4.32%. Comparing base (e44c17e) to head (3589e4a).
Report is 27 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #8839       +/-   ##
============================================
- Coverage     30.93%   4.32%   -26.62%
============================================
  Files          5404     361     -5043
  Lines        380309   29121   -351188
  Branches      55507    5108    -50399
============================================
- Hits         117658    1260   -116398
+ Misses       247041   27719   -219322
+ Partials      15610     142    -15468

Flag
Coverage Δ

simulator-marvin-tests
?

uitests
4.32% <ø> (-0.02%)
:arrow_down:

unit-tests
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@blueorangutan package

@borisstoyanov a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9285

@blueorangutan test alma9 kvm-alma9

@blueorangutan test alma9 kvm-alma9 keepEnv

@borisstoyanov a [SL] Trillian-Jenkins test job (alma9 mgmt + kvm-alma9) has been kicked to run smoke tests

[SF] Trillian test result (tid-9878)
Environment: kvm-alma9 (x2), Advanced Networking with Mgmt server a9
Total time taken: 52051 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8839-t9878-kvm-alma9.zip
Smoke tests completed. 127 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_events_resource
Error
328.67
test_events_resource.py

test_01_events_resource
Error
328.68
test_events_resource.py

test_04_deploy_vm_for_other_user_and_test_vm_operations
Failure
89.78
test_network_permissions.py

ContextSuite context=TestNetworkPermissions>:teardown
Error
1.53
test_network_permissions.py


A problem with test.py on MOT17

Hi every one,
Many thanks to the authors that let others have a chance to study over their work. I encountered a problem once I ran test.py. It looks like  convert_mot_to_coco.py put some folders on the test stage. For example after running we may see MOT17-02-DPM on test vector which is coming from the training folder. That's why we can't run the test.py conveniently. please take a look at this problem and fix it on the repo.

I didn't understand the question. What happened exactly? How can I reproduce the issue (i.e., your command and data folder structures)? I can run the testing on my side following the instructions.

Actually the problem goes back to convert_mot_to_coco.py, line 17. If we set HALF_VIDEO = True, then no matter the stage is train or test, it assigns train directory to the data_path which is not supposed to be.
line 10: SPLITS = ['train_half', 'val_half', 'train', 'test']
line17: data_path = DATA_PATH + (split if not HALF_VIDEO else 'train')

This is expected, since the validation set we used is from the training set.

ok, thanks. So you mean if we want to perform the actual test on the test folder of MOT, this script is not designed for this aim, am I right?

Correct.


feat: Add helper functions to expr when parsing metadata. Fixes #5351

This allows you to do this in your WorkflowEventBinding:

spec:
  event:
    selector: ...
  submit:
    metadata:
      name: 'payload.repository.slug + "-" + sprig.trunc(8, payload.changes[0].toHash)'

Signed-off-by: Stephan van Maris<EMAIL_ADDRESS>Checklist:

[ ] My organization is added to USERS.md.

Not sure why the test is failing?


PWA-677 fixed unit test

Pull Request Test Coverage Report for Build 1031

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 39.759%

Totals

Change from base Build 1030:
0.0%

Covered Lines:
1550

Relevant Lines:
3949

💛  - Coveralls


Add aprende python

What does this PR do?
Add resource
For resources
Description
Active and updated book to learn python in spanish made by a CS teacher
Why is this valuable (or not)?
It can be used to teach from secondary/high school to upper levels.
How do we know it's really free?
The license is in the front page (GPLv3).
For book lists, is it a book? For course lists, is it a course? etc.
Yes, it is a book
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks @quobit !


fix(detector): change dump data structure

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

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

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##             alpha       #24   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           19        19
  Lines          594       603    +9
  Branches        46        48    +2
=========================================
+ Hits           594       603    +9

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

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

Impacted Files
Coverage Δ

controller/sentry/admin.py
100.00% <100.00%> (ø)

controller/sentry/detector.py
100.00% <100.00%> (ø)

controller/sentry/tasks.py
100.00% <100.00%> (ø)

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.


[Logging v2] Installed App with one option true in additionalLoggingSources shows false for all when checking Values yaml view

After installing rancher-logging in one of the supported Control Plane Additional sources I don't see the values used during installation properly.
Sample from a k3s openrc using
   k3s:
    container_engine: openrc
    enabled: true

Checking the Installed App shows:
additionalLoggingSources:
  eks:
    enabled: false
  k3s:
    container_engine: systemd
    enabled: false
  rke:
    enabled: false
  rke2:
    enabled: false

** The app was installed properly with the control plane option enabled **
rancher/dashboard#1109
Rancher version master-head (09/19/2020) bd88c23 HA k8s

@izaac There doesn't seem to be a way to navigate to the installed apps in the latest. So is this still an issue?
If this is still an issue then I'd like @vincent99 to chime in because I don't think this was caused by the logging chart pages.
It looks like the yaml is referencing spec.charts.values here
If I look at the api I see two values objects, one at spec.charts.values and one at spec.values. The spec.values appears to be what was set when installed. Is is the yaml incorrect?

TL;DR: The Values YAML tab of detail is showing the wrong info.
spec.chart.values is the entire original default values.yaml from the definition of the chart it was deployed with. (this is why in your screenshot it's long and has tons of fields)
spec.values is the user's input.  They are shown the full chart values (or a form equivalent) when launching the app, and edit whatever parts they want.  The dashboard then does a diff of the original vs the user's desired values and saves just that diff of the two as spec.values.  (this is why in your screenshot it's just the enabled flag basically, plus the special global fields we silently add).
So on the detail page the values that are shown should be the reconstituted combination of the two (which is what you get if you try to upgrade), but is currently showing just the original values and ignoring the user values.

Rancher version master-head (09/23/2020) e9a98a3
spec.values is now showing the user entered additionalLoggingSources from Installed Apps


TRUNCATE TABLE: table_name

'NAME'.'NAME'.'NAME' seems to make no sense with the TRUNCATE TABLE statement:.
truncate_table -> TRUNCATE TABLE table_name opt_materialized opt_storage

table_name -> NAME
table_name -> NAME '.' NAME
table_name -> NAME '.' NAME '.' NAME

The Oracle SQL TRUNCATE statement syntax diagrams can be found here:
https://docs.oracle.com/cd/E11882_01/server.112/e41084/statements_10007.htm#SQLRF01707
truncate_table:

This is a wrong assumption - the table name may consist of one to three parts separated by dots:


Focus the editor programmatically

Hello,
I want to focus my editor through a keyboard shortcut. I used a simple textarea before and could just call myTextarea.focus() to switch focus. How does this work with this editor? It looks like everything is rendered as divs, so I'm not sure how I can achieve this.
Thanks!

const easyMDE = new EasyMDE()
easyMDE.codemirror.focus()

Worked like a charm, thank you!


MapId related cloud based style is not working

GoogleMap(googleMapOptionsFactory = { GoogleMapOptions().mapId("b6fb728f53b6d3e8") })
The code above should apply cloud-based style. Currently no matter which style is set (via mapId), the style is not reflected within the app. It would be really great if changing this (runtime) would immediately reflect on the map.

@webfrea-k Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.

@webfrea-k Please take a moment to fill out this short survey. Thank you!
This is an automated message, feel free to ignore.

I'm able to repro. It appears that the options provided in the factory is somehow ignored.

Ah.. I completely forgot that this feature is only available if you opt-in to the latest renderer. See: https://developers.google.com/maps/documentation/android-sdk/releases#version_1800 Once you do that you should be able to see your cloud-based style.

Hello @arriolac
I have that, but it's still not working.
Maps initializer:
MapsInitializer.initialize(this, MapsInitializer.Renderer.LATEST, null). I've tried also with callback - it is called before I use the map, but the style is not applied.

@webfrea-k can you confirm in the callback what is the actual renderer used? There are cases when you can request LATEST but the actually loaded renderer is LEGACY

Ah yes, you are correct. It returns LEGACY. How can I request LATEST?

Your emulator likely has an older version of Google Play Services. You can update it as follows:
With the device connected to a computer with ADB and USB debugging enabled: adb shell am start -a android.intent.action.VIEW -d https://play.google.com/store/apps/details?id=com.google.android.gms
Or by hand:
1.  Open Android Settings
2.  Open "Google, Services & preferences"
3.  Tap the question mark icon: (?), top right.
4.  Click the overflow menu icon (3 dots)
5.  Click "View in Google Play Store"
6.  Click the "Update" button if it's available. If an update is not available, it means you're already running the latest version.

Thanks for all the assistance @arriolac , didn't manage to update the services on emulator (either way), but have tried it on real device, where it works correctly for the first time it's set.
If mapId is updated (via collectAsState() and used again) it does not update the map theme. I remember trying this back in the days where map was wrapped in AndroidView and it didn't work there either (I reverted back to local json map style). Is this unsupported feature, or should it work runtime?

@webfrea-k good to hear that you're able to get the LATEST renderer.
Are you trying to set the map with a different mapId from when it is initialized? As currently designed, it is meant to only be set once on initialization. This is because the mapId is a property of a GoogleMapOptions which can only be passed in the constructor of MapView, and so recomposing the GoogleMap with a new mapId is quite expensive. I deliberately choose the factory init pattern for this reason so it's not possible to recompose/reinstantiate the map.

Closing this issue as mapId should only be initialized once. Although I strongly recommend against this, we can reevaluate this behavior if folks feel like the map should be reinstantiated/recomposed on a new GoogleMapOptions/mapId.

Okay @arriolac, thanks for all the provided info & support. I can still apply json style to the compose map right? Looking at api ref, it's probably MapProperties.mapStyleOptions right?

Yep, that's correct @webfrea-k

I know this is an old thread but there's a lack of information on getting cloud-based map styling working on a virtual device. I've spent quite a bit of time on it this afternoon and I just can't get it to work. The map ID is correctly set and linked to a map style, and Google Play Services are up to date on the device. It seems like this just doesn't work on virtual devices...


Allow Containers to be used for Deployment Jobs

Please allow containers to be used for deployment jobs, just like regular jobs.  We depend on containers for many required tools depending on the build/release and are unable to use deployment jobs without deploying new monolithic agents with all tools installed to handle deployment jobs
jobs:
- deployment: publish
pool: Container
container: python:3.7-slim
Unexpected property container

1, would be great indeed!

yes, we do have plans to support it. However, it will be a while before we can get to it.


[vite:dep-scan] missing export in package error when importing directly from package file

Describe the bug
I have a npm package that includes both the src and dist folders. The package does not export types so I've imported a type from a source file directly like
import { DataTableColumn } from '@prefecthq/miter-design/src/types/DataTableColumn';

Typescript follows the import just fine. And I'm able to build my project that uses this package just fine. But if I try and run the vite dev server I get an error. This was working fine in vite 2.8.x but when updating to 2.9.x the error appears.
✘ [ERROR] [plugin vite:dep-scan] Missing "./src/types/DataTableColumn" export in "@prefecthq/miter-design" package

    node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:37698:7:
      37698 │   throw new Error(
            ╵         ^

    at bail (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:37698:8)
    at resolve (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:37775:10)
    at resolveExports (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:38441:12)
    at resolveDeepImport (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:38459:31)
    at tryNodeResolve (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:38232:20)
    at Context.resolveId (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:38040:28)
    at Object.resolveId (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:36609:55)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async resolve (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:36821:26)
    at async /Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:36978:34

  This error came from the "onResolve" callback registered here:

    node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:36968:18:
      36968 │             build.onResolve({
            ╵                   ~~~~~~~~~

    at setup (/Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:36968:19)
    at handlePlugins (/Users/craig/Development/nebula-ui/node_modules/esbuild/lib/main.js:843:23)
    at Object.buildOrServe (/Users/craig/Development/nebula-ui/node_modules/esbuild/lib/main.js:1137:7)
    at /Users/craig/Development/nebula-ui/node_modules/esbuild/lib/main.js:2079:17
    at new Promise (<anonymous>)
    at Object.build (/Users/craig/Development/nebula-ui/node_modules/esbuild/lib/main.js:2078:14)
    at Object.build (/Users/craig/Development/nebula-ui/node_modules/esbuild/lib/main.js:1927:51)
    at /Users/craig/Development/nebula-ui/node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:36769:54
    at Array.map (<anonymous>)

  The plugin "vite:dep-scan" was triggered by this import

    script:/Users/craig/Development/nebula-ui/src/pages/SettingsApiKeys.vue?id=0:165:7:
      165 │ import '@prefecthq/miter-design/src/types/DataTableColumn'
          ╵        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Build failed with 1 error:
node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:37698:7: ERROR: [plugin: vite:dep-scan] Missing "./src/types/DataTableColumn" export in "@prefecthq/miter-design" package

Reproduction
https://stackblitz.com/edit/vitejs-vite-d4u67a?file=src%2FApp.vue&terminal=dev
System Info
System:
    OS: macOS 11.6.1
    CPU: (8) arm64 Apple M1
    Memory: 769.52 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.5.0 - ~/.nvm/versions/node/v16.5.0/bin/node
    npm: 8.3.0 - ~/.nvm/versions/node/v16.5.0/bin/npm
  Browsers:
    Chrome: 100.0.4896.88
    Firefox: 98.0.1
    Safari: 15.1
  npmPackages:
    @vitejs/plugin-vue: ^2.3.1 => 2.3.1
    vite: 2.9.5 => 2.9.5

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Expected. If a path is to be imported, you need to explicitly add that path to the exports field.
TypeScript works fine now because it hasn't fully supported exports yet.
It won't work after the introduction of the nodenext/node12 module feature, which is mentioned at https://github.com/microsoft/TypeScript/issues/46452

Thank you for the explanation and the information about typescript's coming changes to support exports.


[kie-issues#624] Fix coercing double type in Mvel compiler

Fixes https://github.com/apache/incubator-kie-issues/issues/624
The double type was not handled in the mvel compiler.

@tkobayas could you please take a look too?

@baldimir LGTM, thanks!


Fix gl-interop validation error & window not closing

Fixes #1764
No changes to the underlying library have been made. Thus no changelog items to report.
The validation error was caused due to activating all supported device features. Specifically feature buffer_device_address. This means this feature is not properly supported and for it to function correctly support will have to be added to the memory allocator. This is out of the scope of this issue.
I'm not sure what exactly caused the window not closing, but changing the structure of the event loop to more closely mirror the triangle example fixed the problem.

I would say it's not a good idea to enable features you don't need. Features don't just enable new behaviours, but they can change existing ones as well. As you already discovered, enabled features can add extra requirements and disallow certain other things.

@fayalalebrun Merged. Thanks for the fix, and I apologize for the late review.


Implement publish script

Signed-off-by: Dimitar Milov<EMAIL_ADDRESS>Add publish job to run on version tag
Signed-off-by: Dimitar Milov<EMAIL_ADDRESS>Description
Implement a publishing script that

builds
test
publishes to PSGallery if and only if all tests pass and the module version is higher than the available on the PSGallery

Add GHA to trigger the publish script on version tag
Closes: #32
Type of change
Please mark options that are relevant:

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. If applicable, please also list any relevant
details for your test configuration.

[X ] Run publish.ps1 locally with bad NuGetAPIKey

> .\publish.ps1 -NuGetApiKey BAD
[1:03:33 PM] INFO: Publish CloudEvents.Sdk Module to 'C:\git-repos\github\sdk-powershell\CloudEvents.Sdk\CloudEvents.Sdk'
[1:03:35 PM] INFO: Run unit tests

Starting discovery in 9 files.
Discovery finished in 344ms.
[+] C:\git-repos\github\sdk-powershell\test\unit\ConvertFrom-HttpMessage.Tests.ps1 1.1s (360ms|564ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\ConvertTo-HttpMessage.Tests.ps1 396ms (153ms|204ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\New-CloudEvent.Tests.ps1 192ms (27ms|151ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\Read-CloudEventData.Tests.ps1 171ms (13ms|145ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\Read-CloudEventJsonData.Tests.ps1 196ms (45ms|134ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\Read-CloudEventXmlData.Tests.ps1 252ms (80ms|148ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\Set-CloudEventData.Tests.ps1 236ms (56ms|160ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\Set-CloudEventJsonData.Tests.ps1 186ms (20ms|157ms)
[+] C:\git-repos\github\sdk-powershell\test\unit\Set-CloudEventXmlData.Tests.ps1 210ms (64ms|136ms)
Tests completed in 2.99s
Tests Passed: 28, Failed: 0, Skipped: 0 NotRun: 0
[1:03:39 PM] INFO: Run integration tests

Starting discovery in 1 files.
Discovery finished in 196ms.
[+] C:\git-repos\github\sdk-powershell\test\integration\HttpIntegration.Tests.ps1 2.07s (1.4s|504ms)
Tests completed in 2.1s
Tests Passed: 5, Failed: 0, Skipped: 0 NotRun: 0
Performing operation: Publish-Module -Name CloudEvents.Sdk -RequiredVersion 0.2.1 -NuGetApiKey '...' -Repository PSGallery -Confirm:$false
Write-Error: C:\program files\powershell\7\Modules\PowerShellGet\PSModule.psm1:10990
 Line |
10990 |  …             Publish-PSArtifactUtility @PublishPSArtifactUtility_Param …
      |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      | Failed to publish module 'CloudEvents.Sdk': 'dotnet cli failed to nuget push Pushing
      | CloudEvents.Sdk.0.2.1.nupkg to 'https://www.powershellgallery.com/api/v2/package/'...   PUT
      | https://www.powershellgallery.com/api/v2/package/   Forbidden
      | https://www.powershellgallery.com/api/v2/package/ 1330ms error: Response status code does not
      | indicate success: 403 (The specified API key is invalid, has expired, or does not have permission to
      | access the specified package.).   Usage: dotnet nuget push [arguments] [options]  Arguments:   [root]
      | Specify the path to the package and your API key to push the package to the server.  Options:
      | -h|--help                      Show help information   --force-english-output         Forces the
      | application to run using an invariant, English-based culture.   -s|--source <source>
      | Package source (URL, UNC/folder path or package source name) to use. Defaults to DefaultPushSource if
      | specified in NuGet.Config.   -ss|--symbol-source <source>   Symbol server URL to use.   -t|--timeout
      | <timeout>         Timeout for pushing to a server in seconds. Defaults to 300 seconds (5 minutes).
      | -k|--api-key <apiKey>          The API key for the server.   -sk|--symbol-api-key <apiKey>  The API
      | key for the symbol server.   -d|--disable-buffering         Disable buffering when pushing to an
      | HTTP(S) server to decrease memory usage.   -n|--no-symbols                If a symbols package
      | exists, it will not be pushed to a symbols server.   --no-service-endpoint          Does not append
      | "api/v2/package" to the source URL.   --interactive                  Allow the command to block and
      | require manual action for operations like authentication.   --skip-duplicate               If a
      | package and version already exists, skip it and continue with the next package in the push, if any. '.

Test Configuration:

Toolchain:
SDK:
(add more if needed)

Checklist:

[x] My code follows the contribution
guidelines
of this project
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] 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
[ ] Any dependent changes have been merged and published in downstream modules

If you prefix your commit with chore: it will show up nicely in the CHANGELOG :)

Approved! Note: if you prefix the commit with chore: it will nicely render in the CHANGELOG.


Add webpack-dev-server polling example

I just filed https://github.com/webpack/webpack-dev-server/issues/194, to ensure this actually works, but once that is fixed (if it is indeed a bug), an example here to show how to have webpack-dev-server detect file changes using polling would be cool.

Please explain what it means for este, and feel free to reopen issue.


Update to d3 v4

d3 v4 was released a couple of weeks ago, and just recently published v4.1.1.
d3 v4 was released near the end of June, and published v4.2.1 near the start of August.
As a (potential) starting point, it was mentioned in #155 that there's been some work already to support v4 in @cgav's fork: cgav/d3-tip. Sorry, I looked into it further, that fork isn't in a state that can be merged.
It would also be great to add d3 as a peerDependencies dependencies config in the package.json, so that the plugin's supported version range of d3 is more explicit.

While the fork from @cgav supports d3 v4, it uses some new JavaScript features that didn't work in my environment.  I've shared my version of d3-tip, inspired by the work from @cgav, but with minimal changes to the older version so that it is more easily deployed.
It can be found here: https://github.com/VACLab/d3-tip

@davegotz Have you considered switching to an ES6 environment via Babel (compiling down to ES5)? It really is most sublime to be able to write with those newer features.

Paging @Caged, what's the status of d3-tip?

I simply haven't had the time or energy to pick this back up and also haven't used d3 in a while.  I hope that changes, I don't want to abandon the project, but in the meantime it looks like folks are carrying forward with fixes that get this working for d3 v4.

can verify that @davegotz fork https://github.com/VACLab/d3-tip works well with d3v4 in a script-tag or browser environment

I applaud the efforts of @davegotz and @cgav to improve d3-tip, but they both removed the AMD/CommonJS/browser switch in the header, which allows the library to work in multiple environments. They also both diverged master instead of forking, branching, and making a PR (or in @davegotz's case, started a completely different repo). So it's not possible to merge their changes back into the main repo.
I haven't worked with d3 much, but if someone could point out the relevant updates that needs to be updated for d3 ^4 compatability (hopefully, in a way that still works in ^3.5.5), I could make a PR. I tried looking at the diff between davegotz/cgav's changes but I'm no d3 expert. Or if anyone else with more d3 chops than I feels like forking and making a PR I'll be happy to give a hand.

@Caged @davegotz @cgav @micahstubbs This new #158 PR from @besson-genostar looks promising, since it doesn't remove the AMD/CommonJS/globals code. Would anyone be interested in testing out that one?
I also made PR #159 extending his code with peerDependencies and d3 micro library dependencies instead of the whole d3, since that looks to be the direction that d3 wants to be heading with their code. I haven't had time to properly test it out though (I've hit a roadblock trying to convert some unrelated code to support v4's d3-hierarchy).

If #160 gets merged (update package.json to match bower.json) and 0.7.0 is released to npm, this issue should be ready to close, I think?

@vdh Thanks for pulling all of this together and making a little easier for me to sort through these PRs.  With that in mind, I've granted you push access to the repository.  It's up to you, but if you want to continue to work on d3 v4 support, you now have the means and I would absolutely encourage it 🌟 !
As I mentioned, I hope to get back to this, but in the meantime this project could use a good shepherd and I would love to bring someone in to help with future releases so I'm not the single point of failure.   My email is in my profile if you want to get in touch outside of this forum.

@Caged Wow thanks! I think I'll need to get more familiar with d3 (especially v4) before I can be a proper shepherd of this project, but I'll certainly try to help out with PRs and such from contributers 😄

@Caged So will you still be handling the NPM releases?

@vdh Just returning from vacation and reading your message.  yeah, you can publish new releases on npm.  I might need to flip some switches to give you access.  Let me know what you need.  Thanks!

@Caged You could add me using the npm owner cli command. Surprisingly, Npm only uses that one level of access.

@vdh It turns out I didn't originally publish d3-tip to the npm registry, so I don't own the package.  I've emailed the current owner per this doc.  Hopefully we'll hear something back soon, otherwise we might have to choose a different name 😞

@Caged fascinating.  thanks for sharing the backstory.

@Caged Ahh! That explains that earlier issue of the last release of d3-tip not being deployed correctly on npm. Well, hopefully we can get that package ownership fixed up

@vdh what is your npm name?

@Caged Same as here, vdh

@vdh you're now an owner of the npm package!  You should be good to go on publishing 0.7.0.

NPM was fussy about 0.7.0 being occupied by something, so I had to publish 0.7.1 instead. But hey, we have d3 v4 now! 😄

Pulled 0.7.1 from npm fine. Working as advertised.
Thanks for this! I was just looking at using d3-tip with D3 v4 over the last few days so this was a timely fix.

@baerrach Also, if you need a version that makes use of d3's new micro libraries instead of the whole library, I've got a branch in the works for that. It'll probably be 0.8.0 in case anyone wants to keep using just d3 with 0.7.x

Do you have links to micro libraries?
I'm using rollup and tree-shaking, but I've not confirmed that shrinks everything for me. I just know stuff works.

@baerrach Here's where it's mentioned: https://github.com/d3/d3/blob/master/CHANGES.md
If you're using tree-shaking that might already reduce the output size for you already, depending on if the optimisation can successfully identify and strip the unused d3 micro libraries.
In a nutshell, d3 v4 is now just a thin wrapper around the micro libraries. Switching to micro libraries just means requireing/bunding those dependencies à la carte instead of via the d3 wrapper.
I have a (very temporary) branch of it here while we get the linting and other maintenance stuff set up first: https://github.com/vdh/micro-libraries (for a slightly-less-temporary branch use https://github.com/vdh/v0.7.1-temp-fork )

Oh right, I am definitely using modules.
As I'm new to ES6 and the d3 documentation for v4 doesn't go into enough detail when using modules (and things like rollup) it took me a while to work stuff out.
As all the documentation assumes you are importing all of d3 into the d3 namespace, when you move to modules you either have to drop the d3 prefix, or work out how to import a bunch of modules into the d3 namespace. Finally I worked out you need to create your own local d3 module where you import/export the bits that you want.
d3-tip will need to include similar documentation.

Whoops, I got those branch links messed up in my previous comment.
@baerrach You actually only need to roll your own d3 namespace when you're not using a module loader (i.e. when you're using it raw, directly in the browser).
If you're using a module loader (compatible with AMD or CommonJS), you can just require the modules directly. Check out this comparison to see how little the current d3-tip needed to be changed to use micro libraries: https://github.com/Caged/d3-tip/compare/linting...vdh:micro-libraries
You don't need a d3 variable any more, you can just use the methods defined inside the namespaces you get when you require the micro libraries directly:
// instead of:
var d3 = require('d3')
var div = d3.select(document.createElement('div'))
// you can now just do this:
var d3Selection = require('d3-selection')
var div = d3Selection.select(document.createElement('div'))
// or if you're using ES6:
import d3Selection from 'd3-selection'
const div = d3Selection.select(document.createElement('div'))

Sure, but then all the existing cut-n-paste examples need reworking :)
I found it easier to roll my own d3 namespace.

@baerrach Compatibility with cutting and paste large swaths of code doesn't sound like the best coding strategy 😦
You're also reducing your performance by requiring dependencies where they're not needed, and adding a new build dependency for the rollup, just to remove the need to rename a few variable references? It seems weird. Every module is already in their own namespace, you don't need to double-namespace them to make outdated code examples happy.


Change contribution link to local link

Set the link to be a local link rather than a full URL

This really isn't a needed change, closing


DoS protection

Apparently some students are not mature enough and we need some kind of protection. I'm thinking about protection in the PHP script to allow, for example, only ten requests in ten seconds. We can think about the exact rules.

We could try limiting the request based on the browser fingerprint and IP in this way others are not bothered by one DoS'er

The new scheme will block users for a longer period of time (initially 1 second, doubling that up to 1 minute) when they misbehave within 10 minutes from the last time.


Merge pull request #1 from sparklinlabs/master

make it so

Hi! I assume this pull request was done in error? Closing.


move to simple SQL

We are using a document database created on top of sqlite. It feels a bit limiting and unnecessary abstration. It may be a lot simpler and effective in the long run to use SQL and simple abstractions.
Approach
I propose using web.py database for this. web.py makes it easier to write SQL without adding complex abstractions.
For migrations, we can have a simple migrate.py with all the migration steps.
The Document class in the db module will be replaced by a BaseModel that will continue to support the find, find_all and save methods.

That would be a simple enough interface. LGTM 👍

done.


Add crc checks in put operation

This change makes sure that content of a chunk in a PUT operation is not modified in frontend (due to illegal reference counts of byte buf, etc) while we are writing it to server

Codecov Report
Attention: Patch coverage is 2.14286% with 137 lines in your changes missing coverage. Please review.

Project coverage is 18.47%. Comparing base (52ba813) to head (e92fbc9).
Report is 115 commits behind head on master.

Files with missing lines
Patch %
Lines

...ain/java/com/github/ambry/router/PutOperation.java
0.00%
110 Missing :warning:

...hub/ambry/router/ByteBufReadableStreamChannel.java
0.00%
23 Missing :warning:

.../github/ambry/router/NonBlockingRouterMetrics.java
0.00%
4 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (52ba813) and HEAD (e92fbc9). Click for more details.
HEAD has 2 uploads less than BASE

Flag
BASE (52ba813)
HEAD (e92fbc9)

3
1

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2915       +/-   ##
=============================================
- Coverage     64.24%   18.47%   -45.78%
+ Complexity    10398     2930     -7468
=============================================
  Files           840      864       +24
  Lines         71755    73447     +1692
  Branches       8611     8850      +239
=============================================
- Hits          46099    13568    -32531
- Misses        23004    58618    +35614
+ Partials       2652     1261     -1391

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[readme] add ninja requirement and update setup instructions

the readme didn't include the ninja requirement for cmake and untar yielded without .tar.

In the README we list the hard dependencies of sierra2mlir, ninja is a optional build tool you can tell cmake to use, so we would rather not add it there.
Regarding the README instructions, can you update the llvm url to the new version 16.0.4? Thanks

closing as it's stale and it's no longer meaningful


Is it possible to turn dag-format workflow definition to conductor's dsl-format automatically?

A workflow defined in dag-format looks like:
{
"tasks":{
"t1":{
"Task definition of t1"
},
"t2":{
"Task definition of t2"
},
"t3":{
"Task definition of t3"
},
"t4":{
"Task definition of t4"
}
},
"links":{
"1":{
"src":"t1",
"dst":"t2"
},
"2":{
"src":"t1",
"dst":"t3"
},
"3":{
"src":"t2",
"dst":"t4"
},
"4":{
"src":"t3",
"dst":"t4"
}
}
}
The tasks' execution order of this workflow will be: t1->[t2,t3]->t4,which means t2,t3 execute in parallel.Such format provides an opportunity to define workflow visually.Is it possible to let conductor support it?

@yangjiajun2014 This is not possible currently. It is a long-term goal for conductor to be able to define workflows using a visual tool at which time such a feature could come in handy/would be implemented.


Improve MacOS support

[ ] Add memory warning support
[ ] Add image cache support in CacheProvider

macOS support coming back?

Hi @rufferto, unfortunately the development on Carlos by my side it's a bit slow due to other duties, and I'm not planning to add macOS support in the short term. A PR for that would be greatly welcome, though.


Remove type-hint

The method getNamedRoute() returns a RouteInterface (type-hinted) which defines the method getIdentifier() used on the next line. So this explicit type-hint can be removed.

Coverage remained the same at 100.0% when pulling 2e030878925269feea1c613be8cd89f6687205d1 on adriansuter:patch-type-hint into 7f36c9e3ec0e002a915e6ef85677499d1cd0c728 on slimphp:4.x.


[ISSUE-3085][Improve] Improve streampark-flink module based on [3.4 Collection Rule]

FORcollectionreturned values, unless there are specialconcurrent(such as thread safety), always return theinterface, such as:
returns List if use ArrayList

3.Use isEmpty() instead of length() == 0 or size() == 0
I didn't find this way of writing in the streampark-flink module.
What changes were proposed in this pull request
Issue Number: close #3085

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): no

If there are no comments by tomorrow I will start merging

@Xuxiaotuan Thank you


BDD labels pre-processing

Hi, in the paper you mention that for BDD you estimate the middle point of adjacent lane markings because you have 2 lines instead of 1, and then you apply a dilation operation on top of it to make the training targets denser. Could you share the exact implementation of this to be able to reproduce your results?

I have put the generated labels on google drive in ENet-BDD100K-Torch repo.


Data-Driven Unit Tests Failing

Hi,
I have CodedUi Test projects and it is uses following sources
[DataSource("Microsoft.VisualStudio.TestTools.DataSource.TestCase", "https://tfs.xxxxx.com/Development 4.0/;ProjectName", "2873", DataAccessMethod.Sequential)]
We just upgraded to TFS 2017 and all tests which we were running using XAML Build and MTM 2012 stoped working, only we can run tests from VS.
Each time when I run tests using VsTest I have error
Error Message:
The unit test adapter failed to connect to the data source or to read the data. For more information on troubleshooting this error, see "Troubleshooting Data-Driven Unit Tests" (https://go.microsoft.com/fwlink/?LinkId=62412) in the MSDN Library.
Error details: Could not load file or assembly 'Microsoft.TeamFoundation.TestManagement.Controller, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
I tried do copy all missing DLLs to
C:\vstagent_test_work_tool\VsTest\15.9.0-preview-20180924-03\x64\tools\net451\Common7\IDE\Extensions\TestPlatform
But it is also do not work, then i have another error
Error details: Unable to cast object of type 'Microsoft.TeamFoundation.TestManagement.Controller.TestCaseDataConnection' to type 'Microsoft.VisualStudio.TestTools.Utility.TestDataConnection'.
Does anybody have DataDriven tests working with VsTest?

@Mastahh are you running these test locally or using build vnext? if you are using buildvnext which task are you using?

I'm using vNext Build and run it using Vstest Platform Installer and then VS Test to run tests.
Also I have a *.bat file to run tests locally, and it is works same way and also failing with same error.
I run this Agent with parameters
C:\vstagent_test_work_tool\VsTest\16.0.0-preview-20181205-02\x64\tools\net451\Common7\IDE\Extensions\TestPlatform\vsTest.console

@Mastahh thanks for the info. Unfortunately running test case data driving test is not supported via test tools installer and https://www.nuget.org/packages/Microsoft.TestPlatform nuget package. you need to have full VS installed to run these test cases.

At the moment I'm moving Test Data from TFS to SQL Server and plan to access this parameters same way as it was done for TFS.
I Just changed DataSourceAttribute to access SQL Server and it is working for now.
I'm do not want to install VS Enterprise on Test PC only for Test Run :)

@Mastahh the only thing which is not supported by tools installer and the nuget packages is Microsoft.VisualStudio.TestTools.DataSource.TestCase.
Accessing data from sql will work for you as you mentioned.
There are any plans to support DataSource = Microsoft.VisualStudio.TestTools.DataSource.TestCase in the nuget package/Tools installer.
/cc: @PBoraMSFT


How to run this code on custom data

Thanks for your great work! I check the code and find its hard coded for the benchmark given in the paper, whether  could i run on my custom data? thanks a lot!

Hi, the code has optional settings that you may not want or need. Each setting is easy to turn on or off using the input arguments to the scripts.
To run on your own dataset, create your own script. For example, create a copy of cluster_sobel_twohead.py inside code/scripts/cluster and replace the call of cluster_twohead_create_dataloaders in line 171 with a call to your own function, which would return 4 dataloaders:

dataloaders_head_B (for training main head): a list of config.num_dataloaders + 1 dataloaders each containing the main training data for the model. Every PyTorch dataloader is a wrapper for a PyTorch dataset. You can implement your own dataset class with the PyTorch interface. As you can see in the training script, images x are sampled from dataloaders_head_B[0] and images gx are sampled from each of the others, dataloaders_head_B[1..config.num_dataloaders]. So when you create the datasets for the latter, using the PyTorch interface, set the transform field to your invariance transforms. config.num_dataloaders corresponds to the number of sample repeats (r in experiment section of paper). So if you don't want extra sample repeats, you would just have one gx, and the length of dataloaders_head_B would be 2.
dataloaders_head_A (for training auxiliary head): like dataloaders_head_A but the dataset wrapped by each dataloader contains all training data for the model, i.e. including noisy or irrelevant images. Is the same as dataloaders_head_B if you have no extra data. Since training alternates between the main and auxiliary heads, dataloaders_head_B and dataloaders_head_A are alternately used.
mapping_assignment_dataloader: used for evaluation, i.e. similar to dataloaders_head_B[0]. This is used to find the 1-1 mapping between output clusters and ground truth classes.
mapping_test_dataloader: used for evaluation. After the 1-1 mapping is found using mapping_assignment_dataloader, it is used to assess the data contained in mapping_test_dataloader. For the fully unsupervised mode, images used to train the main head and images used to test it are the same (except in test we need to look at the labels to get performance accuracy), so mapping_assignment_dataloader = mapping_test_dataloader. (It's not for semi-supervised overclustering setting, where training and test sets are separate.)

In summary, you would only need to change that one function call to cluster_twohead_create_dataloaders.

@xu-ji For segmentation, I found for Postdam in line in data.py, it requires "unlabelled_train", "labelled_train", "labelled_test", but in the paper it said it's unsupervised method, this is confused to me, could you explain it? Also, how can I generate the input image pairs on my customize segmentation dataset? Thanks.

Images are taken from labelled_train because otherwise you would be not using most of the dataset. Labels are only used for evaluation to find the 1-1 mapping between output clusters and ground truth clusters, not for training.
If you don't have labels, you will train the network but won't be able to quantitatively evaluate it. This means you would be skipping the call to eval.
You don't need labels to generate pairs. You take your whole image, copy it and transform it to create the second image of the pair. The transforms used for Potsdam were jitter and flipping, done here.

Thanks. It's clear to me now. As for the training and test images, for the "unlabelled_train", "labelled_train", "labelled_test", what is the ratio? For example, I have 4500 "unlabelled_train" images, and the "labelled_train" is the same with "labelled_test", but only have 500 images, is it ok? Also, did you try depth images only for segmentation?

In line, for depth image only, do I need to using config.in_channels = 1 + 2 # depth + sobel, using_IR=False or config.in_channels = 1 # depth only, using_IR=False?Thanks.

If you look at the supplementary material (in /paper) table 6 gives the dataset sizes. Unlabelled train + labelled train = 8550 images, labelled test = 5400 images (so labelled train = 5400, unlabelled train = 8550 - 5400). You should be fine with 500 labelled images. The amount of labels required to find the mapping is very low.
We did not try anything with depth.
Your input channels would be 1. You would not use sobel filtering at all, that is a transform for colour images. Because you are working with depth, you may want to consider different transforms to what we used. Jitter is also an operation intended for colour images. You may want to consider trying salt and pepper noise, and flipping (depending on what your images are about), as your transforms.

Thanks. It's really helpful.

@xu-ji Can your IIC method do instance segmentation?

No. That would require some material addition to the method.

what about model ind for our custom dataset?
could you please describe model ind and --arch
is it possible to change input_sz like 256 for our data or not? for these models?

--model_ind is just a name for the experiment, to create the directory to store the results in. Can be anything.
--arch is used to select network architecture. E.g. here.
You could run the scripts on images of 256x256. You might have to change some architecture code (for example to remove any asserts to check for size). The easier way is just resize your images to one of the compatible sizes. For example for segmentation our Potsdam images were 200x200. You can find these details by looking at the code or in the supplementary material.

Hello, your work is very useful for me .Thanks a lot!
could you please tell me how to check the picture like splash.png after running segmentation _twohead.py. I'm trying to using my own dataset and check the result of picture. do I have add some code?

If it's your own dataset, probably best to write your own script. It's quite simple, just load your saved network, run your data through the network, get prediction per pixel, map each prediction to a colour.
There are some examples that I used at one point, the render*.py scripts in this dir, where I do exactly this. I use the PIL Image library or matplotlib to turn numpy arrays into images and save to file.

Thanks a lot for the awesome and useful work!
I was wondering about couple of things:

Are the main and auxiliary overclustering heads independent of each other? Say in a fully unsupervised segmentation task where I would want to use the best model from your experiments, which has 2 heads (head_A and head_B), could I just drop the overclustering head head_Afrom the model and use the resulting net with only head head_B as a pretrained net?
Given that the number of ground truth classes in my scenario would be different (say 10 instead of 6), could I simply reinitialize the Conv2d in the IIC head_B (i.e. the main head) from

(head_B): SegmentationNet10aHead(
    (heads): ModuleList(
      (0): Sequential(
        (0): Conv2d(512, 6, kernel_size=(1, 1), stride=(1, 1), padding=(1, 1), bias=False)
        (1): Softmax2d()
      )
    )
)

to
(head_B): SegmentationNet10aHead(
    (heads): ModuleList(
      (0): Sequential(
        (0): Conv2d(512, 10, kernel_size=(1, 1), stride=(1, 1), padding=(1, 1), bias=False)
        (1): Softmax2d()
      )
    )
)

similarly to what is shown here  for Sqeezenet?

Yes, inference on head B does not need head A. (Though they share the same trunk.) But which head is actually better for your downstream task may need testing to be known.

If you replace head B in a trained network with any randomly initialized new head, it'll need further training for its outputs to be meaningful, either with the IIC loss or some other relevant objective. But yes you could do this.


Retry Mechanism for Kubernetes Loader

Description
Retry mechanism using exponential backoff when trying to contact the Darp pod. This will make sure that an immediate fail wouldn't occur because envoy wasn't ready to accept connections yet.
Issue reference
https://github.com/dapr/dapr/issues/689
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ X] Code compiles correctly
[ ] Created/updated tests
[X ] Unit tests passing
[X ] End-to-end tests passing
[ ] Extended the documentation
[ ] Specification has been updated
[ ] Provided sample for the feature

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

Hey @DaveBben,  it'd be great if you can address the comments and we get this merged :)
Thanks!

Made recommended changes

Thanks, left one last comment.

Thank you for this contribution!


qemu: add nvdimm support using DT for arm64

As Shameer's patch drops the DT mode when add nvdimm support for arm64. This patch
enable it back.
Adopt Shameer's patch [1]
Fixes: #1148
Signed-off-by: Edmond AK Dantes<EMAIL_ADDRESS>[1] https://patchwork.kernel.org/patch/11174981/
@jon @jbryce

thanks @edmond-hk , this PR depends on https://github.com/kata-containers/runtime/pull/2990
any comments @jodh-intel @devimc

hello @jodh-intel @GabyCT, help test this PR, thanks.

/test

Hello @devimc @GabyCT @jodh-intel, help review this PR, thanks!

/teset

/test

/AzurePipelines run


[BUG] sending erc-20 from detail screen, no preselect

Describe the bug
When sending a ERC-20 token from their respective token detail screen, it does not pre select the wanted token but rather just selects ETH
To Reproduce
Steps to reproduce the behavior:

Go to ETH
Press on a Token
Press on send
See error

Expected behavior
Pre select the wanted token to send

Version 26

Additional context

[ ] Please verify for all tokens on all chains

Connected with #1291

QA done.


Enable two warnings (#1245)

because they will be soon be added to -Wall.
See https://gitlab.haskell.org/ghc/ghc/-/issues/15656
I already made this contribution against the ghc-8.10 branch, which in retrospect I think was not where I should have made it.  It's fine on that branch, it's just not particularly useful. To get it into new builds of GHC I think I need it on the ghc-head branch. Sorry for the repeated request.

Thanks! CI won't turn green on head branch these days but I will take care of any fallouts.

@tomjaguarpaw as far as I can tell this does not compile with current GHC master. I'm afraid I'm going to have to revert as it's currently blocking progress in GHC.
@alexbiehl, in general I think it would be best if we don't merge things to ghc-head until we know that they build and the corresponding GHC merge requests are queued. Things become very messy if haddock and ghc evolve in different orders.

@bgamari Makes sense. Sorry for the inconveniences.

@bgamari Where should I put my Haddock commits then? They somehow need to get into this repository so that they are mirrored on Gitlab so that I can update the utils/haddock submodule.

@bgamari says on IRC that I should make a wip/ branch in Gitlab.

To mirror what I said on IRC: the workflow here (documented here) is:

push your branch to a wip/ branch on https://gitlab.haskell.org/ghc/haddock (and your GitHub fork, if you want)
open a GHC merge request bumping the haddock submodule.
wait for the merge request to pass CI and get approval
push your haddock changes to GitHub (if you haven't already) and request that they be merged to the ghc-head branch
wait for the GitHub MR to be merged; after it's merged queue up the GHC MR for merge

@bgamari I agree. Unfortunately Haddock and GHC are very tightly coupled. I have even thought about arguing for Haddock to move into the GHC repo but from experience there are more Haddock releases than for GHC so tracking them in a mono repo probably takes the flexibility for different release cadence. But still they are circular dependencies build wise.
Do you have a vision for a simplified development process once we moved over to GitLab? They would still be separate repositories as far as I understand so the general setup won't change that drastically? Is there maybe a GitLab feature that would help us coordinate MRs over several repositories?
On a more tangential note, one thing I am trying to achieve for some time now is to have Haddocks test-suite run on ghc-head branch. My hope is that we can make that possible with the
In general, improving matters would be very much appreciated. And I am willing and able to help.


Sending Statements to an LRS

Afternoon, team!
One of our external partners is reporting that the most recent codebase seems to have an issue sending statements to an LRS.  I'd assumed this was just a small thing with a missing / on some LRS endpoint, but one of my engineers reported the same problem.
Did the process change for sending statements to an LRS?
Thanks,
-Trey

Here is the setup we are trying to use on the UI

It does not seem to even be trying to send the xAPI statements to an LRS, and is just defaulting to downloading them.

Here is the setup we are trying to use on the UI

It does not seem to even be trying to send the xAPI statements to an LRS, and is just defaulting to downloading them.

There actually was a very recent update to address an issue with LRS sends stemming from some earlier work. The issue was in the DS (server-side) repo not this UI one, can you confirm that the latest master version of client and server are running in the environment experiencing the issue?
Thanks,
Cliff

There actually was a very recent update to address an issue with LRS sends stemming from some earlier work. The issue was in the DS (server-side) repo not this UI one, can you confirm that the latest master version of client and server are running in the environment experiencing the issue?
Thanks,
Cliff

Just pulled all of the code (both UI and API) from github fresh, and still seem to run into the same problem

Just pulled all of the code (both UI and API) from github fresh, and still seem to run into the same problem

@FlorianTolk @vbhayden been trying to get to the bottom of this today. I also made clean installs and recompiles of master today to try to figure it out. First off we definitely need better error messaging when the LRS push fails because it can fail rather silently (i'm opening a ticket for that internally), but unfortunately when all my credentials and endpoints are in place I can't seem to reproduce the issue (tried with two flavors of LRS). Also the download of statements isn't an indicator either way because it does that regardless. However it does indicate, if the download has statements, that the sim was successful so we can probably rule sim params/profile out.
A couple of debug ideas:

It doesn't expect the trailing slash, and explicitly appends '/statements' so in my case it was just "https://{host}/xapi"
One thing that kept catching me (and MAY fail silently which as i mentioned we need to fix) is if the LRS already contains those statements from a prior run. DATASIM being deterministic, having the same params and seed in two runs would result in a conflict error from most LRS implementations.
LRS integration auth is purely basic auth, have you tried posting the same statements via curl or postman?

Barring any of those what i might do is just make a branch to sloppily spit out whatever the LRS says in response and point you guys to it for a test so you can at least see if there's some noise from your LRS endpoint.
-Cliff

@FlorianTolk @vbhayden been trying to get to the bottom of this today. I also made clean installs and recompiles of master today to try to figure it out. First off we definitely need better error messaging when the LRS push fails because it can fail rather silently (i'm opening a ticket for that internally), but unfortunately when all my credentials and endpoints are in place I can't seem to reproduce the issue (tried with two flavors of LRS). Also the download of statements isn't an indicator either way because it does that regardless. However it does indicate, if the download has statements, that the sim was successful so we can probably rule sim params/profile out.
A couple of debug ideas:

It doesn't expect the trailing slash, and explicitly appends '/statements' so in my case it was just "https://{host}/xapi"
One thing that kept catching me (and MAY fail silently which as i mentioned we need to fix) is if the LRS already contains those statements from a prior run. DATASIM being deterministic, having the same params and seed in two runs would result in a conflict error from most LRS implementations.
LRS integration auth is purely basic auth, have you tried posting the same statements via curl or postman?

Barring any of those what i might do is just make a branch to sloppily spit out whatever the LRS says in response and point you guys to it for a test so you can at least see if there's some noise from your LRS endpoint.
-Cliff

Good Morning Cliff,
I managed to curl those statements (once I removed the id field, a lot of these already existed in the public adl lrs) once I used the -k flag.
However, removing the trailing slash did not work. I think the fact that many of these statements have duplicate ids may be what is causing it to fail to send any statements to the LRS? I am unsure how DATASIM handles actually sending xAPI statements

Good Morning Cliff,
I managed to curl those statements (once I removed the id field, a lot of these already existed in the public adl lrs) once I used the -k flag.
However, removing the trailing slash did not work. I think the fact that many of these statements have duplicate ids may be what is causing it to fail to send any statements to the LRS? I am unsure how DATASIM handles actually sending xAPI statements


Problem with non-ASCII character in csv

The next error I have found:

It seems the 'products.csv' file has a non-ASCII character that cannot be decoded.

@danielcanueto can you try to run the tutorial with the latest version of featuretools (v0.3.0) and the last copy of this repo? I suspect this issue may be fixed now


[Training] incorporate changes from June pow-wow

[x] remove FAQs
[x] remove sub-levels from Table of Contents
[x] Author Attribution: move from sidebar into section at bottom of page; retitle 'Contributors' and add sentence(s)
[x] retitle page to PDS4 Training, remove second sentence, and remove redundant mentions of 'PDS4'
[x] remove link for 'PDS4 Documentation'
[x] move all items from 'Where Can I Find' to 'PDS4 Conventions'
[x] move 'PDS4 Software' to 'PDS4 Tools' just before 'LDDTool' and reword to 'Key Tools'
[x] add sentence to end of 'PDS4 Tools' for Tool Registry
[x] move any high-level, clickable item that is a link to the top of its own list
[x] make caret the same blue as document links
[x] make sure all videos are left in the documentation

Sheri has approved the changes. @edwardbarraza, let me know if anything comes up, and we'll create another ticket for it. Thank you!


Update README.md

Hi,
This small PR adds a button to get your app on F-Droid. You can later add a button for Google Play the same way :
[<img src="https://play.google.com/intl/en_us/badges/images/generic/en-play-badge.png"       alt="Get it on Google Play"       height="80">]()

Hi,
Many thanks for yor help!
I still have to tackle the google play deployment, I'm not sure this tool would be useful to anyone but me 😅


DAFFODIL-1172: Emit warning when lengthUnits="bits" is used with bigints.

The DFDL spec prohibits the use of lengthUnits="bits" for types xs:integer and xs:nonNegativeInteger. This update will now emit a DeprecatedTypeUse warning in this case and will be changed to an error in a future release.
DAFFODIL-1172

I don't think the spec makes it clear that lengthUnit="bits" cannot be used with xs:integer and xs:nonNegativeInteger. I see the following table:

Section 12.3 of the says this in the table describing lengthUnits="bits":

'bits' may only be used for xs:boolean, xs:byte, xs:short, xs:int, xs:long, xs:unsignedByte, xs:unsignedShort, xs:unsignedInt, and xs:unsignedLong simple types with binary representation, and for calendar (date and time) simple types with binary packed representation.

I don't understand the reasoning, bit it is pretty unambiguous.
Note that this also adds that it's not allowed for representation="binary". So we can have lengthUnits="bits" for these types when representation="text", we should ensure we still allow that.

The DFDL spec is clear that (section 12.3 definition of lengthKind property:
'bits' may only be used for xs:boolean, xs:byte, xs:short, xs:int, xs:long, xs:unsignedByte, xs:unsignedShort, xs:unsignedInt, and xs:unsignedLong simple types with binary representation, and for calendar (date and time) simple types with binary packed representation.
Integer types other than these are xs:integer and xs:nonNegativeInteger.
Numeric types other than those are float, double, decimal.
There has been agreement in the DFDL workgroup that lengthUnits bits will be allowed for hexBinary, and these can be arbitrarily long.

If we are currently allowing bits, i.e., the code is present and tested, for integer and nonNegativeInteger types, then we should not disable this functionality, but rather should just add a tunable, defaulting to allowing the current behavior, which can be flipped to turn on stricter rules.

The current behavior is still allowed except that it now emits a warning. I updated the tests to reflect the desired usage. Do we want to:

Remove the warning, convert the SDW to a tunable SDE?
Update tests to try both the updated and deprecated way?
Revert tests back to the deprecated way and update to the desired usage later?

Let me opine about this for a sec and I think the right thing to do will emerge.
DFDL didn't want to allow 'bits' for some things to both make implementations not have to agonize of features nobody would need, and to avoid users causing themselves grief. E.g., if we only want to support IEEE floats on byte boundaries then restricting xs:float to not have length units 'bits' makes some sense.
What we have learned is that data format spec documents often pick one way of expressing length, e.g., bits, and stick with it. When creating a DFDL schema it is helpful to use the units that are in the spec document, even if the usage is restricted to multiples of 8 bits long.  So it is convenient in some cases to say dfdl:lengthUnits='bits' even for types where bits makes no sense like xs:float.
So for that reason, I think Daffodil never implemented checks to enforce what can have length units bits.
But, to the letter of the DFDL spec, length units 'bits' isn't allowed, so not portble.
So I think we want a tunable that says to warn on this usage (which can be suppresed), and a tunable to allow/disallow length units bits - i.e., cause it to be an SDE.
This would apply to all the types where we allow bits, but the DFDL spec does not.
Including hexBinary, float, double, decimal, integer, nonNegativeInteger (assuming I have the right list).

To be clear: we want a warning (which can be suppressed via existing means), and then a tunable which says whether to SDW, or SDE. Would default to SDW now.

Note that this also adds that it's not allowed for representation="binary". So we can have lengthUnits="bits" for these types when representation="text", we should ensure we still allow that.

I have asked for a clarification at the DFDL workgroup about this. I expect this is just poor wording, and there is no intention to allow 'bits' lengthUnits for these types ever.

Per discusssion on DFDL Workgroup 2023-01-19, the wording in the spec does not seem ambiguous. bits is allowed only for the specific set of types with binary representation, and this is to be interpreted as meaning that bits length units are allowed for that specific set of types only when they have binary representation, and bits is not allowed otherwise. Hence, bits is not allowed when they have text representation.

To be clear: we want a warning (which can be suppressed via existing means), and then a tunable which says whether to SDW, or SDE. Would default to SDW now.

Updated to emit a warning by default and to raise an error when the allowBigIntegerBits tunable is set to true.

Hence, bits is not allowed when they have text representation.

Updated to add a check for binary representation.

Can you rebase to the lastest master and resolve the conflicts?
Also, can you add the Deprecated/Compatiability stuff to your commit message? Unfortunately updating the PR description doesn't change the commit to match and must be done manually.


Fix/svace issue 210308

Commit 1: Handle NO_CATCH issues
Added missing try-catch statement
resolve 457555, 457556, 457557, 457558
Commit 2: Handle svace INTEGER_OVERFLOW issues
To handle
int h_stride_end = height - eff_k_height - ph;
int w_stride_end = width - eff_k_width - pw;
cases, add ph, pw respectively.
It is stricted than before.
It resolve 457562, 457563

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #985. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @lhs8928, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @lhs8928, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/985-202103081446580.40226411819458-b06063e55aef815dd8bac8d9b7e44d8f20e9f70e/.


Add isOnlyEmoji() function

Checks if a string contains only of emoji.

Since you anyways have this code opened, could you remove old (failing) php 5.4/5.5 and hhvm?

Since you anyways have this code opened, could you remove old (failing) php 5.4/5.5 and hhvm from travis ci config?

Done.


2 4 stable product show cache fix

Now the cache key would look like this views/spree/products/286-20150410055431673670000/952679/5bbf3e786b04e2d50d9bcdab4f4f13ba
Where the 952679 would be the current_order.id

This is just merging stable into master. Will do that manually


Since Gradle 7.4, compileJava does not recognize symbols in generated source directory

When running ./gradlew clean build -xtest, the compiler fails to find symbols in [project root]/proto/build/tmp/protoGeneratedSrc which is a directory produced by a build script we wrote.
This happens in multiple different projects since upgrading from Gradle 7.3.3 (where there was no problem) to Gradle 7.4 (where this problem does occur)
Some strange findings:

Running ./gradlew clean build (omitting the test exclusion) results in a successful build ✅
Running ./gradlew clean ; ./gradlew build -xtest (separating clean and build -xtest into two separate invokations) results in a successful build ✅

Expected Behavior
Running ./gradlew clean build -xtest should result in a successful build.
Current Behavior
Running ./gradlew clean build -xtest results in a compilation error with the following stack trace:
> Task :[REDACTED]:compileJava
[REDACTED: file path].java:1167: error: package [REDACTED] does not exist
      [REDACTED: line of code];
                                                                 ^
[REDACTED: 5 similar errors]
                                                       ^
6 errors

> Task :[REDACTED]:compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':[REDACTED]:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 11s

Context

Gradle 6.7.1 no error ✅
Gradle 6.8.3 no error ✅
Gradle 7.0 no error ✅
Gradle 7.1 no error ✅
Gradle 7.2 no error ✅
Gradle 7.3 no error ✅
Gradle 7.3.3 no error ✅
Gradle 7.4 error occurs ❌

This issue is slowing us from upgrading from Gradle 6 to 7.

Steps to Reproduce

I will try to give a self-contained example project where this occurs, but so far I haven't been able to untangle the dependencies of our projects from this error. I will update this bug once (if) I manage to overcome this.
Your Environment

Happens with both JDK 8 and 11
Happens in both MacOS and Linux

This looks like a problem in input/output declaration and might have to do with changes on how clean is now checking that it should not run after a producing task.
It would be great if you could share a build scan as it might help confirm that.
Unfortunately, without a scan or a reproducer, it is going to be hard to figure out what's the root cause.

Can you share the output with --console=plain so we can see the order of tasks executed (both with 7.4 and pre-7.4)?  I suspect it is a task ordering problem related to how the dependencies are declared between tasks, but it's hard to theorize without understanding exactly what's happening.  Obviously, a reproducer would be best, but until you have that, just seeing the task order might help.

Sorry for the delayed response.
We found that creating a reproducer is infeasible, so there's sadly no way to progress in this bug on Gradle's side.
However, on our side, we found a way to restructure the project's task dependencies such that this bug no longer occurs.
With that, I'll close this bug.


Release 1.5.1

On the docket:

Filter top-level requirements against env markers. #592

Released:

https://github.com/pantsbuild/pex/releases/tag/v1.5.1
https://pypi.org/project/pex/1.5.1/


Provide in NLS interface format methods

Provide in the NLS interface format methods for
BigDecimal
Numbers
Date (both old and new)
in the used Locale.

PR #36


To make curl requests to Elastic 8.3 it's necessary to turn off xpack.security

Hello guys once again!
While trying to make curl requests to the initial Elasticsearch instance, I was getting the following error: curl: (52) Empty reply from server.
Elasticsearch was running as normal from systemctl status however the reply was empty.
Checking on stackoverflow, I saw the following post:
https://stackoverflow.com/questions/35921195/curl-52-empty-reply-from-server-timeout-when-querying-elastiscsearch
Which stated that we need to change xpack.security.enabled to false as it seems from Elastic 8.1, it's been a default setting.
#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically
# generated to configure Elasticsearch security features on 13-08-2022 12:01:10
#
# --------------------------------------------------------------------------------

# Enable security features
xpack.security.enabled: true

So if we change xpack from true to false, we are now able to make curl requests without SSL.
xpack.security.enabled: false
However, in the post it states that xpack needs to be true when Kibana is used!
Thanks once again!

Hey @Sh4dow-BR thanks for checking out the book and your comment. The book was written using version 7.x as 8.x hadn't been released yet.
With version 8.x of the Elastic Stack, there were tremendous architectural changes to its deployment, configuration, and management. One of those changes is the way that the Elastic Stack implements security.
So, for a few suggestions that you can pursue depending on your use case:

Check out the Elastic documentation on a secure deployment of 8.x [Elasticsearch, Kibana]
Check out this project that stands up a full and secure Elastic Stack using Docker with a single shell script (macOS or Linux)


fix postgresql idle connection closed determination

Every after 8 hours, some idle connections in the connection pool gets closed. So we need to re-connect the remote server. However, the original code determine whether to re-connect based on the error message which is variable on different machine and platform. So we changed it to determine based on error code which is much more accurate!

Coverage increased (+0.01%) to 93.476% when pulling f606bb8527752d12cd9489e6953dc77363a91112 on UtillYou:master into ef85849bafa98063dfb85bee0da54235064c7eab on 75team:master.


Setup readme

Add a basic readme and repo description with the language logo and Discord badge.

Idk how the resources should be handled. Should the image the the top of the readme link to the resources from the language suggestions repo, should only the files used be included, etc.?

Thank you so much for the PR!
I'd say we should refer to the other repo for now, not to fragment resources too much. In case we tweak it, we'll only have to do it in one place that way.


makePathsAbsolute does not correctly detect whether a string is a path.

Highlighted in this issue: https://github.com/TryGhost/Ghost/issues/10570
makePathsAbsolute detects the existence of / or \ in a string and assumes it is a path - this broke custom certificates for MySQL and could break others values in future.
This is a tricky issue to fix, and may require we just carefully use the function as was done in https://github.com/TryGhost/Ghost/pull/10573

Closed because makePathsAbsolute implies that this takes paths, undefined behaviour for the wrong type is acceptable imo


Help with Stage 2: llvm-to-backend

Greetings everyone,
As a newcomer to this project, I've been experimenting with the provided examples to familiarize myself with the tool. Currently, I'm researching ways to integrate hipSYCL into my project and leverage its capabilities. Specifically, I'm exploring the Generic SSCP compilation flow, and I have a question regarding Stage 2: llvm-to-backend.
I noticed that the implementation provides a tool (such as llvm-to-ptx-tool or llvm-to-spirv-tool) that can be used to perform the stage 2 compilation step manually. However, I'm not entirely sure how to use the tool. Could someone please provide me with instructions or guidance on how to use it effectively?

First you need to obtain the HCF file, e.g. using syclcc --opensycl-targets="generic" -mllvm -hipsycl-sscp-emit-hcf (The -hipsycl-sscp-emit-hcf argument will be renamed in the future to -opensycl-sscp-emit-hcf).
You can inspect the content of the HCF file using opensycl-hcf-tool. This will list all the content in the HCF:
opensycl-hcf-tool file.hcf -p root
There will be an images node. The subnodes of that node correspond to names of device code images embedded in the HCF. Currently, this is very simple as we only generate a single global LLVM IR image per HCF for now. This image is called llvm-ir.global.
You can then use the llvm-to-backend tools to translate this image, e.g for the llvm-ir.global image.
lvm-to-spirv file.hcf output.spirv llvm-ir.global
Note however that the tools currently do not expose all the functionalities that can be required to successfully translate an HCF that has been generated from SYCL. For example, the SYCL_EXTERNAL feature requires linking of device images which is not exposed in the tools.
Also, note that some backends have to be configured appropriately using the --build-opt or --build-flag arguments. This is a bit of a moving target, and might change in the future. At the moment SPIR-V wants to have the size of local memory configured. In the future, it is also planned to configure the work group size at stage 2 compilation time.


Branch on issue #10

Closes #10

@Ethel2003 thanks for opening this MR. Excellent work. I'm proud of you.
I'll start reviewing asap.


Update manifest.json

search commands don't work on messages

I'll change those others and add to this PR

@johnataylor  can you merge this for me please?


tscore/eventnotify: change fcntl include path

The default include path for fnctl.h changed some time in the 90's.

[approve ci]

The "Jenkins Debian" job failure seems unrelated.

[approve ci debain]

[approve ci debian]

All github-debian builds are failed now. Looks like the build script has a problem with fetching repositories.

[approve ci debian]

Cherry picked to 8.1.0


Adding spectral entropy to feature table

Adding two new types and the entropy for the best spectrum in each row

Sorry I should have mentioned that.
It was a programming tutorial that I gave. Wanted to upload the video but audio quality was bad