NoClassDefFoundError with RxJava

java.lang.NoClassDefFoundError: Failed resolution of: Lrx/AsyncEmitter$BackpressureMode;
Because of https://github.com/ReactiveX/RxJava/pull/4580/files

(on rxJava v1.2.5)

oops - duplicate of https://github.com/cantrowitz/RxBroadcast/issues/13

The new version is out on maven. Let me know of it isn't there
On Fri, Jan 20, 2017, 5:12 PM Zak Taccardi<EMAIL_ADDRESS>wrote:

Closed #15 https://github.com/cantrowitz/RxBroadcast/issues/15.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cantrowitz/RxBroadcast/issues/15#event-931381632, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABqD-M4R9A2BhHuHkVIEaEgT-qT10JHUks5rUTFNgaJpZM4LpzSm
.

I don't see it yet
https://search.maven.org/#search|gav|1|g%3A"com.cantrowitz" AND a%3A"rxbroadcast"

seems like an issue with sonatype. Created an issue https://issues.sonatype.org/browse/MVNCENTRAL-1516

I don't see 1.2.5 on maven - has it been published?

1.1.1 is the latest. We aren't tracking rxjava.
On Wed, Feb 15, 2017, 9:58 PM Afik<EMAIL_ADDRESS>wrote:

I don't see 1.2.5 on maven - has it been published?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cantrowitz/RxBroadcast/issues/15#issuecomment-280216467,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqD-I4589ZOHV9aUTy6a-I8Y3Xr2qAHks5rc7tSgaJpZM4LpzSm
.


YJDH-496 | KS-Backend: Create and send youth summer voucher on accept

Description :sparkles:
KS-Backend: Create youth summer voucher on accept
YouthSummerVoucher:

Change YouthApplication <-> YouthSummerVoucher relation to 1:0-1.
Previously the relation was 1:0-N. Change related_name from
youth_summer_vouchers to youth_summer_voucher to reflect this.
Change YouthSummerVoucher.summer_voucher_serial_number to a positive
integer validated as at least 1. Use sequential youth summer voucher
serial numbers starting from 1 i.e. 1, 2, 3, ... etc. Add and use
package django-sequences for this.
Change default ordering to summer_voucher_serial_number

YouthApplication:

Prefix set_handler and handle functions with underscore to make it
explicit that they are not part of the class's public interface
Create youth summer voucher when accepting a youth summer application
Allow accepting a youth summer application only if it doesn't have a
related youth summer voucher

YouthApplicationSerializer:

Add to_internal_value function to remove read-only field "handler"
from results. As the "handler" field is read-only it should not be
present in the to_internal_value function's result but it is. Remove
the field explicitly and add FIXME into code about the unexplained
behavior.
Add modified_at and receipt_confirmed_at to Meta.read_only_fields
Reduce duplication by adding Meta.read_only_fields to Meta.fields

Add tests for youth summer voucher serial number sequentiality:

test_youth_summer_voucher_sequentiality
test_youth_summer_voucher_sequentiality_duplicate_create
test_youth_summer_voucher_sequentiality_failing_transaction
test_youth_summer_voucher_sequentiality_failing_nested_transaction
test_youth_summer_voucher_sequentiality_failing_nested_transactions
test_youth_summer_voucher_sequentiality_complex_transaction_nesting

Add/Change other tests:

test_youth_application_serializer_fields

Categorize YouthApplicationSerializer fields into
required/optional/read-only field partitions.

Add youth summer voucher checks to tests

test_youth_applications_activate_unexpired_inactive
test_youth_applications_activate_unexpired_active
test_youth_applications_activate_expired_inactive
test_youth_applications_activate_expired_active
test_youth_applications_dual_activate_unexpired_inactive
test_youth_applications_accept_acceptable
test_youth_applications_accept_accepted
test_youth_applications_reject_rejectable
test_youth_applications_reject_rejected

Extend test_youth_application_post_valid_random_data test coverage

Test 20 instead of 10 random youth application postings
Test with different field combinations

Only required fields
Required fields and optional fields
Required, optional and read-only fields

Test response content
Test created youth application content
NOTE: This makes the total combinations tested 20 * 3 = 60 which
is considerably higher than the previous 10. The running time is
still in my opinion acceptable.

Lock youth application for update in accept/reject actions to prevent
multiple accepts/rejects of the same youth application.
Shared code additions:

Add LockForUpdateMixin class which provides lock_for_update function
which can be used to lock current model instance for update using
select_for_update.

KS-Backend: Send youth summer voucher email
Send youth summer voucher email when accepting a youth application.
If youth summer voucher email sending fails then log an error, rollback
the transaction and return 500 Internal Server Error.
Extend mail sending functionality from YouthApplication._send_mail with
HTML and MIMEImage support and move it to Kesäseteli's utils.py to
send_mail_with_error_logging.
Add youth summer voucher email templates:

youth_summer_voucher_email.txt for plaintext email content
youth_summer_voucher_email.html for HTML email content

Add youth summer voucher email images:

Helsinki logo in the left bottom corner of email:

helsinki.png

Finnish/Swedish/English summer voucher logos

youth_summer_voucher-325e-fi.png
youth_summer_voucher-325e-sv.png
youth_summer_voucher-325e-en.png

Refs YJDH-369, YJDH-450
Issues :bug:
YJDH-369
YJDH-496
YJDH-450
Testing :alembic:
Screenshots :camera_flash:
English email

Swedish email

Finnish email

Additional notes :spiral_notepad:
English/Swedish/Finnish test emails as .eml files
Unzip and open the .eml files in your email client, e.g. Outlook:
test_emails_as_eml_files.zip

Codecov Report

Merging #845 (193c5db) into develop (e56f069) will increase coverage by 21.57%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##           develop     #845       +/-   ##
============================================
+ Coverage    57.40%   78.98%   +21.57%
============================================
  Files          768       60      -708
  Lines        19212     1884    -17328
  Branches      2222        0     -2222
============================================
- Hits         11029     1488     -9541
+ Misses        7811      396     -7415
+ Partials       372        0      -372

Impacted Files
Coverage Δ

backend/shared/shared/models/mixins.py
66.66% <66.66%> (ø)

...nd/shared/shared/service_bus/service_bus_client.py
33.33% <0.00%> (-57.58%)
:arrow_down:

backend/shared/shared/yrtti/yrtti_client.py
37.50% <0.00%> (-53.13%)
:arrow_down:

backend/shared/shared/audit_log/viewsets.py
45.56% <0.00%> (-50.64%)
:arrow_down:

backend/shared/shared/audit_log/audit_logging.py
76.59% <0.00%> (-10.64%)
:arrow_down:

frontend/tet/admin/src/pages/new.tsx

...pplications/forms/application/step2/utils/dates.ts

...esaseteli/handler/src/components/footer/Footer.tsx

frontend/shared/src/auth/AuthContext.tsx

...on/steps/step2/accordions/EmploymentAccordions.tsx

... and 704 more

Continue to review full report at Codecov.

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

Merged although SonarCloud gave 1 Bug and 1 Code Smell:

The Code Smell was about an added FIXME comment which is fine IMHO.
The Bug was about not adding table headers using <th> tags to the youth summer voucher email's HTML table content. The table headers were omitted because the table was only used for visual grouping and its columns did not have a semantic meaning beyond "the left part of the table" and "the right part of the table".


[Proposal] Consider using tape test runner

Tape supports esm and can be piped to a variety of reporters, which opens the door for further integrations (i.e. running test on the site)
https://github.com/substack/tape

We prefer using jest since it is popular and familiar to our contributors. As I mentioned in #451, we cannot remove babel, I don't see any advantage in switching testing framework here. Please let me know what you think.

Before closing, consider the advantage of using TAP-based reporters.
Thanks for your consideration.

@bennypowers I'm going to chime in late here and agree with @tejasbubane
I'm not sure I see the advantage in switching the entire track over for what seems to be a matter of Coke vs. Pepsi.  If there were an inadequacy we needed to address, I could be convinced, but...
Please don't be discouraged from further comments and contributions!  We really do value comments and contributions.


Realtime pin monitoring does not work on Pi's < 5

The realtime pin monitoring uses the "pinctrl" utility supplied with Pi 5 in order to get pin state information. It's currently not available on Pi 4 (does it come with Bookworm, perhaps?), so this needs some investigation.

See #11 - pinctrl is a "Bookworm thing" rather than a "Pi 5 thing", and I've verified that "live mode" is working correctly (over SSH) on Pi 5, Pi 4B and Pi 1B+ (although due to #12 it's not very "realtime" on a Pi 1 :laughing: ).


Add connectors card and service category labels, take 2

This is the re-do of https://github.com/redhat-developer/app-services-ui-components/pull/239 that was reverted to save for later. DO NOT MERGE until ready in May!
Adds a new connectors card to the overview page per https://issues.redhat.com/browse/MGDCTRS-645
Also adds service labels to all cards on the overview page.

Closing this one since actions are not being run for some reason


Example implementation for handling MsalThrottlingException

How can I handle it when I catch it? I need an example implementation.
    try{
        Future<IAuthenticationResult> future =
        confidentialClientApplication.acquireToken(authorizationCodeParameters);
        IAuthenticationResult authenticationResult = future.get(1, TimeUnit.MINUTES);
    }
    catch(ExecutionException e){
        if(e.getCause() instanceof MsalThrottlingException){
            //how to handle it
        }
    }

https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-error-handling-java
There was a document about it also(you can see the screen shot in above link), but it doesn't give an example handling implementation. Could you give an example?

Hello @javate : I don't think we have a specific example showing it being handled. That MsalThrottlingException object has a retryInMs field, which is based on the Retry-After field in the HTTP 429 response, and that value shows how long the server recommended to wait.
So, a basic handling could be as simple as "Try to make the token request. If an MsalThrottlingException is returned wait for MsalThrottlingException.retryInMs milliseconds, then try the token request again". If your application plans on having multiple users or making calls to different backend services, then you could also try making other calls during that downtime.

Closing due to inactivity. If you have any questions or related issues, feel free to leave a comment or re-open this thread.


Fix the authservice httpGet probe config and use jwks_uri.

Signed-off-by: Jianfei Hu<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incfly
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incfly]

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


Add type "guards" to method arguments

Steps To Reproduce
http://deck.net/9ec0d1c5f88869b6739643876c266124

I guess that it is not good idea because it is non standard way to call a method. What about if you pass string instead number? If you need some gueard then you can add it manually, for example, to handle numbers values range
ui = ui + 0;
i = i + 0;
b = (byte)(b + 0);

This code just ensure that a input data is correct, even if this code call from dynamic environment.

In any way, thanks for suggestion, we will discuss with the team what we can do


Might wish to consider an engine keyword like xarray for IO.

are you thinking through xarray.open_rasterio()?
(Which seems to be deprecated in favor of rioxarray).
What kind of benefits would we expect to change the engine? Reading with rioxarray would allow lazy loading I guess; but performance-wise, rioxarray and open_rasterio() seem to abstract rasterio which presumably loads through GDAL, which presumably loads through HDF4/5 netCDF libraries. I would not expect a speedup here.

on the other hand, we might consider swapping out netcdf4, h5py and pyhdf4 with just rioxarray to use a common interface for all three. We'd need to be careful to ship a rasterio version that supports all 3 file formats though.


[FEA] Profiling tool auto-tuner should consider spark.databricks.adaptive.autoOptimizeShuffle.enabled

Fixes https://github.com/NVIDIA/spark-rapids-tools/issues/670
The auto-tuner should recommend users to set spark.databricks.adaptive.autoOptimizeShuffle.enabled=false before making shuffle partition recommendation.
Here are some preliminary benchmark results:
Databricks AWS

Configuration Setting
Ave Runtime (s)

Baseline
1275.5

Adaptive Auto Shuffle
1201

shuffle partitions = 400
1190

Databricks Azure

Configuration Setting
Ave Runtime (s)

Baseline
1209

Adaptive Auto Shuffle
1309

shuffle partitions = 400
1208

For "Adaptive Auto Shuffle", we append
"spark.sql.adaptive.enabled": "true",
"spark.databricks.adaptive.autoOptimizeShuffle.enabled": "true",

to the baseline template, and for "shuffle partitions = 400", we append
"spark.sql.shuffle.partitions": "400",

I am fine with that for now. Maybe we can revisit that when we want to make the autotuner output more informative including configs that overlap/conflict with the GPU ones.

Thank you for the feedback @amahussein! I will keep an eye if we need to revisit this.


Hidden Date Format Field Getting Wrong ID Attribute

I've been using pickadata for multiple version now and had an input element named 'txtProjectStartDate' with an id of 'txtProjectStartDate'.
When i init the pickdadate I specify :
formatSubmit: 'yyyy/mm/dd',
hiddenPrefix: 'hid_',
hiddenSuffix: '_val',
and using Firebug could see a hidden form element being correctly generated:
input  type="hidden" id="hid_txtProjectStartDate_val" name="hid_txtProjectStartDate_val"
This seemed to work fine as expected. I believe I was using v 3.5.0. I recently upgraded to 3.5.3 and now the hidden element is being generated as:
input type="hidden" id="txtProjectEndDate_hidden" name="hid_txtProjectEndDate_val"
notice that the NAME attribute is correct, but the ID attribute is not.

Hi
I have a concern with this, fairly old, issue :)
In my project, I handle some form-data where I, for various reasons, do not submit the form, but rather go over the input fields and get each value.
I am interested in the hidden value, not the displayed one, and not having an id on the hidden field, makes this somewhat harder.
I have been able to add an id to the hidden field, by going through the _hidden object, and adding the id there, but as the API says: If you have a valid reason for using this, please mention it in the Issues
Would it be possible to add id's on the hidden value, back in?
Thanks in advance!


[Bugs] NAS LastVisitedRegisteredTAI length should be 7

Describe the bug
NAS LastVisitedRegisteredTAI length should be 7
To Reproduce
Dump LastVisitedRegisteredTAI
Expected behavior
NAS LastVisitedRegisteredTAI length is 7
Environment (please complete the following information):

free5GC Version: 3.0.4
OS: Ubuntu 18.04
Kernel version: 5.0.0-23-generic
go version: 1.14.4 linux/amd64

Pull Request
Pull Request for the fix.

The PR has been merged.
Thanks a lot for the contribution!


Add README.md file

Change-Id: I038c3030f2f6d38969b25939fcba9aca1867a565

感谢提交 Pull Requests！
Thanks for submitting a pull request.

start build

手动触发！
感谢 Pull Requests！
Thanks for submitting a pull request.

Security Check : bf8f93ead269ed47f60161f2152d77ab89a0ae83

auto build success,number:156

autotest fail,number:1370


Re-opened PRs can potentially merge requirements

Discussion: https://balena.zulipchat.com/#narrow/stream/348930-balena-io.2Fflowzone/topic/Flowzone.20skipped.20almost.20everything/near/455074162
Here is the suspected order of events where a problem may occur:

PR is closed manually for any number of reasons (unmerged)
PR close event triggers the workflow and runs the Custom Clean job, and maybe some others
At some point in the future, the PR is reopened manually or by Renovate
Flowzone workflows are not currently triggered by reopen event types so nothing happens
The last successful workflow run at this point was on the previous close event, so the All jobs required step has a result of skipped
Jobs with a skipped result are unusually considered to be passing in branch protections, so at this point the PR can be merged manually by clicking Merge

The possible solutions vary:

Run All jobs on all event types, but mark as failed if the PR is not open
Run workflow on reopen events (this requires changing the calling workflows in 100s of repositories)
???

The core of this issue seems to be that Github PR triggers do not include closed (including merged) events by default, and they must be added. Combine this with the fact that Github treats skipped jobs as meeting merge requirements puts us in this situation.

Resolved by https://github.com/product-os/flowzone/pull/1144


fix: prevent viya from generating guid based html files

Summary
This prevents viya connections from generating uuid based files
Testing

[x] Made sure viya results worked as expected
[x] Made sure SAS 9 worked as expected via iom

Tested this out locally this afternoon. Looks good on viya connections.

To test this, we'll just need to make sure ods html results work as expected for viya and non-viya connections.

It works well with Viya and SAS9 IOM connection.


Fix dependencies version

Hi there,
today my CI pipeline failed to build my docker image in which the python code references your lib.
It failed because gcc was missing from my image which was not the case the last time it was built (4 days ago).
After some investigation why the gcc was required, I found that regex was the culprit. regex is a dependency of dateparser and it was updated yesterday with the version 2019.12.9.
It is a good pratice to fix the version of all dependencies when you release a version of a lib because without changing the version of a lib, it might crash because a dependency has changed.
thanks for your job on this lib :)

Fixing dependency versions makes sense on applications using those libraries, but I don’t think libraries are meant to have fixed versions of dependencies, only version checks to ensure that compatible dependency versions are used.

May this be a duplicate of https://github.com/scrapinghub/dateparser/issues/505?

This is similar, you're right!
As I said, the problem with a library not fixing dependencies (with a single version or a range) is that you can't ensure that the version of the lib you released will still work when a new version of a dependency will be.
And even a range of versions is complex to achieve when the dependency you use doesn't respect the semantic versioning.

I was wrong then, this is definitely something we need to do. Let us close this and keep track of this issue at #505.

#505 is about a specific issue with 2019.02.19, and I think the way to solve it is to change the entry in setup.py to regex !=2019.02.19 (although it probably does not really affect anyone at this point).
That does not apply here, though. It sounds like the latest regex does work with dateparser, it simply requires gcc. If things worked fine after installing gcc, I think there’s nothing we should change in dateparser. You can, and probably should, freeze versions on your end, as I suggested in my first comment.

I don't think any version of regex should work. Imagine they change the contract (parameters or result) of a function you use in your code then a previously functionnal release will not work any more.
I may add that fixing the regex version on our end is not a good practice when using loose coupling. I should not have to be aware that when I use dateparser lib I have to install the regex lib or fixing its version.

If you use dateparser along with a different library that also uses regex, if each library pins a different version, you are screwed.
Instead, we need to define in setup.py a range of versions of regex that should work with dateparser.

I agree with @Gallaecio and I will close this issue because this was fixed when we merged this: https://github.com/scrapinghub/dateparser/pull/600.
Feel free to reopen the issue if you consider that it's not solved.


Not able to open my jrnl

on Pop!_OS 18.10 and my journal will not open. I have tried completed removing jrnl, also tried resetting the config file and reconfiguring to point to file and it keeps giving this error:
Traceback (most recent call last):
  File "/usr/local/bin/jrnl", line 11, in <module>
    sys.exit(run())
  File "/usr/local/lib/python2.7/dist-packages/jrnl/cli.py", line 138, in run
    config = install.install_jrnl(CONFIG_PATH)
  File "/usr/local/lib/python2.7/dist-packages/jrnl/install.py", line 76, in install_jrnl
    util.set_keychain("default", password)
  File "/usr/local/lib/python2.7/dist-packages/jrnl/util.py", line 65, in set_keychain
    keyring.set_password('jrnl', journal_name, password)
  File "/usr/local/lib/python2.7/dist-packages/keyring/core.py", line 44, in set_password
    _keyring_backend.set_password(service_name, username, password)
  File "/usr/local/lib/python2.7/dist-packages/keyring/backends/SecretService.py", line 62, in set_password
    collection = self.get_default_collection()
  File "/usr/local/lib/python2.7/dist-packages/keyring/backends/SecretService.py", line 47, in get_default_collection
    raise InitError("Failed to unlock the collection!")
keyring.errors.InitError: Failed to unlock the collection!

This was over SSH. I found that I had to unlock the keyring locally on the machine.


Add structured grid outline

@ajpmaclean : Please review.

Please resolve the conflict

Conflict resolved. Please review.

Thanks


Disable flask messages in standalone

All flask messages should be surpress, and instead there should be a simple optional printout to the command line

Closed by https://github.com/spfrommer/torchexplorer/commit/2e2ae85e825c6fd76143fc6db24bae3a02b9428a


The new version of 2.1.0 has an error that unable to identify the map

Thank you  for your providing.Here I find an error.I use the leaflet.pm of 2.0.3 can well done my work, but when I update the leaflet.pm to the version of 2.1.0, I can find some error like "unable to identify the map in the leaflet.pm.mini.js". I have no idea about it. Please resolves it .Thanks.

Please provide a jsfiddle showing the problem

I am so sorry for your waiting. I have test again about the plug-in of 2.1.0  that it is working successfully.


ECU-R (2160xxxxxxx) connection refused and requiring manual reboot often

I just started using this integration and am very grateful for it.. Though for whatever reason it doesn't seem to be very stable in my environment.. I am running into cached mode A LOT:

and have set an automation to cycle a smart plug to reboot the device.. it has automatically done it 3 times today.. with the last time taking nearly 2 hours to reconnect.. My wireless signal is great.. I have tried some of the tricks by moving the system and even removing the wifi antenna, but it doesn't seem to be helping..
This is happening in the middle of the day not after sunset..
Is there anyway to make this system work with a wired connection?

That's a lot indeed! I own the same ECU with firmware. It is is hard to tell why this is happening could be interference from surrounding WiFi and/or Zigbee signals. Try to switch channels on the 2.4Ghz band or see if the ECU is roaming between AP's. It is true that sometimes it happens more frequent than other periods but this is extreem. Wired connection does not work, feature is undocumented. Here's my cache usage:

I moved my device again.. it's right under the WAP and has fantastic signal.. but it didn't seem to help.. It is going into cached mode crazy often.. I have also changed my 2.4ghz channel.. I don't know if it's just my unit or what's going on.. But  have no idea why it would keep getting a connection refused

Preventing interference sometimes means weaken the signal of surrounding devices (Zigbee and WiFi share the same channel), not to strengthen it. So removing the ECU further from the AP and other devices that might cause interference could be considered. Take in account the signal strength of the inverter (monitor that).

Is there anyway to test to see what's going on root cause wise?
Signal wise things look good, and I I can see I'm not losing packets via network.. I'd love to know if the system itself is overworked or something..
Any issues with me switching the polling to a shorter time to see if it is still switching over to cache mode as much? Or will that make matters worse?

Keep an eye on the signal data from the inverters. Increasing the number of queries will only make things worse, an interval of 300 seconds should be fine but you could try 240. Try a restart of the ECU if you've increased the query interval before.

Update… I’ve rebooted both the ECU and my HA container.. since back up I haven’t had an issue. I saw some issues with another device automation via HA and so I reset it. It’s been over 2 hours with no caching. It’s a good start. If we make it through the next day or two with little to no cached mode I think we are good

I'll close this issue for now. Feel free to raise another issue when needed.


refactor: context only parenting

This PR is a draft showing what changes would be required to restrict explicit span parenting to context only (rather than allowing a span, or context). This is an effort towards validating that: https://github.com/open-telemetry/opentelemetry-specification/issues/510 is viable in Ruby.
There were two options to provide an explicit parent to start_span and friends. One was named with_parent and expected an argument to be a span. The other was named with_parent_context where the argument was a context. In this PR we removed with_parent_context and updated with_parent to accept a context rather than a span.
I also added a Tracer#context_with_span convenience method which is the equivalent of ctx = tracer.with_span(span) { |_, c| c }, which was something I found myself doing in tests when I removed explicit span based parenting.
The original with_parent option was only used in tests. Instrumentation used with_parent_context, further validating context based parenting want we want.

https://github.com/open-telemetry/opentelemetry-specification/pull/875 also requires on_start for span processors to accept a parent_context parameter. This requires a little refactoring because Span#initialize only has a SpanContext and not the parent Context.

This is ready for review and can merge when folks are comfortable with it. The corresponding spec changes merged earlier today: https://github.com/open-telemetry/opentelemetry-specification/pull/875.


Error while starting the server

How to view doctor
and how to add patient to the network

updated the project to the latest version the issue has been fixed.


Delay usage of AppAssertionCredentials

This should avoid some import problems on the test servers related to
issue #21.

Where does the secrets.json normally come from? If I clone this repo and run grunt build, will the secrets.json be there or does it need to be copied in as a separate step?

@phoglund you have to run grunt build and then all that stuff is built.
previously you could run it directly from the appengine directory (sans javascript being compiled with grunt build) but now you have to build all of it.

LGTM.

Ok. My point is we need some way to bring up the server on the bots without importing the stuff that broke the bots before (e.g SignedJwtSomething). The bots do build using grunt build. Will this patch solve that or do we need to add a app.yaml flag the bots can override?

@phoglund how are you running the server on the bots? If you are using dev_appserver.py then it should just work. The problem was the import and now the actual object that was being imported should never be used. When running dev_appserver.py we look for secrets.json and if it's not there then we just do logging to stdout. The only time this would fail is if it was running on AppEngine.

It does use dev_appserver, but the problem was the crypto libraries were too old on the bot, but not on our workstations.
To test this, go into the google_appengine SDK you're launching from. Edit google_appengine/oauth2client/client.py. Go to line 44 or thereabouts and change the line HAS_CRYPTO = True to HAS_CRYPTO = False. Run your code with google_appengine/dev_appserver.py path/to/checkout/out/app_engine and ensure you can still get a call up on that server.
If that still works you're good. Remember to change back the HAS_CRYPTO line later :)

It works. Since it's very late here I will merge this tomorrow when I get in.


Animations (PageSlide and CrossFade) can now be added in Xaml files

Hello,
I would like to say that I am very impressed with what you guys have built so far in Perspex. Modern C# with Rx goodness. It's awesome! I synced today on both Windows and OSX, built from source, and both platforms ran smoothly with no fuss.
Now on to the business. I am submitting my first pull request for a simple change that adds the ability to specify animations (PageSlide and CrossFade) within Xaml files. To support that I also added a TimeSpanTypeConverter to support this to the Markup.Xaml project.
Let me know if I should make any additional changes. I am hoping I can contribute to this project regularly, it would be for a very good cause.
We can talk more later if you like.
Jason

Thanks, looking great. Just added a few questions.


Supporting legacy formats (compatability with acrg)

Adding legacy compatability to ObsData object (created when get_obs.. functions are called) to current ACRG formats. This is to mimic a dictionary to allow the dataset to be returned when the site key is used (e.g. ObsData["MHD"] would return the dataset - equivalent to ObsData.data). This is to ensure initial legacy compatibility with current ACRG formats which can be depreceated over time and then replaced.
This won't impact the current workflow and can be replaced when we don't need it anymore, but will make transition from current acrg formats to any new formats easier.

Codecov Report

Merging #74 (ca1e84b) into devel (70ef136) will decrease coverage by 0.03%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##            devel      #74      +/-   ##
==========================================
- Coverage   56.41%   56.37%   -0.04%
==========================================
  Files         106      106
  Lines        7062     7072      +10
==========================================
+ Hits         3984     3987       +3
- Misses       3078     3085       +7

Impacted Files
Coverage Δ

openghg/dataobjects/_obsdata.py
56.25% <41.66%> (-43.75%)
:arrow_down:

Continue to review full report at Codecov.

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

Seems to be an issue with generating the documentation from the workflow notebook but I didn't make any changes on this branch to the notebook format.

Seems to be an issue with generating the documentation from the workflow notebook but I didn't make any changes on this branch to the notebook.
This is causing one of the test cases below to the fail (ubuntu 3.7) but all other versions seem to pass fine.

Yeah this is an issue that's been introduced with the new jinja release going 2 -> 3. In the searchRank branch I've updated the requirements to pin the jinja version until I get a chance to look into what's going on / something changes on their end.

Example code to check this:
from openghg.modules import ObsSurface
from openghg.localclient import get_obs_surface
import os
import tempfile
tmp_dir = tempfile.TemporaryDirectory()
os.environ["OPENGHG_PATH"] = tmp_dir.name # "/tmp/openghg_store"
home = os.getenv("HOME")
decc_file = os.path.join(home,"openghg/notebooks/tutorials/data/DECC/bsd.picarro.1minute.248m.dat")
decc_results = ObsSurface.read_file(filepath=decc_file, data_type="CRDS", site="bsd", network="DECC")
data = get_obs_surface(site="bsd", species="ch4", inlet="248m")
print("Type of data returned from get_obs_surface",type(data))
print(f"Extract Dataset {type(data.data)} using data.data")
print(data.data)
print(f"Can also extract Dataset {type(data['bsd'])} using legacy format data[sitecode]")
print(data["bsd"])
The ability to extract the Dataset using data["bsd"] is what has been added in this pull request.

Waiting on fix related to  jinja version going into devel, to check the tests all pass before this can be merged.
Would it possible to move this fix into devel (rather than the searchRank branch) so this can be checked?


mixed resultset mapping for multiple entity

Q
A

Version
2.9.0

Support Question
I want to get mixed entity mapping of native query resultset like following.
public function getUpdatedListBySubforum(Subforum $subforum)
    {
        $em = $this->getEntityManager();

        $rsm = new ResultSetMappingBuilder($em);

        $rsm->addRootEntityFromClassMetadata(Thread::class, 'thread');
        $rsm->addRootEntityFromClassMetadata(Post::class, 'post',
             ['id' => 'post_id', 'create_date' => 'post_create_date']);

        $query = 'select ' . $rsm->generateSelectClause(['thread' => 'WFT', 'post' => 'WFP']) .
            ' from forum_thread WFT ' .
            'inner join (select thread_id, max(id) as last_post_id from forum_post group by thread_id) LPI on WFT.id = LPI.thread_id '.
            'inner join forum_post WFP on WFP.id = LPI.last_post_id where WFT.subforum_id = :subforumId';

        return $em->createNativeQuery($query, $rsm)
            ->setParameter(':subforumId', $subforum->getId())
            ->getResult();
    }

Actual Resultset
[
  {id: 1, class: Thread},
  {id: 1, class: Post},
  {id: 2, class: Thread},
  {id: 2, class: Post}
]

Expected Resultset
[
  ['thread': {id: 1, class: Thread}, 'post': {id: 1, class: Post}],
  ['thread': {id: 2, class: Thread}, 'post': {id: 2, class: Post}]
]

I suggest comparing a ResultSetMapping to the ResultSetMapping of an arbitrary join.
See https://github.com/doctrine/doctrine2/issues/7221
See https://github.com/doctrine/doctrine2/pull/7255
Closing as duplicate: while this isn't ideal, this is how DQL handles multiple root entities.


Add @nogc to std.algorithm.searching

@atilaneves

@alexandrumc What is the status of this PR? Do you plan on taking it to the finish line?

@alexandrumc What is the status of this PR? Do you plan on taking it to the finish line?

Yes, I’ll take a look soon.

ping @alexandrumc


Can I used algorithm triple des in compose mutilplatform ?

I try convert triple des from swift code to kotlin mutilplaform but result outputData?.base64EncodedStringWithOptions(options = 0uL = "SpE3b1aZ7MM=") wrong.
In module iosMain:
`@Suppress("CAST_NEVER_SUCCEEDS")
fun String.nsdata(): NSData? {
return (this as NSString).dataUsingEncoding(NSUTF8StringEncoding)
}
fun String.toUTF8String(): String {
val bytes = this.toByteArray(Charsets.UTF_8)
return bytes.decodeToString()
}
@OptIn(ExperimentalEncodingApi::class)
actual fun tripleDesEncryptString(input: String, keyRd: String): String? {
val inputData = input.toUTF8String().nsdata()
val keyData = keyRd.nsdata()
val outLength = cValue<ULongVarOf<size_t>>()
val outputData = NSMutableData.dataWithLength(inputData?.length?.plus(kCCBlockSize3DES) ?: 0uL)
val outLength1 = cValue<size_tVar>()
memScoped {
    val result = CCCrypt(
        op = kCCEncrypt,
        alg = kCCAlgorithm3DES,
        options = (kCCOptionPKCS7Padding or kCCOptionECBMode),
        key = keyData?.bytes,
        keyLength = keyData?.length ?: 0uL,
        iv = null,
        dataIn = inputData?.bytes,
        dataInLength = inputData?.length ?: 0uL,
        dataOut = outputData?.mutableBytes,
        dataOutAvailable = outputData?.length ?: 0uL,
        dataOutMoved = outLength1.ptr
    )

    if (result != kCCSuccess) {
        return null
    }
    outputData?.setLength(outLength1.size.toULong())
}
return outputData?.base64EncodedStringWithOptions(options = 0uL)

}
`
Has anyone ever come across this problem? Hoping for your help

Unless I miss something, the problem is not really related to Compose Multiplatform.
You likely need to carefully go through your code and check what parts get "translated" from swift to kotlin not properly.
For example I see:
@Suppress("CAST_NEVER_SUCCEEDS")
fun String.nsdata(): NSData? {
return (this as NSString).dataUsingEncoding(NSUTF8StringEncoding)
}

If you aim to have a multiplatform solution, then you can't use platform specific types. In this case it's NSData.
Kotlin's ByteArray can be an alternative, I think.
If it's not common code, then casting String to NSString, afaik, is incorrect. IDE highlighted that issue, but you suppressed it for some reason - @Suppress("CAST_NEVER_SUCCEEDS")

Closing this as unrelated to Compose Multiplatform.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Give the possibility to build a http handler with the HTTPServerBuilder

moving forward on this one, so I can improve the tests on perses afterward

we can always change later if the implementation is not tasty enough


Enhancement: Add a simple workflow to get started with GitHub Actions

This PR

[x] adds a very simple workflow to get started with GitHub Actions

💁♂ This is part 1 of a series of pull requests, as suggested here:

https://twitter.com/nikolaposa/status/1289475202573901824
https://twitter.com/localheinz/status/1289616543257464834

@nikolaposa
I am glad you like it! I'm prepared to follow up, as promised! 🤓

@localheinz Thanks!
So what do you think should be the next steps? I suppose this was a PR with demonstrative purposes, do you think we should merge it anyway?

@nikolaposa
👍 Let's merge it, and then I will follow up!

Thank you, @nikolaposa!


create the ios directory with the flutter create command?

What's the feasibility of creating the ios/ directory and xcode project as part of flutter create? So create would create the dart code, the android project (as we do now), and the ios project as well.
It looks like FlutterXcode.zip is ~20MB. I'm guessing the steps would be something like getting ios/Tools/ into cloud storage, stripping down the rest of the project into something much smaller, and getting it to a place where we only need to generate the xcode project once (and not re-gen over it).

/cc @chinmaygarde

Fixed over a few PRs.


Parser Causes Exception

Hello everyone!
I am not sure if I am the only one to experience this, but since version 2.9.1 the release fails with the following error:
TypeError: this.buffer.substring is not a function
    at Lexer.getLine (/home/runner/work/ott-channel-schedule-template/ott-channel-schedule-template/node_modules/yaml/dist/parse/lexer.js:208:28)
    at Lexer.parseStream (/home/runner/work/ott-channel-schedule-template/ott-channel-schedule-template/node_modules/yaml/dist/parse/lexer.js:244:25)
    at parseStream.next (<anonymous>)
    at Lexer.parseNext (/home/runner/work/ott-channel-schedule-template/ott-channel-schedule-template/node_modules/yaml/dist/parse/lexer.js:226:36)
    at parseNext.next (<anonymous>)
    at Lexer.lex (/home/runner/work/ott-channel-schedule-template/ott-channel-schedule-template/node_modules/yaml/dist/parse/lexer.js:160:32)
    at lex.next (<anonymous>)
    at Parser.parse (/home/runner/work/ott-channel-schedule-template/ott-channel-schedule-template/node_modules/yaml/dist/parse/parser.js:159:20)
    at parse.next (<anonymous>)
    at Composer.compose (/home/runner/work/ott-channel-schedule-template/ott-channel-schedule-template/node_modules/yaml/dist/compose/composer.js:130:20) {
  pluginName: 'semantic-release-helm3'
}

I tried with node versions 18, 19, and 20.
I did some investigation and I think the problem might be in `lib/publish.js' on lines 23- 24:
const chartYaml = await fsPromises.readFile(filePath);
const chart = yaml.parse(chartYaml);

I found this issue on GitHub that hints at the fact that readFile returns a buffer if called without a second argument, while yaml.parse() expects a string.
I would be curious to hear someone else's opinion on this and knowing if anyone else had this issue

I think you are correct, opened a PR to fix that. Would you be able to test the fix? I can release a rc

Published<EMAIL_ADDRESS>with a fix

The project is for my organization, so I can't trigger a new release if I don't have new features, but as soon as I or one of my colleagues release something either in this or another project, we will try the version with the fix

I think I will just release this before others run into the same issue. Thanks a lot for reporting and sorry that this caused issues.

Published a new version<EMAIL_ADDRESS>


Added Step attribute to number input type

Issue - #2712
@dougbu

Closing this PR since we decided to use type=text for float and double types.
Created https://github.com/aspnet/Mvc/pull/2812 with correct changes.


message_edit: Reinit topic input box typeahead in message edit UI.

This fixes the issue where the auto-complete dropdown doesn't reflect
the changed stream in the message edit UI
Fixes #19874
GIFs or screenshots:

@timabbott Could you please review ?

@timabbott Made the changes. Please review

Merged, after removing that first commit and reworking things to use the existing sub_store module to look up stream names.  Thanks for fixing this @pradyumn014!


pass service id as secret

Signed-off-by: invinciblejai<EMAIL_ADDRESS>

[test]

@invincibleJai Your image is available in the registry: docker pull registry.devshift.net/fabric8-analytics/f8a-3scale-connect-api:SNAPSHOT-PR-47

@msrb thanks Michal for help :)


formFieldProxy: Argument of type 'string' is not assignable to parameter of type 'never'

I am trying to componentize my forms, but keep having this error.
In my app, the component calling the componentized TextField  is not being rendered (no error messages).

This happens with a copy-paste "as is" from the example: https://stackblitz.com/edit/superforms-2-componentization?file=src%2Flib%2FTextField.svelte
Same issue when I copy-paste the examples from the doc (https://superforms.rocks/components#using-a-formfieldproxy)
Dependencies & versions:
    "@sveltejs/kit": "^2.5.0",
    "@sveltejs/vite-plugin-svelte": "^3.0.2",
    "svelte": "^5.0.0-next.55",
    "vite": "^5.1.1",
    "sveltekit-superforms": "^2.3.0",

Thank you

Here's my reproduction with similar error - https://github.com/vladshcherbin/svelte-superforms/tree/reusable-components

I've tried to use svelte context and store/retrieve form from there to avoid passing {form} to each input. Seems like the error is when it doesn't understand the shape of schema. Everything's working though.
If I pass {form} to all input components instead of a general context one or even change the Input.svelte generics from Record<string, unknown> to Record<string, string> the error disappears.

Compare with the updated example, it works without any error for TS.

Updated example doesn't even use TS :) Add any type and it breaks, link from above - https://stackblitz.com/edit/superforms-2-componentization?file=src%2Flib%2FTextField.svelte:

Yes, because Stackblitz doesn't support types well, especially in svelte components. Test it locally (with TS) and it should work fine.

Thank you, it's working like a charm now ! 😀🙏

Btw, just declaring the generics in the main script tag should work AFAIK.
I can confirm this works just fine for me:
<script lang="ts" generics="T extends Record<string, unknown>">

Without this part:
<script lang="ts" context="module">
  type T = Record<string, unknown>;
</script>

It works at runtime, but you will get type errors:

Looks like I'm lucky, no type errors for me 🙂
In case this is useful:

VSCode TS version: 5.3.2

devDependencies versions:

    "@sveltejs/kit": "^2.5.0",
    "@sveltejs/vite-plugin-svelte": "^3.0.2",
    "@total-typescript/ts-reset": "^0.5.1",
    "@types/node": "20.11.17",
    "@typescript-eslint/eslint-plugin": "^7.0.0",
    "@typescript-eslint/parser": "^6.21.0",
    "eslint": "^8.56.0",
    "eslint-config-prettier": "^9.1.0",
    "eslint-plugin-svelte": "^2.35.1",
    "prettier": "^3.2.5",
    "prettier-plugin-svelte": "^3.2.1",
    "svelte": "^5.0.0-next.60",
    "svelte-check": "^3.6.4",
    "tslib": "^2.6.2",
    "typescript": "^5.3.3",
    "vite": "^5.1.1",
    ``

Could your no-undef eslint rule be disabled?
Just a note, if you're using Svelte 5, then you should have the next version of the eslint plugin as well:
"eslint-plugin-svelte": "2.36.0-next.5",

(Thank you for the tip regarding eslint-plugin-svelte!)
Doesn't look like it, here is my .eslintrc.cjs
module.exports = {
  root: true,
  extends: [
    'eslint:recommended',
    'plugin:@typescript-eslint/recommended',
    'plugin:svelte/recommended',
    'prettier',
  ],
  parser: '@typescript-eslint/parser',
  plugins: ['@typescript-eslint'],
  parserOptions: {
    sourceType: 'module',
    ecmaVersion: 2020,
    extraFileExtensions: ['.svelte'],
  },
  env: {
    browser: true,
    es2017: true,
    node: true,
  },
  overrides: [
    {
      files: ['*.svelte'],
      parser: 'svelte-eslint-parser',
      parserOptions: {
        parser: '@typescript-eslint/parser',
      },
    },
  ],
  rules: {
    '@typescript-eslint/no-unused-vars': [
      'warn',
      {
        varsIgnorePattern: '^_',
        argsIgnorePattern: '^_',
      },
    ],
  },
}
``

Nothing even if you enable that rule explicitly?

still no errors, even when enabling the rule explicitly
rules: {
+    'no-undef': 'error',
    '@typescript-eslint/no-unused-vars': [


[Event Request] Codeunit 1535 "Approvals Mgmt." –  OnBeforeCheckPurchaseApprovalPossible

[Event Request] Codeunit 1535 "Approvals Mgmt." –  OnBeforeCheckPurchaseApprovalPossible
Can we please get a var before the Purchase Header variable at the event OnBeforeCheckPurchaseApprovalPossible (Codeunit 1535 "Approvals Mgmt.)
    [IntegrationEvent(false, false)]
    local procedure OnBeforeCheckPurchaseApprovalPossible(**var** PurchaseHeader: Record "Purchase Header"; var Result: Boolean; var IsHandled: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 44163.


Switch to use spring-cloud-incubator/spring-cloud-kubernetes

There now is a release we can use - https://github.com/spring-cloud-incubator/spring-cloud-kubernetes/releases/tag/v0.2.0.RELEASE

Acceptance tests failed, seems the config map and secrets aren't picked up


Introduce feature_flag for credhub

For issue 399
Add conditionals in all YAMLs files where we set spec properties for credhub, based
on the feature flag conditional(.Values.features.credhub.enabled).
Added  overrides for the base cf-deployment.yml file, based on the current v12.18.0 version.
Description
Adding the feature flag conditionals in all related places where we define spec properties for credhub. Also, because credhub is by default defined in the cf-deployment.yml, we need to remove some spec properties also there.
Motivation and Context
The reasoning is that in IBM, we do not use the credhub component. Also, I will expect in the future more use cases, where credhub requires to be feature_flag.
How Has This Been Tested?
I deploy this current PR branch in an IKS cluster two times, the first with the feature_flag disable, the second one with the feature_flag enable. Both deployments were successful, and I was able to push applications.
Types of changes

[ ] 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 change)

Checklist:

[ ] My code has security implications.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@qu1queee Thanks for the PR! Could you resolve the conflict, please?

Working on this, I was on holidays during the end of last week,

I had an issue with credhub disabled and CATS enabled. It's fairly simple to fix. I'll push a commit to fix it here. Other than that, it worked fine! Thanks again.


Capabilities granularity too low

Most existing capability-based systems have either of the following issues.

Too low granularity of capabilities (an app can access network, but actually should be allowed to access e.g. just several OSI 4 or higher protocols, have limited bandwidth, shouldn't have access to any OSI 3 or lower information, etc.)

Too high granularity (e.g. SELinux is super complex which is contra-productive as it's therefore quite often ignored or quite incorrectly configured)

To solve this, capabilites shouldn't be fix, but rather shall be a turing-complete executable code/assembly (imagine Linux BPF JIT). Then one can provide a standard library with low-grained capability-building-blocks (like e.g. Android does) and allow for fine-grained specification in all scenarios.
How do you want to approach this granularity/complexity issue in WASI?

My rough idea is that Mandatory Access Control (MAC) is out of scope for WASI, at least for now. That is, at the point of resolving a filesystem path or configuring a network socket or otherwise obtaining a new resource handle, the host environment may be permitted to apply additional rules to determine if access should be granted, such as SELinux or other systems. As you say, this can be pretty complex.
For filesystem support, WASI currently has a directory-oriented capability model. Wasm code can be granted access to a directory, providing it access to the contents of that directory. This access can be restricted to being readonly or other things, but there's no finer-grained path filtering currently.
For networking support, my rough idea (mentioned here) is that we could introduce a kind of capability which represents a set of sockets that can be created. For TCP-like sockets, this might look like a set of address (source and destination), port (source and destination), and protocol tuples that application code might create and configure a socket on.
My rough idea for both of these is to look for sweet-spot solutions that work for the majority of cases while still being really simple, and leave the more specialized cases to host/environment-specific mechanisms outside of WASI. However, this may also be a result of my lacking experience with BPF-style filtering -- to me, it sounds more complex, sounds like functionality that's only needed in highly specialized circumstances, and any time you add a new turing-complete mechanism to an overall system in a security-relevant area, my generic experience is that you have to be very very cautious.
However, if someone who has more experience with BPF or similar mechanisms wanted to make a writeup showing how it would work for WebAssembly, it'd be a great topic for the CG subgroup to discuss.

@sunfishcode I don't understand how capabilities are in scope for WASI. Could you clarify this? APIs don't enforce capabilities, implementations of those APIs do.

As an example, let's say we have TCP-like sockets. We want to restrict the WASM to connect() only to a single address. If you're running on Linux (most all of us are), you just put the runtime in a cgroup and set iptables rules on that cgroup. The connect() command will fail on everything but the specified address. But this has nothing to do with the API itself. This is entirely enforced by the host OS. Where the host OS doesn't provide such capabilities, the runtime can add them. But it doesn't impact the API.

Continuing the discussion here now that we have a dedicated repo.


Consider to make plugins configurable

Don't need for now, can consider create similar task in future


Consider core dns in the preflight DNS check

Since now coredns it is a real alternative for DNS server in Kubernetes I would like to be able to run sonobuoy without modifying default labels.

@pipo02mix - we use DCO signoff checker on our repos.  Could you amend your commit with --signoff
/cc @liztio for review as you wrote this section

I have screwed it up doing the sign-off. For some reason, I could not sign only last two commits. I close this in favor of a new PR


Email context

#1611

Automated message from Dropbox CLA bot
@paxapy, it looks like you've already signed the Dropbox CLA. Thanks!

I don't understand the first commit -- it doesn't seem to actually reuse the function?

yes, sorry, thats because it was done before rebasing. there was change that made logic too complex to reuse it (that realm thing)
I can squash these two commint into one If it will be more readable

Yeah, makes sense, I think squashing the adding of the new function and the use makes sense; it's probably worth keeping the refactoring for add_settings as its own commit.

Merged as 8c7ed80281b6d9c4857bb119a54bf5f882b34651 and ff1e97603d81f97b9daaea9006328bc86b33381a, thanks @paxapy!  Note that I cleaned up the commit messages and history; please be more careful about putting things like import changes into the commit where those changes are needed, and writing more extensive commit messages.


DHCPv6, replace domain name option with domain search list option

Should fix the remaining issues from #2336.

Many thanks, looks good ❤


Input's should support placeholder color

Feature Request
Input theming has an option for fontColor, but that changes both the color of the entered text and the color of the placeholder. We have a requirement for the placeholder text being a different color than the input text.

versus

Or the placeholder should default to some sensible color as I'm not sure there are a lot of scenarios that require different placeholder colors within the same app.


Support for managed OS and Data disks

It looks like currently, this uses one storage account per VM provisioned?
That causes scale problems since an Azure subscription is limited to 250 storage accounts.
It seems perhaps it would be pretty simple to support Azure Managed Disks for OS and Data with minor alterations to this plugin, which would eliminate the storage account problem.
I'm hoping you can comment on whether this has been investigated, or seems reasonable.  If I've misunderstood how it works you might save me some time attempting to add the functionality :)

@stefangordon - no need to attempt to add it yourself - stay tuned, it'll be in the upcoming release

Hey @jasonbw thanks! I'm going to toss you a follow up via email with some non-public details.

@stefangordon - sure


Fix incorrect aggregation in case that GROUP BY contains duplicate column names

Which issue does this PR close?

Closes #1854 .
What changes are included in this PR?

Add HashAggregateExec::output_group_expr that provides the GROUP BY columns with indices that correctly correspond to the schema of the RecordBatchStream created by this ExecutionPlan.
Use HashAggregateExec::output_group_expr in DefaultPhysicalPlanner when planning a LogicalPlan::Aggregate. (The latter is planned as two HashAggregateExecs and the second one needs to correctly use the output columns of the first as input.)
Add test csv_query_sum_crossjoin to datafusion/tests/sql/aggregates.rs that checks against regressions from the correct behavior.

Are there any user-facing changes?

The added HashAggregateExec::output_group_expr is marked as pub. As this is only an addition, it does not break any existing public API. (The added function could also be marked pub(crate) or pub(super), but this did not seem in line with the rest of the methods that HashAggregateExec exposes.)

@alex-natzka looks like there is a minor linter formatting error that needs to be addressed.

@alex-natzka looks like there is a minor linter formatting error that needs to be addressed.

Woops, that's right. Apparently the formatting was off in hash_aggregate.rs. Ran cargo fmt, this should do the trick.

@houqp I force-pushed the branch again with corrected formatting. Could you re-approve the workflows when it's convenient for you?

Thanks @alex-natzka


CIL v24 supported py and np versions

We previously followed:
https://numpy.org/neps/nep-0029-deprecation_policy.html#support-table
We should look at this:
https://scientific-python.org/specs/spec-0000/
I would suggest:
python:

3.10
3.11
3.12

numpy:

1.23
1.24
1.25
1.26

We are responsible for building all out plugins to match this list with the exception of astra-toolbox. This still only has up to py 3.10 so I would suggest we change
https://github.com/TomographicImaging/CIL/blob/7632209f0ed756ce4258782af4c2c531b34c1501/recipe/meta.yaml#L42
to:
test:
  requires:
    - astra-toolbox           # [ py<311 ]

and document the versions we have fully tested.

Numpy 1.26 is the 1st that supports py3.12. So I propose the following combinations:
python:
  - 3.10
  - 3.10
  - 3.10
  - 3.10
  - 3.11
  - 3.11
  - 3.11
  - 3.11
  - 3.12
numpy:
  - 1.23
  - 1.24
  - 1.25
  - 1.26
  - 1.23
  - 1.24
  - 1.25
  - 1.26
  - 1.26
zip_keys:
  - python
  - numpy

closed  by #1765


Use official AWS SDK for Java instead of jets3t library

jets3t library seems to be unsupported.
https://github.com/aws/aws-sdk-java

+1
Would also be nice to upgrade our hadoop version to one that supports s3a, which uses aws-java-sdk instead of jets3t.

Actually not using the SDK raises many issues. Especially It is a best practice to not use credentials whenever possible and using roles / instance profiles instead.
This is impossible with the current implementation.

You can use instance profiles. The credential chain is here https://github.com/druid-io/druid/blob/master/aws-common/src/main/java/io/druid/common/aws/AWSCredentialsUtils.java

thank you. that wasn't quite clear from the docs

Closing in favor of #4289


Enhanced and Fixed Logitech Harmony

I started with what @enriquez had done, fixed a few more things, changed it to use the new HAP API's, and enhanced.

LogitechHarmonyAccessory now bases off HAP's Accessory and utilizes new Service and Characteristic API's

Uses the loop that @enriquez added to update the state of which activity is "On"

Turning activity "Off" now just changes the activity to the "Power Off" activity

Properly responds to HomeKit set calls (waits for Harmony to finish and completes callback with updated state)

Added extra handling for connection loss

Could you pull latest from master and fix conflicts? Probably just a package.json thing. Also will need @enriquez or @madmod's signoff as I have no idea how this accessory works :)

Yeah, my last changeset was supposed to handle any conflicts, but git still got scared because a line was added right next to a line that was removed lol.

Anyone else using the Harmony platform that can test this PR? The code looks great to me but I don't own any devices :)

I'd be happy to test if I knew how. Have any instructions for how I can get this pull request pulled locally for testing?

Sure i would lime to try it

On Oct 20, 2015, at 3:57 PM, Nick Farina<EMAIL_ADDRESS>wrote:
Anyone else using the Harmony platform that can test this PR? The code looks great to me but I don't own any devices :)
—
Reply to this email directly or view it on GitHub.

git remote add kraigm https://github.com/KraigM/homebridge.git
git fetch kraigm
git checkout -b feature/Harmony kraigm/feature/Harmony

Thanks for the pr, I will give it a try with my Harmony

Just tested. Fixed the crashes, and I was able to successfully activate an activity and then turn it off from the El Gato Eve app. Haven't yet figured out how to make Siri do it (it just googled "turn on Apple TV" when I tried that), but it works.

"Turn on Watch TV" worked, so maybe I just need to change the name of my Apple TV activity or something.

I'm having an error with node-stringprep when I install the packages so I can't test it until I get it running on a PI tonight.

I do get the node-stringprep error mentioned by @madmod, but it doesn't appear to actually prevent anything from working.
  node-stringprep Cannot load StringPrep-0.7.2 bindings (using fallback). You may need to `npm install node-stringprep` +0ms
  node-stringprep Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at bindings (/Users/fitzage/Source/homebridge/node_modules/node-stringprep/node_modules/bindings/bindings.js:76:44)
    at Object.<anonymous> (/Users/fitzage/Source/homebridge/node_modules/node-stringprep/index.js:10:39)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32) +1ms
  node-stringprep Cannot load StringPrep-0.7.2 bindings (using fallback). You may need to `npm install node-stringprep` +0ms
  node-stringprep Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at bindings (/Users/fitzage/Source/homebridge/node_modules/harmonyhubjs-client/node_modules/node-xmpp-core/node_modules/node-stringprep/node_modules/bindings/bindings.js:76:44)
    at Object.<anonymous> (/Users/fitzage/Source/homebridge/node_modules/harmonyhubjs-client/node_modules/node-xmpp-core/node_modules/node-stringprep/index.js:10:39)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32) +0ms

@KraigM What's the StringPrep thing? should that be added to the global package.json?

I don't use it but harmonyhubjs-client does use it.  I have not had any issues with it myself.  I did go ahead and update to the officially released version of the package, since the repo admin finally approved/merged released @enriquez's fix.  Maybe that will help?  Also try deleting your node_modules before npm install

I updated and removed my node modules, but I still get the same stringprep error.

Do you get the error on npm install or is this happing at runtime? If runtime, do you get any errors/warnings on npm install?

I did not see any errors during npm install that I noticed. This is a runtime error, but it doesn't prevent anything from working as far as I can tell.

Just out of curiosity, try running "npm install node-stringprep" at the root of homebridge and see if that fixes it.  If so, a work around could be to add that dependency to homebridge to enforce this.
The only thing special I noticed is that that package is used with several diff versions throughout the harmony packages (nested) and also it has to be node-gyp rebuilt so it could act diff on diff platforms.  What platform are you using?

I did try manually installing it. No change.
I'm running on Mac OS.

On Oct 21, 2015, at 4:22 PM, KraigM<EMAIL_ADDRESS>wrote:
Just out of curiosity, try running "npm install node-stringprep" at the root of homebridge and see if that fixes it. If so, a work around could be to add that dependency to homebridge to enforce this.
The only thing special I noticed is that that package is used with several diff versions throughout the harmony packages (nested) and also it has to be node-gyp rebuilt so it could act diff on diff platforms. What platform are you using?
—
Reply to this email directly or view it on GitHub.

I'm running mac as well but I didn't have full debug info on (I used 'node app.js').  I get the same message but it doesn't effect me either.  Seems to work just fine.  Also it was reported in #131 so it doesn't seem to be unique to my changes.

I finally got my RPi setup (I have been running it via an IDE on my mbp retina) and I have it working on both.
SideNote: I learned the hard way that you have to use a different hub config if you try using a different computer (even if you only run one at a time).  iOS must keep track of MAC Address' or something and deny hub connection if it does not match.

Ok then I am good with merging if you think it's ready @KraigM

Yeah I think its good to go.  Should hopefully fix some of the other issues written up in the issue tracker.  If not or it introduces new issues, I would be happy to help.

Awesome.


Fix docstring typos

Codecov Report

Merging #172 (72ad26d) into main (2a55f4e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #172   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines          829       828    -1
=========================================
- Hits           829       828    -1

Impacted Files
Coverage Δ

meilisearch_python_async/task.py
100.00% <ø> (ø)

meilisearch_python_async/index.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


StatusBar is still light-content after use on iOS

Issue Description
StatusBar remains light-content when predefined types are used.
Steps to Reproduce / Code Snippets

Use one of the predefined types.
Do not have <StatusBar /> in parent
Notice it's still light-content after it's gone

Expected Results
Perhaps give a prop to enable or disable the change or remove completely.
Additional Information

React Native version: 0.40.0
react-native-dropdownalert version: 2.5.0
Platform(s) (iOS, Android, or both?): iOS

A workaround:
//...
render() {
  return (
   <StatusBar barStyle={this.state.barStyle} />
  )
}
//...
  onClose(data) {
    this.setState({
      barStyle: 'default'
    })
  }
// ...

This is also affecting me on Android. The status bar remains the colour of the alert that has been dismissed.

hi @michaelduminy I updated the workaround above. I'm thinking either dropping support to change the StatusBar style and/or I can toggle back to default styles onDismiss for predefined types.

In my opinion, the component should remember the barStyle before and revert to that value afterwards.

hi @insraq That would be ideal but StatusBar does not provide a way to access the current barStyle.


odo 'hangs' after using a cluster that's no longer accessible

/kind bug
What versions of software are you using?

I was using odo successfully, then installed CRC, used it for a bit, and then stopped the CRC cluster.
Actual behavior
Tried to use odo again and every command (even ones I would have thought are 'local') takes >1min to respond. No errors, but every time you think it's hung and not going to return, then finally does. Even things that should fail fast (e.g. current dir is not a component) hang for a while.
Expected behavior
I realize it's likely something underlying that is still trying to connect to my stopped cluster, but I didn't intentionally connect odo to it, nor is there any indication that's what the problem is: it just looks like odo performance is awful and it's my experience with odo that I associate with the problem.
There should be:

a shorter timeout
when there is a long delay, there should be some indication that the command is trying to connect (so I don't think it's hung)
when there's a timeout, there should be something that tells me how to stop trying to connect to that cluster

@deboer-tim mentioned odo seems to hang when cluster is unreachable, even for error cases like The current directory does not represent an odo component, I tried considering odo push command as a base case

case-1 : odo push, cluster is reachable
It works fine, no hang

case-2: odo push, cluster not reachable, no local config data/devfile present in the folder
odo hangs for quite a while and gives error  The current directory does not represent an odo component. Use 'odo create' to create component here or switch to directory with a component

Ideally in this case odo should return instantly with error without hang or delay.

case-3: odo push, cluster not reachable, devfile.yaml/env.yaml present in the folder

In this case, a little delay is justified as odo is trying to reach cluster, but when i run with verbose enabled before trying hitting openshift API's it hangs for a while.
In a nutshell, odo hangs for a while when cluster in not reachable. I found out the reason is while initializing the commands  few command initialization calls to IsCSVSupported, which tries to connect with cluster and odo seems to be hanged.

Around 12 secs delay i got on my system witj IsCSVSupported call
[adisky@localhost odo]$ odo push --v 5
In IsCSVSupported  2020-12-10 15:11:31.759876225 +0530 IST m=+0.043293748
In IsCSVSupported  2020-12-10 15:11:34.817076826 +0530 IST m=+3.100494440
In IsCSVSupported  2020-12-10 15:11:37.889947183 +0530 IST m=+6.173364822
In IsCSVSupported  2020-12-10 15:11:40.961679592 +0530 IST m=+9.245097191
In IsCSVSupported  2020-12-10 15:11:44.034027999 +0530 IST m=+12.317445615
I1210 15:11:47.122253     819 util.go:432] path devfile.yaml doesn't exist, skipping it
I1210 15:11:47.122309     819 util.go:737] HTTPGetRequest: https://raw.githubusercontent.com/openshift/odo/master/build/VERSION
I1210 15:11:47.122541     819 util.go:758] Response will be cached in /tmp/odohttpcache for 1h0m0s
 ✗  The current directory does not represent an odo component. Use 'odo create' to create component here or switch to directory with a component

odo link, unlink and odo service commands using IsCSVSupported during command initialization, it is easier to move for link/unlink command but with odo service commands we are using to differentiate help and flags.
https://github.com/openshift/odo/blob/master/pkg/odo/cli/service/create.go#L524

odo link, unlink and odo service commands using IsCSVSupported during command initialization, it is easier to move for link/unlink command but with odo service commands we are using to differentiate help and flags.
https://github.com/openshift/odo/blob/master/pkg/odo/cli/service/create.go#L524

This sucks. And it's a piece that I added. :disappointed:
We faced a similar issue earlier https://github.com/openshift/odo/pull/3825#issuecomment-694866119. This check for CSV support is my mistake. We were earlier working with the understanding that if the user is working on a cluster that supports Operators, we will not show anything related to Service Catalog in the help output. That assumption is no longer valid, and we have to fix this.

We decided to remove IsCSVSupported  call during command initialization, we will update the help message with all the options available.


Populate rundata in all feature tests.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 46.471%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
586

Relevant Lines:
1261

💛  - Coveralls

Going to abandon this PR for now and split rundata to its own generated file, as discussed.


Standardize OpenClarity repo structure, hygiene, documentation and remove copy pasta

To improve the developer experience and long term health of the OpenClarity project we should invest in some standardisation around repo management, and have unified front for users and developers to navigate the project. Some things we think should be improved/added:

repo for managing common workflows and other common configurations (too much copy and pasta right now)
repo template for creating new repos with all the basics ready to go
standard template/design for READMEs etc
standard documentation style/format? perhaps a docs.openclarity.io site?

Thanks for filing this issue, Sam!
First things first, for Cisco employees, I would suggest reviewing the OSPO's docs on releasing open source projects.
The "Requirements" and "Best Practices" sections include some guidance and examples to get started with.

* repo for managing common workflows and other common configurations (too much copy and pasta right now)

For organization-level, the .github repo serves as an inheritance point for some GitHub application configurations as well as community health files, like CONTRIBUTING.md, and issue/pull request templates.
The GitHub official docs for this are here: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file
Here are some examples of org-level configurations:

Allstar: https://github.com/openclarity/.github/tree/main/.github/allstar
CODEOWNERS: https://github.com/openclarity/.github/blob/main/.github/CODEOWNERS (docs)
settings.yml: https://github.com/openclarity/.github/blob/main/.github/settings.yml (docs)
stale.yml: https://github.com/openclarity/.github/blob/main/.github/stale.yml (docs)

For development workflows, I would suggest taking a look at kubernetes-sigs/release-utils.
My team (SIG Release) maintains that project and leverages it for most of our other projects.
Of note in that repo is magefile.go, which is built on Mage (a Golang-based build tool, which has some likenesses to make).
There are a few simple targets that will do things like:

Run tests
Verify boilerplate headers for files
Dependency checks
Linting (via golangci-lint)
go build

The mage/ package in kubernetes-sigs/release-utils gives some more examples of what one could do with mage.
So yes, I'd agree that we could benefit from some instrumentation of common workflows here

repo template for creating new repos with all the basics ready to go

What would you want to see out of a template repo?

standard template/design for READMEs etc

Same question as above.

standard documentation style/format? perhaps a docs.openclarity.io site?

We currently have a website for OpenClarity here: https://openclarity.io / https://github.com/openclarity/openclarity.io
I'll make a few suggestions here:

use Hugo as a static generator
leverage Hugo modules, replacements, and mounts to import content from multiple repos: https://gohugo.io/hugo-modules/configuration/

An example config snippet might look something like this:
module:
  imports:
    - path: github.com/openclarity/apiclarity
      mounts:
      - source: docs
        target: content/docs/apiclarity
    - path: github.com/openclarity/kubeclarity
      mounts:
      - source: docs
        target: content/docs/kubeclarity
    - path: github.com/openclarity/functionclarity
      mounts:
      - source: docs
        target: content/docs/functionclarity

What that config snippet is saying is:

import {api,kube,function}clarity repos
map those repos' docs/ directory to docs/{api,kube,function}clarity on the website

Then we run some sync job in the background to republish the site if docs/ for any of the sites change.
Let me know what you think about these!

What would you want to see out of a template repo?
Same question as above. (for the README)

I think a template repo would lay down the basic foundations/layout for a project (we might need multiple templates one for go projects/other project types), including things like:

the docs directory with a landing page and an example document
a starting magefile/Makefile with some of the basic targets already implemented even if empty (build, lint, test, clean)
a README template with a ToC, a couple of placeholders to indicate what to put there (like  ), an empty Why/What section, and then standard Contributing and License sections
some standard/starter workflows which have lint, test, build, publish steps even if the steps are empty (if we standardise on a mage/Make targets these should be able to be filled out for most projects)
for go projects we could include a template go.mod as a starting point, and even a hello world main.go so that the targets have something to build and show working even if you've only just cloned the template

Opened a separate issue for Code of Conduct: https://github.com/openclarity/.github/issues/3

(Flagging this as the canonical tracking issue: https://github.com/cisco-open/.github/issues/3)


Mark repo as experimental

Hi @ghostdogpr!
Thanks for creating those badges! That was definitely missing.
I think it would be better to mark this project as experimental. Is it ok?

Sure, I was hesitating about this project actually. Feel free to update it the way you want in the future. I put some descriptions of the stages here: https://github.com/zio/zio/wiki/Project-Stages

Hm, it looks that I don't have permissions to merge it. Could you merge this PR?


Metrics inside a dictionary are not properly moved to GPU

🐛 Bug

The following code WORKS:
self.accuracy = Accuracy()

The following code DOES NOT WORK (throws CPU error):
self.metrics['accuracy'] = Accuracy()

Please reproduce using the BoringModel and post here

https://colab.research.google.com/drive/1oLE2Ts4AkQwd2oLSaz8qNvFdiygyvgrZ?usp=sharing
To Reproduce

Expected behavior

Move metric to proper device (GPU) whether assigned to self.some_metrics or self.all_metrics['some_metric']
Actual behavior
--> 113         self.correct += torch.sum(preds == target)

RuntimeError: Trying to pass too many CPU scalars to CUDA kernel!

Environment
COLLAB

CUDA:

GPU:

Tesla P100-PCIE-16GB

available:         True
version:           10.1

Packages:

numpy:             1.18.5
pyTorch_debug:     False
pyTorch_version:   1.6.0+cu101
pytorch-lightning: 1.0.4
tqdm:              4.41.1

System:

OS:                Linux
architecture:

64bit

processor:         x86_64
python:            3.6.9
version:           #1 SMP Thu Jul 23 08:00:38 PDT 2020

Additional context

I put the Metrics in a dict, so I can use the following code:
for metric_name, metric in self.metrics.items():
    self.log(f"{metric_name}/{phase}_step", metric(predictions, targets))

You should use torch.nn.ModuleList or torch.nn.ModuleDict
This is not a PL issue. Torch does not detect submodules in lists and dicts.

Thanks, that was indeed the issue!


Add schema assignation for tests

Feature idea.
When new test run gets uploaded to the test it requires schema definition.
Schema definition does not changes a lot from test runs that comes from JMH.
JMH+ Horreum Jenkins plugin usage can be simplified a lot if Horreum will link one schema to all test runs in the test.
So the usage of it for performance tester would be :
Add plugin to the pipeline and create a new test for it in Horreum, instead of wrapping the data additionally with schema id.
Describe the solution you'd like
So I propose to add a tab in the test menu that will show the schemas used by the test and additionally it will contain schema setter for all test runs in the same test

Hi @dupliaka Is the idea here that we could define a "default" schema for a particular test, and if data is uploaded without a schema defined, then apply that default schema?
If an upload defines a schema, we should apply that schema to the uploaded data?
In terms of preference; upload schema -> default schema -> no schema


Align extension scanning

This PR fixes #144444
Align extension scanning between Extensions UI and Extensions Runtime (Extension Host)

Extract extension scanning, validating and nls replacement into INativeExtensionsScannerService
Use INativeExtensionsScannerService for scanning in Desktop and Remote extension managements and extension hosts
Represent invalid extensions in Extensions UI
Remove prompting for invalid extensions while scanning in Desktop Extension Host in Dev mode

@alexdima This is still in progress. Most of the scanning code is refactored, aligned and re-used. I also did some testing and it is working as expected. Only behavioural change I have done is following:

Removed prompting for invalid extensions while scanning in Desktop Extension Host when in Dev mode. Instead these invalid extensions are represented in UI.

For eg., following prompt is removed

in favour of following UI

I still have to work on unit tests and will complete the PR after that.
It would be great if you can take a look and provide early feedback, also play around a bit to test.
Thanks

Added tests !!!

PR is ready for review !!!

@alexdima Moved caching into ExtensionsScanningService. Caching is being leveraged only by Extension Hosts Scanning (Desktop & Server) for now (this milestone). New addition is caching in Server.
I did not capitalise this yet in Extensions Management. I would want to do some good testing before enabling it as it involves some good number of scenarios to test like, install, uninstall etc., Hence I would like to target this in next milestone.
Can you please review the remaining changes and provide feedback so that I can merge the PR?

Merged 🎉


setData works only for values inside image

setData works only for values inside image

Yes, but you can use setCropBoxData + setCanvasData to instead it.

It is called workaround, i do not love it

Em 11/05/2015, às 22:48, Fengyuan Chen<EMAIL_ADDRESS>escreveu:
Yes, but you can use setCropBoxData + setCanvasData to instead it.
—
Reply to this email directly or view it on GitHub.


Publish security audit

Can you publish the security audit for falcon in an easy to find place?
https://github.com/envoyproxy/envoy#security-audit

Yes, we are planning to do this before releasing 0.18.0 - we are waiting for an update from the auditors to add the fixed PR links to the document, if they don't reply promptly we'll find another way to have such information in the same place.

/milestone 0.19.0

Ready to publish!

/assign @mfdii

Please drop a note in slack when it's published! And a blogpost on it!

where is it published?
can you also create advisories for the issues via the github security tool?
https://github.com/falcosecurity/falco/security/advisories
cc: @leodido

It's not published yet @caniszczyk - @mfdii was assigned at the last Repo planning call

@mfdii is in charge of publishing the reports.
me and/or @fntlnz are going to create the advisories soon.

friendly ping on this @mfdii :)

Yep yep. Working on the blog drafts now.
On Wed, Dec 11, 2019 at 9:41 AM Chris Aniszczyk<EMAIL_ADDRESS>wrote:

friendly ping on this @mfdii https://github.com/mfdii :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/falcosecurity/falco/issues/886?email_source=notifications&email_token=AAM74DKNEWYTHKLZF7ESJS3QYD3YPA5CNFSM4I7EKMQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGTLVTA#issuecomment-564574924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM74DJB5FGIGUKJXWADGKDQYD3YPANCNFSM4I7EKMQA
.

Draft done. Will publish 2019/12/16


get-bc not working

OK  I have to do some other things, but I can't get get-bc to work on my mac.
It took me a while to get gclang to work, see f42fbca27377507e0727bdd272d2027a54f1698e
but now I canna get the bitcode.  To reproduce:
cd whole-program-llvm/test/test_files

CC=gclang make many

get-bc main

The problem seems to be that filesToLink is [] @loicgelle

@ianamason Is the problem specific to binaries?

not sure. i'm testing it now on linux. took a while to get my vagrant box up and coughing.
will look into it momentarily.

No seems to not work pretty uniformly.  try some of the simple examples in
whole-program-llvm/test/test_files
CC=gclang make archive
get-bc libfoo.a

CC=gclang make many

get-bc main

etc

@ianamason Working on that issue. Bitcode from libraries + objects are extracted fine on Mac, the problem must lie in the method for reading/writing .llvm_bc sections to objects and libraries.
As for binaries, I am not surprised. Look here at line 81: https://github.com/SRI-CSL/whole-program-llvm/blob/master/wllvm/compilers.py

OK I will let you fix the issue.  Yes executable binaries get their section from the linker.
But they still contain sections.

@ianamason No problem for me to build/extract objects/libraries in a Linux Docker machine. Probably you did not install llvm tools (like llvm-ar / llvm-link) in your Vagrant box

@ianamason My bad, I had to change something in the way the output filename is generated. Checkout the latest commit.

Nope still doesn't work.
vagrant@vagrant-ubuntu-trusty-64:/vagrant/whole-program-llvm/test/test_files$ CC=gclang make many
gclang foo.c -c
gclang bar.c -c
gclang baz.c -c
gclang main.c -c
gclang foo.o bar.o baz.o main.o -o main
vagrant@vagrant-ubuntu-trusty-64:/vagrant/whole-program-llvm/test/test_files$ get-bc main
2017/06/28 16:58:52 There was an error reading the contents of main. Make sure that the 'objcopy' command is installed.
vagrant@vagrant-ubuntu-trusty-64:/vagrant/whole-program-llvm/test/test_files$ ls -la main.bc
ls: cannot access main.bc: No such file or directory
vagrant@vagrant-ubuntu-trusty-64:/vagrant/whole-program-llvm/test/test_files$ extract-bc main
vagrant@vagrant-ubuntu-trusty-64:/vagrant/whole-program-llvm/test/test_files$ ls -la main.bc
-rw-r--r-- 1 vagrant vagrant 1788 Jun 28 16:59 main.bc
vagrant@vagrant-ubuntu-trusty-64:/vagrant/whole-program-llvm/test/test_files$

@ianamason I was saying that I fixed objects and libraries, not binaries. I've just fixed binaries for *nix only and pushed, you can test.
For Mac still not working for some strange reason. Even though I doubt it is related to that, I will try to clean the mess of the extractSectionDarwin function.

OK gotcha. Still getting the same behaviour, though :-(

@ianamason My version of objcopy is 2.28. Can you run objcopy --dump-section .llvm_bc=/dev/stdout main and give me the output? Mine is:
/root/go/src/gllvm/.foo.o.bc
/root/go/src/gllvm/.bar.o.bc
/root/go/src/gllvm/.baz.o.bc
/root/go/src/gllvm/.main.o.bc

Yes that is what I was doing. My version is 2.24 and it hasn't got that feature :-(
vagrant@vagrant-ubuntu-trusty-64:/vagrant/whole-program-llvm/test/test_files$ objcopy --dump-section .llvm_bc=/dev/stdout main
objcopy: unrecognized option '--dump-section'

@ianamason We have to make a choice then. Either we revert back to legacy support, which probably means a messy extracting function like the one for Darwin, or we precise the need for a working version of objcopy.

I think reverting is better. 14.04 is a pretty popular OS.

Why do we have to deal with legacy dinosaurs... Fine then.
Can you try get-bc for Mac? It's working for me in fact

Yes it seems to work on my mac now.

@ianamason Fixed.

Yep looks good here too.

👍


[Visual requirements - ADF - Azure data factory] Controls are getting disappeared after resizing to 200% Azure data factory window.

User Experience:
User will find difficulty to interact with the control if that control is getting disappeared as user won't get the actual UI and also will miss the functionality of such control.
Test Environment:
Application Version: 1.16.0-dev
Build Number: 20200921.1
Pre-Requisite:

Set to 200% from System Display-> Advance system settings.
Navigate to the storage expoler.exe and select it.

Repro Steps:

Launch Azure Storage Explorer app.
Navigate and select Add data factory control at left panel.
Now, navigate to various control like Account, Subscription, etc. on Azure data factory window.
Verify each control after resizing to 200%.

Actual Result:
Controls(Account, Subscription, etc.) are getting disappeared after resizing the screen to 200% on Azure support page and due to user won't be see such control and won't be interact with that control too.
Expected Result:
Controls(Account, Subscription, etc.) should not get disappeared after resizing the screen to 200% on Azure support page so that user could easily interact with such control.

Regarding this one, I believe we already have it fixed by putting a scroller bar aside since v0.1.4 and could close it.

Our part in fixing this ended up being fixing the disappearing vertical divider bug.


Skip building when certain paths/file in a PR hasn't changed.

It would be really nice if there was an ability to skip building a pr if a particular path or file hasn't changed in a PR.
Right now the prbuilder builds everytime a pr is opened against a branch but it would be nice if there was a way to tell it to build only when a particular path/file changes.
And unforunately this doesn't work in conjunction with the existing option("polling ignores commits in  certain paths") on the git plugin.

There would need to be more logic around how a build gets triggered than there currently is.  I am looking to refactor the trigger logic anyways, so then this would be much easier to add.

I've done it. I need it really fast, and I just finished the implementation. I will submit a pull request in the next 2 days. I've used janinko/ghprb but I will fork from this repo and add the changes. If it get's accepted you can use it in the same way as Include/Exclude regions from the SCM/git section.

Did this enhancement make it into a PR? I would also love to see this functionality.

It looks like there is an API call to get a list of files that have changed.  This would require that every time we check a PR we also call out to get the list of changed files.
https://developer.github.com/v3/pulls/#list-pull-requests-files

@DavidTanner is the extra API call a problem?

Fixed with #293


:bug: Test cases for #390

Creating this as a draft (will not yet submit it) including test cases for #390.
Unfortunately it will currently not work due to test problems (cf. #418).

@ascheman could you sign all the commits?


Open instruction page when 'Connect' clicked and extension not installed

Currently when 'Connect' is clicked and extension is not installed Github page is opened.
Instead, we need to show a detailed instructions page on how to install developer version of the Web Client (from sourc3, NOT Github)
This means that the build of Web Client should be (for now) uploaded to a new repo 'Sourc3 Releases'

Download extension page desing https://www.figma.com/file/3UUMChv0qaOOkHoddpEFgA/SOURC3?node-id=2701%3A419

Checked


VC2013 C++ Compile

nanovg_gl.h#L1444-#L1525
EX.
#L1447
static NVGcontext* nvgCreateGL3(int flags);

#L1492
static void nvgDeleteGL3(NVGcontext* ctx);

#L1502
static int nvglCreateImageFromHandle(NVGcontext* ctx, GLuint textureId, int w, int h, int imageFlags) {...}

#L1518
static GLuint nvglImageHandle(NVGcontext* ctx, int image) {...}

to compile without problems I had to make static struct and the void of this section, otherwise the compiler returned an error saying that they were already defined.

The GL backend is a bit special, as it follows the one-header-file library model (idea stolen from the stb_* libraries).
The idea is that in one file you define NANOVG_GL_IMPLEMENTATION before including the header, and it will also include the implementation, not just the prototypes. Then on each other case you include just the header.
The backend contains implementations for multiple GL versions. For example if you're using GL2 backend, you can define NANOVG_GL2 once in your build settings.
I hope that makes sense.

@memononen
Could you explain it a bit more in depth?
I have a viewer that have some basic implementation of drawing funcs using nanovg, with a header app.h (where #define NANOVG_GL3_IMPLEMENTATION happens)
And for a derived class that defined in another header derivedApp.h, if there is a derivedApp.cpp exist and include derivedApp.h, the compiler will report sth like:
nvgDeleteGL3 already defined in xxx.obj
nvgCreateGL3 already defined in xxx.obj

#define NANOVG_GL3_IMPLEMENTATION should be in the implementation file
not in header.
On Sat, May 25, 2019 at 8:06 PM X.ZhaoMa<EMAIL_ADDRESS>wrote:

@memononen https://github.com/memononen
Could you explain it a bit more in depth?
I have a viewer that have some basic implementation of drawing funcs using
nanovg, with a header app.h (where #define NANOVG_GL3_IMPLEMENTATION
happens)
And for a derived class that defined in another header derivedApp.h, if
there is a derivedApp.cpp exist and include derivedApp.h, the compiler
will report sth like:
nvgDeleteGL3 already defined in xxx.obj
nvgCreateGL3 already defined in xxx.obj
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/memononen/nanovg/issues/199?email_source=notifications&email_token=ABIBXSGIXD2OCKBWAFZGUDLPXFWZ5A5CNFSM4A4B5AG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWHVRUA#issuecomment-495933648,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIBXSHFKR5QAH3TZGOEKRDPXFWZ5ANCNFSM4A4B5AGQ
.


Register sizeof functions for Numba and RMM

Makes sure that sizeof functions are registered for Numba DeviceNDArrays and RMM DeviceBuffers.

[ ] Tests added / passed
[ ] Passes black dask / flake8 dask

@cjnolet, I don't know if this will fix the issue we saw today, but it's possible it might. Would you be able to test this and let me know? 🙂

It looks like black is slightly unhappy.
Do we want to include tests for things like this?  I might defer to @jcrist for an unbiased opinion.

Would testing this require GPU access? I don't have access to a GPU, and we don't on CI either, so I'm inclined to leave tests out unless it's likely they'll be run somewhere.

Yes both would require a GPU to test.
Leaving tests out would be my inclination as well. Though I don’t have strong feelings about this if they are desired.

I've pushed a fix for black. Please let me know if there is anything else 🙂

This looks good to me, but I have no way to test it. @jakirkham if you've verified it fixes your issue feel free to merge.

Thanks all! Was able to run the following on a machine with a GPU using this change.
In [1]: import dask

In [2]: import dask.sizeof

In [3]: import rmm

In [4]: import numba

In [5]: import numba.cuda

In [6]: rb = rmm.DeviceBuffer(size=10)

In [7]: na = numba.cuda.device_array(shape=(10,), dtype="u1")

In [8]: dask.sizeof.sizeof(rb)
Out[8]: 10

In [9]: dask.sizeof.sizeof(na)
Out[9]: 10


Register WSL without importing

Current state for if you want to back up or restore WSL os

Export your current Kali WSL distribution to a backup file:
wsl --export kali-linux D:\backup\kali-linux.tar

Restore the tar file
wsl --import kali-linux "D:\Virtual Machines\kali-linux" D:\\backup\kali-linux.tar --version 2

or restore vhd file (extracted from tar or from old pc)
wsl --import kali-linux "D:\Virtual Machines\wsl-kali" "D:\Virtual Machines\wsl-kali-linux\ext4.vhdx" --version 2 --vhd

Explanation:
wsl --import kali-linux "<new empty folder>" "<old vhd location that will be copied to the new location>\ext4.vhdx" --version 2 --vhd
Any better way to restore the vhdx file without it coping it again to new folder like unused --register?

Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs

/feature

How about this option?
--import-in-place

How about this option?
--import-in-place

Sounds good
I just don't want to copy 70GB any time I import the WSL after format


Outdated README?

README reads
Easy and flexible extensions for the Eloquent ORM (Laravel 5.3).

Shouldn't it be saying 5.4 now?

Yeah, can create a PR easily ;)


[node-identity:concerns:authentication] EmailAndPassword

Acceptance criteria

[ ] An approach is chosen after alternatives examined
[ ] Unit tests exist and pass
[ ] ADR created

Realizing I didn't meet the criteria, I'm reorganizing the tickets to add testing to the initial batch of code after the fact.