Traceback because of "No module named 'testcloud'"

bash-5.0$ rpm -q tmt
tmt-0.11-1.fc31.noarch
bash-5.0$ tmt
Traceback (most recent call last):
  File "/usr/bin/tmt", line 7, in <module>
    import tmt.cli
  File "/usr/lib/python3.7/site-packages/tmt/__init__.py", line 3, in <module>
    from tmt.base import Tree, Test, Plan, Story, Run
  File "/usr/lib/python3.7/site-packages/tmt/base.py", line 16, in <module>
    import tmt.steps.provision
  File "/usr/lib/python3.7/site-packages/tmt/steps/provision/__init__.py", line 11, in <module>
    from tmt.steps.provision import vagrant, localhost, podman, testcloud
  File "/usr/lib/python3.7/site-packages/tmt/steps/provision/testcloud.py", line 6, in <module>
    import testcloud.image
ModuleNotFoundError: No module named 'testcloud'
bash-5.0$

@happz this needs to be fixed on our side :) for now, but let's keep it here

we  need to install also tmt-testcloud

I don't think it has to be fixed on our side - we can add a workaround. If I install the official tmt RPM and it crashes this way, I am not the one who's supposed to fix it ;)

@happz sorry, it has to be workaround on our side (for now) :)

Yes, the minimal install is not working. Fixing this in #177.


Mac version has broken cursor movement keyboard shortcuts

On OS X 10.9.5, JDK 8u40:

Word-left & word-right (usually CMD-LEFTARROW / CMD-RIGHTARROW) does not work.

If you attempt to use word-left or word-right, the DOWN arrow stops working (although UP still works).

To recover DOWN arrow, have to use mouse to click elsewhere in the editor pane.

Same under Linux :-( In most cases that I watched this behaviour, I was switching back from another application (via keyboard). Reason might be some focus stealing.

Hello guys, Thanks for feedbacks.
@kittylyst Can you try this pre-release https://github.com/asciidocfx/AsciidocFX/releases/download/v1.3.7-alpha/AsciidocFX_Mac.dmg
I wonder if it will solve the problem

@lefou Can you test latest master in Linux environment?

@rahmanusta Confirmed fixed for me on the pre-release.

That is great! Thanks @kittylyst

Looks like the issue is gone. Thanks!

Thank you @lefou  and @kittylyst . You can use/try AsciidocFX version 1.3.7-RC1.


Use a task for handling IPv6::SendMessage requests to reduce stack utilization.

The change looks fine to me, but I am just worried that the Message class keeps getting bigger and bigger each byte increase will be multiplied considerably. Maybe there is a better way to handle those internal parameters? Maybe at least a union for fields that aren't used simultaneously?

@nibanks, I agree the Message class could use some cleanup.  Let's file an issue to track this and revisit it in a separate PR.


Question: Atomic update of multiple files

Hi,
Does littlefs support atomic update of multiple files?
If not, what would be the best approach to achieve that with littlefs?
Kind regards,
Thomas

Hi @thomas-ot, littlefs does not support atomically updating multiple files.
You may be able to get what you're looking for with a directory rename, however this would atomically update all files in the directory which may not be what you're looking for.
What exactly are you looking to achieve? Most filesystem consider files as separate atomic units. You may be able to group all of the data you are trying to update into a single file.

Hi @geky,
I need to make updates to multiple files resilient to power loss.
It is not an option to group the data into a single file.

littlefs doesn't provide an operation like that. It only handles atomic updates for individual files or directories.
One option would by to use a lock file. Create the lock file before updating the files, and remove the lock file when you are done. If a power-cycle occurs you can detect the lock file and try to fix any out of date files.


How to set line space?

How to set line space?

set crossAxisAlignment and runSpacing in Wrap widget.
return Wrap(
  crossAxisAlignment: WrapCrossAlignment.center,
  runSpacing: 30.h,
  children: breakEquation.parts,
);


Adding license to the repo

Hello, thank you for sharing your implementation with the community.
Could you please add a license (such as an MIT license) to this repository?
Thank you.

yes, sure, I added the same APACHE 2.0 license as original SASRec repo.

Thank you so much for your quick response!


Rest API for creating IoT Edge Device

Is there any rest API endpoint for creating new IoT Edge device ?
We need to create a new edge device as a part of automation and since there is no az cli support for raspberry pi we will need the rest API...
Thanks

@suhas9844 Can you please provide us with the URL of the Azure Doc you are having issues with? We look forward to your reply.

@SumanthMarigowda-MSFT I was talking about this doc ... https://docs.microsoft.com/en-us/azure/iot-edge/how-to-register-device

@suhas9844 Please try below and see if ithelps.

PUT https://{iot-hub-name}.azure-devices.net/devices/{edge-device-name}?api-version=2018-06-30

I haven't found an example for your scenario.

Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.

@suhas9844 Please try below and see if it helps.
PUT https://{iot-hub-name}.azure-devices.net/devices/{edge-device-name}?api-version=2018-06-30
I haven't found an example for your scenario.

I have found this link
[https://www.danielemaggio.eu/iot/iot-edge-rest-api/]
I have tried the PUT api they are specifying using the SAS token generating in azure portal
But i am getting
{
    "Message": "ErrorCode:ArgumentInvalid;BadRequest",
    "ExceptionMessage": "Tracking ID:085fde61ce3849c186d129d769197c35-G:5-TimeStamp:06/23/2020 12:18:32"
}

can someone help me in solving this issue


Installing LendingClub in Python 3.8

I am unable to install the LendingClub module.  I was on an older version of Python on Windows 10.  I upgraded to Python 3.8.  I upgraded pip.  I still get this error by using
pip install lendingclub or pip3 install lendingclub
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command
I'm new to coding and Python and muddling my way through :)

I know it's a little late but for anyone else wondering, it looks like this library was built for Python 2.x based on the setup data in setup.py
For me, the install is failing when trying to install pybars. In Python 3 I think the real library is pybars3. Not sure if that helps anyone.
I'm very interested in using this myself and plan on trying to port to python 3.x if not done already.

Yes, this library was written for Python2. I am also no longer actively maintaining this library. If anyone wants to take an attempt at upgrading it to Python3, I will gladly merge the pull request.


Python: Dictionary_Comprehension #3200

Description 📜
Added a video on Dictionary Comprehension.
Fixes #3200

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[x] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[ ] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[x] Python_Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

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

can u plz assign this to me

@apeksha235 Can we close this pr?

@kumarankm, i guess we can merge this. what do you think?

Yes, we can.
@adityabisoi you can merge this pr


support all mysql data types

Support all mysql data type and refine the document of datatype mapping.

Now, the ENUM/SET datatype  will cause failure while using MySQL CDC 2.0 shown in #371 .
As #387 shows, it's caused by JsonTableChangeSerializer ignored defaultValue, hasDefaultValue, enumValues of ColumnImpl in Debzium and there has been a PR debezium/debezium#2671 to fix it.
But actually, to simply fix it,  we only need to consider the fields enumValues, and it's ok to ignore the field defaultValue and hasDefaultValue.  So I think we can implement a custom JsonTableChangeSerializer that only serialize and deserialize the field enumValues to work around it before the PR debezium/debezium#2671 is merged into Debezium.
WDYT @leonardBang @Jiabao-Sun

@leonardBang

@luoyuxia
I think it's a nice enhancement to serialize enumsValues first.
It can solve the problem that the currently known Enum type is not supported.
Currently, I have not tested the type unsupported problem caused by the missing defaultValue.
If there is indeed a problem caused by the missing defaultValue, we can also consider using serializing tools like Kryo to serialize defaultValue before [debezium-2671] is released. The only concern with custom serializers is that we may not cover all possible types.
I think we can accept this PR first. @leonardBang What do you think?


Tizen 3 Sintel 4K stream error

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
2.5.14
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Custom
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Tizen 3 (Samsung 2017)
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
UE55MU6122, firmware version:180
What are the manifest and license server URIs?
manifestUri: 'https://storage.googleapis.com/shaka-demo-assets/sintel-widevine/dash.mpd'
com.widevine.alpha: 'https://cwip-shaka-proxy.appspot.com/no_auth',
What did you do?
Loaded and started the stream.
What did you expect to happen?
Stream goes up to uhd resolution, because the TV is capable of uhd, and there is enough bandwidth.
What actually happened?
Error when the stream changed to uhd resolution.

What actually happened?
Error when the stream changed to uhd resolution.

Can you please tell us what the error was?

Sorry, I forgot that.
The player did not throw an error, but the video did, which was error code 3 (VIDEO_DECODE_ERROR).
I read it's out of control of javascript, but with Tizen, I can't get to chrome://media-internals to get more information.

I don't know for certain, but I believe Tizen 3 is WebKit-based, and so wouldn't have chrome:// URLs.

https://developer.samsung.com/smarttv/develop/specifications/web-engine-specifications.html
According to this website, from 2017, Tizen is based on chromium.

I stand corrected!  But it's not a given that Samsung would enable those features in their build, so it's still not super surprising that chrome:media-internals doesn't work on Tizen 3.
We have a Tizen 3 device in our lab, so we should be able to replicate this.  We may not be able to get much more info, but we'll just have to try and see what we can see.
Thanks for providing all the necessary details in your report!

I've discovered something surprising.
First, I played the content on Tizen, using an automated playback test that forces low res.  It played fine.
Then, I did it again, but modified the config to force 4k.  It failed, as you reported.  Same results with the 1440p track.
When I played this same content on Chrome, I noticed that there was no 4k track in the UI at all.  Same for 1440p.
I did some more digging and discovered the same thing on both Chrome and Tizen: we don't have UHD keys in the license.
I'll work to fix this in the license proxy and see if that fixes playback.

After correcting the license proxy to return UHD keys, I'm getting 4k playback on Tizen with this content.  Thanks for reporting!


Is it required that equals and hashcode be implemented on id field only?

As in the documentation suggested by the Entity http://neo4j.com/docs/ogm-manual/current/tutorial/#graphid
Is this required as suggested in the documentation to have all classes inherit from an Entity which equals and hashcodes on the ID only? Or can I have my own equals and hashcode including any field?

@PhilAndrew,
In fact, you can use any style of equals/hash that you like, so long as it conforms to the standard equals contract (bidirectional, transitive, etc).
The example that you link to is a little misleading showing the use of ID. In fact if you do use ID, it is important to not that an object's hashCode will change on save. In general this should be ok, however there's a few cases where care must be taken. These are documented here:
http://neo4j.com/docs/ogm-manual/current/reference/#reference-graphid-annotation

Ok so the important point to know is that the ID can change from time to time. Then however that knowledge is used by me to do equals and hashcode is up to me. For my purpose, relying on id for anything seems like a bad idea as it doesn't act as object identity. a GUID would be more suitable for object identity and would be up to me.
I read through the documentation and I came up with a few questions.

How can I do a Cypher query and get the results back as objects?
If I make many multiple changes to my graph in memory, how can I persist back that graph in one single operation at the end to the database? I think I could save with a large depth number, but that doesn't seem clear on what would happen. Will it only save those changed fields or will it save down the entire graph if my large depth number is used?
Its likely that I am going to have a graph in memory which changes a lot and then I want to save it back.
It would be nice to be able to fetch just a particular graph of nodes along different paths to different depths along different paths, I mean, I may want to be able to pull down a customer and the customers orders but I don't want the customers emails. However the depth number is going to give me the customer and the orders and the emails.
I want to be able to restrict what comes back. That's related to 1.
Its likely I'm going to change my graph in memory in random small locations, if I do a save then as your documentation says its not going to save those locations which are not reachable by modified fields. (unless I add a large depth?). In any case, I want to be able to change my graph in memory here and there and then do a bulk update of it to the db.

If you annotate your domain objects and then do a session.query() or session.queryForObject() you will get back a response already mapped into these domain objects and their relationships.
 If they can reach each other through traversal in memory, the session's default behaviour is to save that. Whether this is one operation or several depends on the amount of changes being made. If you want to pull in a large graph in memory then you can save it back at various depths (overloaded on the save() method.

I do this every day in my own product. If you aren't happy with uniform depth loading you can just pull back the specific object graph you want through cypher (see the first point). We are looking at some annotation based approaches but these won't be appearing for quite a while.
I'm not sure your question is very clear. The OGM will detect changes in anything loaded through it and persist them. You can restrain the OGM from going down every path by setting the depth on save().

It's important to let the OGM do the heavy lifting for you. If you see performance problems we can then look into those but for most cases performance isn't an issue. That said if you plan on doing bulk/batch processing there are other tools like CSV import that can also work.

What motivated some of my questioning here in the area of "Relationship save cascading" where is a part of your documentation says "In this case, even though the movie has a reference to the actor, the property change on the actor will not be persisted by the call to save(movie). The reason for this is, as mentioned above, that cascading will only be done for fields that have been modified. Since the movie.topActor field has not been modified, it will not cascade the persist operation to the actor.".
Refer to:
Example 3.2. Relationship save cascading
http://neo4j.com/docs/ogm-manual/current/reference/
This indicates that when the movie is going to be persisted, even though the topActor object is reachable from movie the topActor fields won't be persisted because the topActor reference didn't change. Is my understanding correct?
However you said "If they can reach each other through traversal in memory, the session's default behavior is to save that." and also many other parts of documentation say basically the same thing that the behavior is that if the object is reachable then it will be persisted.
These two behaviors appear to be in contradiction to each other. That motivated my question 2 and question 4.

@PhilAndrew My explanation above is the correct behaviour.  You are right though that what is currently written in the documentation is wrong. If what is loaded in memory has been modified and is reachable from the entity in session.save(entity) then it will be detected and updated without you having to call all those changes.
I will update the documentation to close this. If you have any more issues with the behaviour you want to explore come find us in the neo4j-users slack channel or raise another issue :)


Regarding BPF Forms issues while including a Form Component Control.

Hi,
I wanted to know when will the next update come regarding this new feature.
I have to include a Form Component control in a form where BPF is used and is currently showing unexpected behaviors as mentioned in the document.
Is work going on on this issue of BPF and when can I expect the nearest update?
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 385e47fe-5e1a-edb0-6932-408621881a80
Version Independent ID: 0f3d2630-2e3e-e194-de9f-b4314e444694
Content: Edit table records directly from another table’s main form - Power Apps
Content Source: powerapps-docs/maker/model-driven-apps/form-component-control.md
Service: powerapps
Sub-service: mda-maker
GitHub Login: @Mattp123
Microsoft Alias: mspilde

Thanks for your comment, @krnaryal. This issue has been assigned to the doc author for review.

@krnaryal - Thanks for your feedback. For product-related feedback, visit Power Apps Ideas.
Vote for an existing request or submit a new one.
Closing this issue.


Reaction Method Spam

Reaction methods in views are being hit multiple times when the reaction is only emitted once.
The first time the app is run, the reaction will be received once. The second time the app is opened (after hitting onDestroy on the activity), the reaction will be received twice... 3 == 3, 4==4, so on.

I have found a solution to this i will get a hot fix in this weekend.

Thanks @nigelbro

@ptmr3  can you dug for me a bit in your application? I have confirmed that I do have a check in the flux class that checks if the class has already been added to the REACT_CACHE list. So there will never be a time more than one instance would be in the list at a given time.

I call an action in the onResume of my main fragment. When opening the application, the action gets called once. I have then validated that the action creator method and the store method is hit once. The emit reaction is called once. The react method in the view however is being called multiple times, corresponding to how many times the application has been opened

Hmm. Thats interesting. The only way this could happen is if this action is being called multiple times or an activity leak . Also I would shy away from calling actions in the onResume of a fragment as it can be called multiple time back to back which would also result in your action to be sent out more than once. The only way for the library to call out the method more than once is if the class is added to the cached ConcurrentMap object more than once. This however can not happen because when any view is added as a reactionSubscriber the method does a REACT_CACHE.containsKey(class) condition which will ignore and not re-add it to the map if it is already added. So at any given time the map only can have one instance of a class and its react annotated methods as you see why its impossible for the library to call the method more than once. which you can see here which is the emitReaction logic
for(Object parentClass : REACT_CACHE.keySet()) { 					for(Method method : REACT_CACHE.get(parentClass)) { 						if(reaction.getType().equals(method.getAnnotation(React.class).reactionType())) { 							HashMap<String, Object> map = new HashMap<String, Object>(); 							map.put(METHOD, method); 							map.put(CLASS, parentClass); 							map.put(REACTION, reaction); 							e.onNext(map); 						} 					} 				}

@ptmr3  I added an unregisterAllSubscribers() method that you can call in your main activity onDestroy. This will make certain that the library is not holding on to any context. With this change the library itself can not call the React methods of a class unless by user code.
build this snapshot compile 'com.github.nigelbro:fluxion:issue_6-SNAPSHOT'
and call the Flux.getInstance().unregisterAllSubscribers() in the main activity on destroy

fixed in v2.2


obsolete term names are not visible

http://amigo.geneontology.org/amigo/term/GO:0043234

also ideally the history link would take you here:
https://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0043234#term=history
since it might not be clear the a"change log" is  the place to go

actually this isn't an obsoleted term (which would have "replaced by")
It's a term merge, so it shouldn't require a "replaced by". So why does this secondary ID  have its own page? It should just go directly to the merged term shouldn't it?

This was caused when we changed how merging is treated in OWL, we haven't caught up with the amigo loading yet.
Yes, you are correct. We could have this redirect but it may be more transparent to clearly report this as a merged term and to show the replacement term?
Reported in #476, which was merged into #91 (the irony...), but I'm not sure a (ticket) merge was warranted here?

Yes, you are correct. We could have this redirect but it may be more transparent to clearly report this as a merged term and to show the replacement term?

I'm not sure. if a term is merged, going straight to the extant term with secondary IDs displayed isn't confusing? All the necessary info is there...


Unable to create user with mongodb as ORM

Using mongo the save for a user model fails with NoMethodError (undefined method saved_change_to_encrypted_password?' for #User:0x00007f81d8608ba8):`
This is on a brand new Rails 6.0.0 set up. I had to do a bundle exec rails g devise:install along with bundle exec rails g devise_token_auth:install_mongoid User auth.
Using postman to make a post request to /auth with the following params gives the attached stacktrace.
{
  	"email"<EMAIL_ADDRESS>  	"password": "password123",
  	"password_confirmation": "password123",
  	"name": "Kristy Skiles"
}

Looks like Mongoid doesn't support the new ActiveRecord API yet (https://jira.mongodb.org/browse/MONGOID-4528)

Version:

devise_token_auth (1.1.0).
Ruby 2.5.5 Rails
Rails 6.0.0-rc1

Rails Stacktrace: this can be found in the log/development.log of your API.

NoMethodError (undefined method `saved_change_to_encrypted_password?' for #<User:0x00007f81d8608ba8>):

devise_token_auth (1.1.0) app/models/devise_token_auth/concerns/user.rb:230:in `should_remove_tokens_after_password_reset?'
devise_token_auth (1.1.0) app/models/devise_token_auth/concerns/user.rb:236:in `remove_tokens_after_password_reset'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:429:in `block in make_lambda'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:201:in `block (2 levels) in halting'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:607:in `block (2 levels) in default_terminator'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:606:in `catch'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:606:in `block in default_terminator'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:202:in `block in halting'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:514:in `block in invoke_before'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:514:in `each'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:514:in `invoke_before'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:134:in `run_callbacks'
mongoid (7.0.3) lib/mongoid/interceptable.rb:132:in `run_callbacks'
mongoid (7.0.3) lib/mongoid/persistable/creatable.rb:118:in `prepare_insert'
mongoid (7.0.3) lib/mongoid/persistable/creatable.rb:23:in `insert'
mongoid (7.0.3) lib/mongoid/persistable/savable.rb:23:in `save'
devise_token_auth (1.1.0) app/controllers/devise_token_auth/registrations_controller.rb:42:in `create'
actionpack (6.0.0.rc1) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
actionpack (6.0.0.rc1) lib/abstract_controller/base.rb:196:in `process_action'
actionpack (6.0.0.rc1) lib/action_controller/metal/rendering.rb:30:in `process_action'
actionpack (6.0.0.rc1) lib/abstract_controller/callbacks.rb:42:in `block in process_action'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:135:in `run_callbacks'
actionpack (6.0.0.rc1) lib/abstract_controller/callbacks.rb:41:in `process_action'
actionpack (6.0.0.rc1) lib/action_controller/metal/rescue.rb:22:in `process_action'
actionpack (6.0.0.rc1) lib/action_controller/metal/instrumentation.rb:33:in `block in process_action'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:180:in `block in instrument'
activesupport (6.0.0.rc1) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:180:in `instrument'
actionpack (6.0.0.rc1) lib/action_controller/metal/instrumentation.rb:32:in `process_action'
actionpack (6.0.0.rc1) lib/action_controller/metal/params_wrapper.rb:245:in `process_action'
mongoid (7.0.3) lib/mongoid/railties/controller_runtime.rb:19:in `process_action'
actionpack (6.0.0.rc1) lib/abstract_controller/base.rb:136:in `process'
actionpack (6.0.0.rc1) lib/action_controller/metal.rb:191:in `dispatch'
actionpack (6.0.0.rc1) lib/action_controller/metal.rb:252:in `dispatch'
actionpack (6.0.0.rc1) lib/action_dispatch/routing/route_set.rb:51:in `dispatch'
actionpack (6.0.0.rc1) lib/action_dispatch/routing/route_set.rb:33:in `serve'
actionpack (6.0.0.rc1) lib/action_dispatch/routing/mapper.rb:18:in `block in <class:Constraints>'
actionpack (6.0.0.rc1) lib/action_dispatch/routing/mapper.rb:48:in `serve'
actionpack (6.0.0.rc1) lib/action_dispatch/journey/router.rb:49:in `block in serve'
actionpack (6.0.0.rc1) lib/action_dispatch/journey/router.rb:32:in `each'
actionpack (6.0.0.rc1) lib/action_dispatch/journey/router.rb:32:in `serve'
actionpack (6.0.0.rc1) lib/action_dispatch/routing/route_set.rb:837:in `call'
warden (1.2.8) lib/warden/manager.rb:36:in `block in call'
warden (1.2.8) lib/warden/manager.rb:34:in `catch'
warden (1.2.8) lib/warden/manager.rb:34:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
rack (2.0.7) lib/rack/etag.rb:25:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
rack (2.0.7) lib/rack/conditional_get.rb:38:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
rack (2.0.7) lib/rack/head.rb:12:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/callbacks.rb:101:in `run_callbacks'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/executor.rb:14:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/actionable_exceptions.rb:17:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/debug_exceptions.rb:32:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
railties (6.0.0.rc1) lib/rails/rack/logger.rb:38:in `call_app'
railties (6.0.0.rc1) lib/rails/rack/logger.rb:26:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/tagged_logging.rb:80:in `block in tagged'
activesupport (6.0.0.rc1) lib/active_support/tagged_logging.rb:28:in `tagged'
activesupport (6.0.0.rc1) lib/active_support/tagged_logging.rb:80:in `tagged'
railties (6.0.0.rc1) lib/rails/rack/logger.rb:26:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/request_id.rb:27:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
rack (2.0.7) lib/rack/runtime.rb:22:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
activesupport (6.0.0.rc1) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/executor.rb:14:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/static.rb:126:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
rack (2.0.7) lib/rack/sendfile.rb:111:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/host_authorization.rb:83:in `call'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:57:in `block in call'
activesupport (6.0.0.rc1) lib/active_support/notifications.rb:182:in `instrument'
actionpack (6.0.0.rc1) lib/action_dispatch/middleware/stack.rb:56:in `call'
railties (6.0.0.rc1) lib/rails/engine.rb:526:in `call'
puma (3.12.1) lib/puma/configuration.rb:227:in `call'
puma (3.12.1) lib/puma/server.rb:660:in `handle_request'
puma (3.12.1) lib/puma/server.rb:474:in `process_client'
puma (3.12.1) lib/puma/server.rb:334:in `block in run'
puma (3.12.1) lib/puma/thread_pool.rb:135:in `block in spawn_thread'

Environmental Info: Created a brand new application with just the user model.

So on a bit of further investigation, a quick fix for this would be changing this line to be if Rails::VERSION::MAJOR <= 5 || !respond_to?('saved_change_to_encrypted_password?')
Not sure if this is an acceptable change. If it is I can create a MR for it. Until this is sorted I have just overridden the method in my app/user.rb with the change.

Check #1328 way, it should be a cleaner way to ask that


[HOLD for payment 2023-02-13] [HOLD for payment 2023-02-10] [$1000] Profile : Infinite loading spinner appears choosing images with file names has space or special character

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to settings > Profile
Upload any image which has space or having brackets () in the image file name

Expected Result:
Able to upload without any issue
Actual Result:
Infinite loading spinner appears
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Version Number: 1.2.64-2
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/216393900-86df9390-229e-4ecd-aa56-826d8fff2e32.mov

https://user-images.githubusercontent.com/43996225/216393999-0ab8f66c-e86e-47d9-8022-dcf6b87c4393.mp4

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675312872492999
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011dbd8a1da41596b4
Upwork Job ID:<PHONE_NUMBER>104563200
Last Price Increase: 2023-02-03

Adding same response which I have added here https://github.com/Expensify/App/issues/14266#issuecomment-1415853647
Proposal
Associated PR seems to raise a regression where we won't able to reach out to Avatar Crop part and the infinite loader will remain on the screen after cleaning the filename.
Reason is uri will be undefined as the file object is overwritten here.
https://github.com/Expensify/App/blob/51f1a77e18f222806da32c5d6670d2de5267fa6f/src/components/AttachmentPicker/index.js#L39-L42
https://user-images.githubusercontent.com/14358475/216611655-e81806b3-9cb6-4670-b288-8aced226e179.mp4
To solve we need to make an order change
diff --git a/src/components/AttachmentPicker/index.js b/src/components/AttachmentPicker/index.js
index dddceb7cf7..dc6573e02c 100644
--- a/src/components/AttachmentPicker/index.js
+++ b/src/components/AttachmentPicker/index.js
@@ -36,10 +36,10 @@ class AttachmentPicker extends React.Component {

                         if (file) {
                             const cleanName = FileUtils.cleanFileName(file.name);
-                            file.uri = URL.createObjectURL(file);
                             if (file.name !== cleanName) {
                                 file = new File([file], cleanName);
                             }
+                            file.uri = URL.createObjectURL(file);
                             this.onPicked(file);

https://user-images.githubusercontent.com/14358475/216611547-b1dc061c-913d-4533-917d-17e4f3348759.mov
Context for me - https://github.com/Expensify/App/issues/14757

Monil is offline, so I will take over on this issue

@Pujan92 Can you please get a PR up ASAP? This is linked to a deploy blocker

Sure @thesahindia

@thesahindia @thienlnam
PR is ready for review.

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.65-2 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/14823

If no regressions arise, payment will be issued on 2023-02-13. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@thesahindia / @thienlnam] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@thesahindia / @thienlnam] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@thesahindia / @thienlnam] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@Pujan92] Propose regression test steps to ensure the same bug will not reach production again.
[ ] [@mateocole] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Keeping this open to pay out

Still need C+ and issue reported to apply to the upwork link!
https://www.upwork.com/jobs/~011dbd8a1da41596b4

@mateocole applied

Regression Test Proposal

Go to the profile page
Choose upload photo
Select any pic with special char in file name
Verify that it proceeds and loading spinner won't turn out to be infinite

try here @thesahindia

Ok thx!

@mateocole reporting bonus is pending

@mateocole reporting bonus is pending

@mateocole same(payment pending) for me.

@mateocole quick bump!

@thienlnam can you please reopen the issue as payment is pending here
cc: @mateocole

📣 @gadhiyamanan! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01b6fd34f946454a68

✅ Contributor details stored successfully. Thank you for contributing to Expensify!

Pinged Matt to take care of payment on this issue!


[Translation zh-cn] Shared > Udacity > ud893.html

Check out a review request at GitLocalize

@sotayamashita & @chikathreesix - would you please take a look!


Why is the tool including WebPack when creating the project?
Wouldn't it be more flexible if only Typescript is included and leave the decision over the other tools to the user?

Updated the extension with the ability for users to choose which template they want. Give it a try. (v1.1.4)

@Power-Maverick  Tested and it works phenomenally!


Remove $Changed from logical flow of emitter

Previously we were providing the ActionContext of the emitter to $Changed handlers.  The transaction was destroyed in this case so was not really useful.  Now we instead just provide metadata about the subject that triggered the change.
Also, the emitter was awaiting $Changed handlers if they were async.  There are advantages and disadvantages to doing this:

Advantage is that the logical flow is more deterministic and we track the promise as a normal part of node activity
The disadvantage is that the emitter blocks until an independent process completes

This commit makes it so $Changed handlers operate independently of the emitter.  Tests pass but effects will be subtle so will need to keep an eye on this.

see review comments in Discord - also reason for the failed testcase


{language}/*.json pathPattern not working

pathPattern: "./src/locales/{language}/*.json" (as demonstrated in example02)
File structure: src/locales/en/home.json & src/locales/fr/home.json, both containing a single k/v pair with a common "test" key
i("test") returns nothing, even when switching languages using switchLanguage.
Note that ./src/locales/{language}.json works perfectly (with the adapted file structure)
Also I make sure to rm -r "src/routes/inlang" whenever I change my config

@WarningImHack3r Thanks for creating the issue.
@NilsJacobsen and I are currently working on this exact issue. We have created a new pre-release 2.3.1 for it and will be testing it tomorrow with several repos. After that we will pin it as a newest version.
Test it with your use case by pinning this version in your inlang.config.js and give us feedback 🙂

Doesn't seem to work unfortunately :/<EMAIL_ADDRESS>

I will investigate it tomorrow, keep you updated here and try to provide a sample.
If you use i18next, we currently build a dedicated plugin for this, that will be similar to the inlang-plugin-json. So you can be sure, we find a solution this week.

@WarningImHack3r This problem should be fixed with the latest release and the version 2.
Additionally, the plugin-i18next has now been released.
Please reopen it if you find anything else.

Unfortunately, it still does not work with my config:
/**
 * @type {import("@inlang/core/config").DefineConfig}
 */
export async function defineConfig(env) {
	const { default: pluginJson } = await env.$import(
<EMAIL_ADDRESS>	);

	const { default: sdkPlugin } = await env.$import(
		"https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>	);

	const { default: ideExtensionPlugin } = await env.$import(
		"https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>	);

	return {
		referenceLanguage: "en",
		languages: ["en", "fr"],
		plugins: [
			pluginJson({
				pathPattern: "./src/locales/{language}/*.json",
				variableReferencePattern: ["{", "}"]
			}),
			sdkPlugin({
				languageNegotiation: {
					strategies: [{ type: "localStorage" }]
				}
			}),
			ideExtensionPlugin()
		]
	};
}

@WarningImHack3r I created a SvelteKit project with the same structure and configuration and could not get it to work either. We will try to fix this next week.

Well, now it works 😄
Check here and compare it with you project: https://github.com/NiklasBuchfink/inlang-plugin-json-24
The editor works now too: https://inlang.com/editor/github.com/NiklasBuchfink/inlang-plugin-json-24

What did you change to make it work? Removing the languages array and adding the standardLintRules in the config?

Oh, I had to precise the file name in the key path!!! Alright, thanks a lot!


OpenXR-based VR integration

In development...

Readily working on Windows. Disabled XR by default. Check readme. Working on OS X version in a branch.


feat: move v2/expenses from personal cards page to platform

Moved this to draft, will fix linting issues and unit tests and then set for review


Move sharded checkpoints into their own intermediate prefix folder

What does this PR do?

What issue(s) does this change relate to?

Before submitting

[ ] Have you read the contributor guidelines?
[ ] Is this change a documentation change or typo fix? If so, skip the rest of this checklist.
[ ] Was this change discussed/approved in a GitHub issue first? It is much more likely to be merged if so.
[ ] Did you update any related docs and document your change?
[ ] Did you update any related tests and add any new tests related to your change? (see testing)
[ ] Did you run the tests locally to make sure they pass?
[ ] Did you run pre-commit on your change? (see the pre-commit section of prerequisites)

Ok, @dakinggg, @mvpatel2000, I changed the PR so the user configures what they want the prefix folder to be. PTAL

Ok, @dakinggg, @mvpatel2000, I changed the PR so the user configures what they want the prefix folder to be. PTAL

Also, updated FSDP docs to reflect this change

alright @mvpatel2000, I thiiiink I have addressed all the feedback. PTA(nother)L

@dakinggg, you interested in squinting at the tests to make sure the remote tests are sufficient and I don't have to launch any manny tests?

Ok manual tests look good


Translation

Coverage remained the same at 93.91% when pulling 54e0e0d4609c1a3288806a198e2b3a8910833311 on translation into 56ef15a5cd20771bbf5bf5265473fd8a6a0fbcc3 on master.


Fix for Typescript build script error

Leaving the explicit paths in, I get this error:
$ npm run build

> functions@ build C:\Users\Nella\Documents\GitHub\dutchess-church\functions
> tslint -p tslint.json && ./node_modules/.bin/tsc

'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! functions@ build: `tslint -p tslint.json && ./node_modules/.bin/tsc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the functions@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Nella\AppData\Roaming\npm-cache\_logs\2017-12-10T01_49_04_598Z-debug.log

Here is the debug log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle functions@~prebuild: functions@
6 info lifecycle functions@~build: functions@
7 verbose lifecycle functions@~build: unsafe-perm in lifecycle true
8 verbose lifecycle functions@~build: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\Nella\Documents\GitHub\dutchess-church\functions\node_modules\.bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\Nella\bin;C:\Program Files\ImageMagick-7.0.7-Q16;C:\Python27;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\PuTTY;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files (x86)\Yarn\bin;C:\Program Files\nodejs;C:\Ruby23\bin;C:\Users\Nella\AppData\Local\Microsoft\WindowsApps;C:\Users\Nella\AppData\Local\GitHubDesktop\bin;C:\Program Files\Microsoft VS Code Insiders\bin;C:\Users\Nella\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Microsoft VS Code\bin;C:\Users\Nella\AppData\Local\Yarn\bin;C:\Users\Nella\AppData\Roaming\npm
9 verbose lifecycle functions@~build: CWD: C:\Users\Nella\Documents\GitHub\dutchess-church\functions
10 silly lifecycle functions@~build: Args: [ '/d /s /c',
10 silly lifecycle   'tslint -p tslint.json && ./node_modules/.bin/tsc' ]
11 silly lifecycle functions@~build: Returned: code: 1  signal: null
12 info lifecycle functions@~build: Failed to exec build script
13 verbose stack Error: functions@ build: `tslint -p tslint.json && ./node_modules/.bin/tsc`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid functions@
15 verbose cwd C:\Users\Nella\Documents\GitHub\dutchess-church\functions
16 verbose Windows_NT 10.0.17025
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v8.9.3
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error functions@ build: `tslint -p tslint.json && ./node_modules/.bin/tsc`
22 error Exit status 1
23 error Failed at the functions@ build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Removing the explicit paths from the script makes it run just fine. I thought when things were run as an npm script, you didn't need to give explicit paths. I'm in Windows, which probably matters here.

@inlined @mbleigh this is autogenerated from firebase init when we choose TypeScript as the language for the new project. Maybe we should change this in firebase-tools directly?

I'm trying to get ahold of a windows VM so I can dive into this better. The explicit path is very intentional; it means each project uses the (package) locally installed version of tsc so the developer can have some semblance of control over their tools.
I'd like to find a way to have:

A dependency on the locally installed version of tsc
A command that works on Windows
A command that isn't determined by the OS that was used to initialize the project (e.g. same command for Windows and *nix)

@inlined Update: running the command with yarn instead of npm works!
So, running yarn build builds the .js files just fine. Running yarn serve which in the package.json file uses npm run build fails.
Changing the npm run commands to yarn results in:
=== Serving from 'C:\Users\Nella\Documents\GitHub\KingstonChurchNg4'...

!  functions: Cannot start emulator. Error: Cannot find module 'C:\Users\Mark\AppData\Local\Yarn\config\global\node_modules\grpc\src\node\extension_binary\node-v57-win32-x64-unknown\grpc_node.node'

Sorry it took so long to get ahold of a Windows machine. This bug is fascinating. There's a few things at play here:

Windows does allow dot-relative paths in commands. This does the same thing as Unix and is highly recommended for security and predictability (If I had a nickel for every machine hacked when a program loading a local dll from the search path...)
Windows obviously doesn't use '/' as a path separator, though many scripting tools paper over this, like 'node run'
Unfortunately, 'node run' doesn't understand '&&' implies there are two commands and only fixes up the first command we run.

We'll do a proper fix in an upcoming release of firebase-tools but in the meantime, you can fix it for your own project. We'll need to move the "&&" up a level to something that's not using slashes. So....

Change your package.json build command to be "./node_modules/.bin/tsc".
Add a lint command with "./node_modules/.bin/tslint -p tslint.json"
Change your firebase.json predeploy command to be "npm --prefix functions run lint && npm --prefix functions run build"

So to recap, after this fix your package.json should have the following snippet:
{
  "scripts": {
    "lint": "./node_modules/.bin/tslint -p tslint.json",
    "build": "./node_modules/.bin/tsc"
  }
  // other stuff
}

and your firebase.json should have the following:
{
  "functions": {
    "predeploy": "npm --prefix functions run lint && npm --prefix functions run build"
  }
}

This should give you a project setup that is predictable, safe, and cross-platform compatible.


Render arrows on oneway trails

Some trails are oneway and people expect to see this.

Mostly done in cc1878babe0f86e9e80fb38e12b1bbac602ad0f1.


Update cli-installcli.md To fix tips and note

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] If the changes in this PR is part of the next future release, make this pull request against the docs-staging branch which will be published at the next release boundary. If the changes in this PR are part of the current release, use the default base branch, master. For more information about branches, see https://github.com/zowe/docs-site/tree/master#understanding-the-doc-branches.

[x] If this PR relates to GitHub issues in docs-site or other repositories, please list in Description, prefixed with close, fix or resolve keywords.

Description (including links to related git issues)
Updated cli-installcli.md to fix missing tip and note tags.
:heart:Thank you!

@aimmta The build issues are for master branch build while this PR is targeted for docs-staging. I ran a local build and verified that there is no error, so these build messages can be ignored. : )


Take into account the Date Header when ratelimiting

This makes the internal ratelimiter take into account the date header to calculate an offset from the date header provided in the response from discord. A fair bit of the ratelimting code had to be rewritten + re-arranged to accommodate this change.
This addresses issue https://github.com/zeyla/serenity/issues/84

Going to close this PR and redo do it

This wouldn't have worked properly in the lib so all work on it has been scrapped


Incorrect JSON wrapper break JQ

Describe the bug
Commonly used Linux command line JQ tool doesn't work with JSON which prepared by sdp, because jq expect that wrapper is double quote.
Example of real GCP BigQuery DDL:
DDL:
$ cat sample_ddl.sql

CREATE  TABLE `dataset.table`
(
    Updated_Date           DATE   NOT NULL OPTIONS (description =Description1),
    Lead_Store_Id          INT64  NOT NULL OPTIONS (description =Description2),
)
PARTITION BY LeadCreatedDate
CLUSTER BY Lead_Store_Id

OUTPUT:
$ sdp -o bigquery --no-dump sample_ddl.sql
Start parsing file sample_ddl.sql

File with result was saved to >> schemas folder
[{'alter': {},
  'checks': [],
  'cluster_by': ['Lead_Store_Id'],
  'columns': [{'check': None,
               'default': None,
               'name': 'Updated_Date',
               'nullable': False,
               'options': [{'description': '=Description1'}],
               'references': None,
               'size': None,
               'type': 'DATE',
               'unique': False},
              {'check': None,
               'default': None,
               'name': 'Lead_Store_Id',
               'nullable': False,
               'options': [{'description': '=Description2'}],
               'references': None,
               'size': None,
               'type': 'INT64',
               'unique': False}],
  'constraints': {'checks': None, 'references': None, 'uniques': None},
  'index': [],
  'partition_by': {'columns': ['LeadCreatedDate'], 'type': None},
  'partitioned_by': [],
  'primary_key': [],
  'schema': '`dataset',
  'table_name': 'table`',
  'tablespace': None}]

JQ run:
$ sdp -o bigquery --no-dump sample_ddl.sql |  egrep -v 'Start parsing file |File with result was saved to ' | jq .
parse error: Invalid numeric literal at line 2, column 10

Followed JSON is OK:
[{"alter": {},
  "checks": [],
  "cluster_by": ["Lead_Store_Id"],
  "columns": [{"check": "None",
               "default": "None",
               "name": "Updated_Date",
               "nullable": "False",
               "options": [{"description": "=Description1"}],
               "references": "None",
               "size": "None",
               "type": "DATE",
               "unique": "False"},
              {"check": "None",
               "default": "None",
               "name": "Lead_Store_Id",
               "nullable": "False",
               "options": [{"description": "=Description2"}],
               "references": "None",
               "size": "None",
               "type": "INT64",
               "unique": "False"}],
  "dataset": "`dataset",
  "index": [],
  "partition_by": {"columns": ["LeadCreatedDate"], "type": "None"},
  "partitioned_by": [],
  "primary_key": [],
  "table_name": "table`",
  "tablespace": "None"}]

Here is few issues:

JQ expect that all values wrapped (None, False, True - as well)

JQ expect that wrapper will be double quote, not single quote.
JSON validator https://jsonformatter.curiousconcept.com/ said that points 1 and 2 are  RFC violation.

Incorrect parsing if table name wrapped by back quote: "CREATE  TABLE `dataset.table`". As you can see from output, parser keeped back quote at the beginning (but sometimes at the ending) of the table name:

 'schema': '`dataset',

@andy65535  Hi! This is because in stdout output is not JSON, but python dict (and because of that you see None, in JSON it must be null). If you want JSON - remove flag --no-dump and it will dump json to the file. I didn't thought about use case that someone need json in stdout :) I will add in next release flag --json to get output in stdout as json, not Python object.

thank you for replay!
I removed --no-dump and JSON now formatted as expected.
But, point 3 from my initial report still in place:
... TABLE dataset.table
parser leave back quotes in final JSON:
...
    "table_name": "table`",
...                                ^
    "dataset": "`dataset"
...                  ^

@andy65535 hi, I'm ready to kill myself for the my previous answer to you! first of all ))) you can get json output with python code ))  (I really need spend time on documentation improvement) - you can do it like this (sample added in README): https://github.com/xnuinside/simple-ddl-parser#get-output-in-json
second - to get output without artifacts like ` at the end you can use flag "normalize_names=True" like here:
https://github.com/xnuinside/simple-ddl-parser/blob/07f8b1f5c4c6b4aaf15a0fce4ce29fc8b213757a/tests/non_statement_tests/test_common.py#L49
so if you will run parser like:
result = DDLParser(ddl, normalize_names=True).run(json_dump=True, group_by_type=True)

You will get required output.
by default (without flag normalize_names=True) parser leave as is all symbols to get possible reconstruct DDL from parser output
Again, one more time SORRY for my wrong answer )
With CLI is not possible to use normalize_names flag - I will work in next release to update the CLI to keep all arguments & settings for parser


Prevent Password Recovery Spamming

@ritwikd
JS on the password recovery page can make vadweb be used as a server for spam. This may or may not be worth fixing

yikes

lol. nice to see you giving some attention to this criticial security issue!


index of gallery

Hello, how can i set index to open up gallery at specific image when the specific image is clicked? thanks!

remove controller and initial is working

Hi @MichalNemec I see you have found a solution, but you should also be able to achieve this using the controller as ImageGalleryController galleryController = ImageGalleryController(initialPage: 2);

hello, i need it reactive and i dont know if setting a controller like that is good option.
i need setstate to dynamically change the index for pageview and for this image gallery.
Awesome library tho! i hope the leaving jitter is only on android emulator, otherwise i appreaciate what you did!

@MichalNemec thank you very much :)
If you could give me an exact example of what you mean by "reactive", I may be able to help you with that. Maybe you just need to set galleryController = ImageGalleryController(initialPage: dynamicValue); every time?
Also not sure about the jitter on Android, can you maybe provide an example for that if it persists on a separate issue?


[feat][meta] Upgrade to jetcd to 0.7.5

Fixes #20308
Motivation
As described in #20308, we have test flakiness because of an issue in the etcd dependency. This PR upgrades etcd to fix the test.
I am not familiar with this integration. If there is any reason we should avoid this upgrade, please comment as much.
Modifications

Upgrade etcd dependency from 0.5.11 to 0.7.5
Update license files
Increase test timeout since it was failing during docker pull on my local machine
Replace code with the new methods/classes

Verifying this change
Tests passing should be sufficient.
Documentation

[x] doc-not-needed

Matching PR in forked repository
PR in forked repository: https://github.com/michaeljmarshall/pulsar/pull/49

/pulsarbot rerun-failure-checks

Codecov Report

Merging #20339 (35dccce) into master (426ad3e) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #20339      +/-   ##
============================================
- Coverage     72.93%   72.90%   -0.04%
+ Complexity    31973    31951      -22
============================================
  Files          1868     1868
  Lines        138663   138663
  Branches      15248    15248
============================================
- Hits         101133   101086      -47
- Misses        29484    29519      +35
- Partials       8046     8058      +12

Flag
Coverage Δ

inttests
24.18% <ø> (+0.06%)
:arrow_up:

systests
24.91% <ø> (+0.05%)
:arrow_up:

unittests
72.18% <ø> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ache/pulsar/broker/loadbalance/LinuxInfoUtils.java
43.65% <ø> (ø)

...ker/loadbalance/impl/LinuxBrokerHostUsageImpl.java
79.68% <ø> (-4.69%)
:arrow_down:

... and 66 files with indirect coverage changes

Error:  jetcd-core-0.7.5.jar: CVE-2020-15113(7.1)
Error:  jetcd-grpc-0.7.5.jar: CVE-20[17](https://github.com/apache/pulsar/actions/runs/4999756027/jobs/8959140598#step:10:18)-8359(9.8), CVE-2020-15113(7.1), CVE-2020-7768(9.8), CVE-2017-7861(9.8), CVE-2017-9431(9.8), CVE-2017-7860(9.8)

We may need new suppression rules @lhotari @michaeljmarshall

I'll add those.

@michaeljmarshall I am releasing 3.0.2, and the license check can not pass.
The dependency's version of animal-sniffer-annotations is 1.21 now, but the license of presto(trino) is still 1.19
see: https://github.com/apache/pulsar/actions/runs/6627474211/job/18019187456?pr=21435
Run src/check-binary-license.sh ./distribution/server/target/apache-pulsar-*-bin.tar.gz && src/check-binary-license.sh ./distribution/shell/target/apache-pulsar-shell-*-bin.tar.gz
  src/check-binary-license.sh ./distribution/server/target/apache-pulsar-*-bin.tar.gz && src/check-binary-license.sh ./distribution/shell/target/apache-pulsar-shell-*-bin.tar.gz
  shell: /usr/bin/bash -e {0}
  env:
    MAVEN_OPTS: -Xss1500k -Xmx1024m -Daether.connector.http.reuseConnections=false -Daether.connector.requestTimeout=60000 -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.http.retryHandler.class=standard -Dmaven.wagon.http.retryHandler.count=3 -Dmaven.wagon.http.retryHandler.requestSentEnabled=true -Dmaven.wagon.http.serviceUnavailableRetryStrategy.class=standard -Dmaven.wagon.rto=60000
    ARTIFACT_RETENTION_DAYS: 3
    GRADLE_ENTERPRISE_ACCESS_KEY:
    JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.8-1/x64
    JAVA_HOME_17_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.8-1/x64
    ACTIONS_RUNTIME_TOKEN: ***
    ACTIONS_RUNTIME_URL: https://pipelinesghubeus21.actions.githubusercontent.com/EXIZfX8ixSbQEfqDA00dMJrEtloTMSwjlUs9NqJqrTcJfd7NaR/
    UBUNTU_MIRROR: http://azure.archive.ubuntu.com/ubuntu/
    UBUNTU_SECURITY_MIRROR: http://azure.archive.ubuntu.com/ubuntu/
src/check-binary-license.sh: line 69: echo: write error: Broken pipe
src/check-binary-license.sh: line 69: echo: write error: Broken pipe
animal-sniffer-annotations-1.21.jar unaccounted for in trino/LICENSE
animal-sniffer-annotations-1.19.jar mentioned in trino/LICENSE, but not bundled

It looks like there are issues with the LICENSE/NOTICE.
Error: Process completed with exit code 2.

I saw this PR removed this line, I want to cherry-pick this PR to branch-3.0


Improve integration testing client (CodexClient) and json serialization

The current client used for integration testing against the REST endpoints for Codex accepts and passes primitive types. This caused a hard to diagnose bug where a uint was not being deserialized correctly.
In addition, the json de/serializing done between the CodexClient and REST client was not easy to read and was not tested.
These changes bring non-primitive types to most of the CodexClient functions, allowing us to lean on the compiler to ensure we're providing correct typings when doing integration testing. More importantly, a json de/serialization util was created as a drop-in replacement for the std/json lib, with the main two differences being that field serialization is opt-in (instead of opt-out as in the case of json_serialization) and serialization errors are captured and logged, making debugging serialization issues much easier.

I thought I saw some UInt256 serialization stuff in stint or somewhere. That could explain some of those issues

It could have been https://github.com/status-im/nim-eth/blob/master/eth/common/eth_types_json_serialization.nim#L26-L30. Importing these was definitely something I tried, but could not get working.

Sure! I'd be up for that sometime and like figuring out puzzles. It'd be nice to chat with you too, I don't think we've had the chance to. :)

Let's do it 💪  DM me in discord and we can setup a date/time.

P.S. My favorite serde library in Nim is msgpack4nim. It can serialize directly into or from an object making. This avoids allocations making it near the fastest one I've benchmarked. It rivaled flatbuffers which is famed for it's no-copy speed!

msgpack4nim looks pretty cool! After looking at all the places that we use serialization in codex, i do think a universal  solution should be implemented at some point. The issue that I see right now is that nim-chronicles uses nim-json-serialization due to our use of the json sink. I don't think it's possible to use a different serializer for a json sink, unfortunately. We could possibly remove the json sink (using formatIt instead), but I imagine we'll probably need to use the json log output for consumption in eg ElasticSearch or Loggly at some point.


feat(#48): mdlint

closes #48

PR-Codex overview
This PR updates the GitHub Actions workflow file markdown-lint.yml to include licensing information and configure markdown linting for the repository.
Detailed summary

Added MIT License information
Defined GitHub Actions workflow for markdown linting
Set up linting for the master branch
Specified concurrency and cancellation settings
Configured job to run on ubuntu-22.04 environment

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 9min)


[CCAP-408] Fixing date error message formatting

🔗 Jira ticket
https://codeforamerica.atlassian.net/browse/CCAP-408
✍ Description

📷 Design reference

✅ Completion tasks

[ ] Added relevant tests
[ ] Meets acceptance criteria

@spokenbird This is just a prototype of me fixing this. I made an override of date.html where the differences between the library and mine are:

removed the 3 th:block for the individual fields, and left only the 1 for the entire group
moved text--help above the error block vs below it to be consistent with the single inputs, for example

If you like this fix, there are two options:

Move this into the library itself
I change all our other date inputs to use this new override

I am agnostic on which is the correct choice here, but wanted to open a PR as a prototype for you to look at and help decide the direction.

@cram-cfa lets put it in the library, makes it easier to update in all places.

Cool, @spokenbird. That's what I was leaning towards, but wasn't sure if that was the correct fix! I'll do that and tag you in the PR over there once I do it.

New PR at https://github.com/codeforamerica/form-flow/pull/630


Manage uploads

fixes #454

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

Merged as 9a5179c460669bf67c76b82050a60ec703474cbf, after fixing a bunch of issues (original version had no security checks, only removed the Attachment without deleting the file, etc.).

Huge thanks for building this @paxapy!  I think a lot of folks will enjoy this extra control.


Add a hidden header to the hours list

WAVE alerted me back in the spring that it thought the "Hours today" box included a layout table:

After some digging, I realized the table was missing a header for the columns, which means we were presenting the library hours data in a purely visual manner (not WCAG 2.1-compliant). It's obvious to sighted users that these are hours for each library, but if you are relying on a screen reader, it would be confusing. Jared added a header that is hidden visually but accessible for screen readers.
Another oddity of this box was multiple <tbody> tags inside the the main table's <tbody>, which would have been confusing for any visually-impaired users navigating by screenreader. Jared fixed that as well.
Jared's styles were not screen reader-friendly, so I made a small adjustment. Everything looks great!
Well done, @jaredrcleghorn! 💯


implemented logic for using server timestamps (sourcetime and servert…

…ime)

PR Checklist

If your build fails due to your commit message not passing the build checks, please review the guidelines here.

Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[ ] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

I haven't seen that there are reviewers assigned meanwhile.
If appropriate don't apply my "suggestions" by the github functionality directly. The are not intended a a direct replacement for the commented lines. Just as snippets.


cargo install gcc installs gcc-shim in PATH

When you do cargo install gcc, you end up having gcc-shim in your path.
Given that it's used only for testing, probably it should be moved to some different plave and not being installed?

This crate isn't intended to be installed, but thanks for the report! (right now that binary is just used in testing)


Allow specifying a format for the label of a collapsed StructBlock

Currently, the label shown for a StructBlock's collapsed representation takes its content from the first sub-block of the StructBlock, which isn't always what you want. Add a new label_format meta option to StructBlock to allow customising this - e.g. label_format = "Profile for {first_name} {surname}"
Tested on bakerydemo by adjusting HeadingBlock in bakerydemo/base/blocks.py:
class Meta:
    icon = "title"
    template = "blocks/heading_block.html"
    label_format = "{heading_text} (size {size})"

(Prompted by a question on the #support Slack channel, which made me realise that customising this is currently a lot harder than it should be :-) )

Merged in 0380f01b245615e5ec2a818e5e8dabf20250223f


Update module golang.org/x/text to v0.21.0

This PR contains the following updates:

Package
Type
Update
Change

golang.org/x/text
require
minor
v0.20.0 -> v0.21.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

golang.org/x/sync
v0.9.0 -> v0.10.0


Table with scrollable tbody example

I really can't figure out how to have this working with a table with a basic structure:

        <row />

 <== virtual!
        <row />
        <row />
        <row />

Since I have the DOM element of tbody only after componentDidMount of table component ( therefore inside a component lifecycle ) how can I pass that down to the VirtualList?

Will virtualList use the containerEl to wrap elements? Thus avoiding the Warning: validateDOMNesting(...):
 cannot appear as a child of
.

Is there any working example with tables?
Thanks for the great work!

Hey @damianobarbati, I'll try to answer your questions:

You should be able to model your table component like so:

const MyList = ({
  virtual,
  itemHeight,
}) => (

	  ...

      {virtual.items.map(item => (

          ...

      ))}

);

I'm not 100% sure about the CSS of table and tbody elements, though, so there might be some complication there.

The container element is only used to calculate the scroll position.  If you don't have your
 inside a scrollable element, you can just leave it out.  As for your warning, can you post the full JSX of your component(s) ?

I don't have a working example with tables, unfortunately, but it's something I'd like to add.


Allow analysis scripts to read data.json

Closes #238.

Adds data to the latestRun object
Adds a files argument to the pyodide and webr mechanisms to allow us to populate arbitrary files

This sets the SIR analysis.R example go from
# posterior predictive check using the pred_cases generated quantity

install.packages(c("outbreaks", "bayesplot"))
library(outbreaks)
library(posterior)
library(ggplot2)

# same as data generation
cases <- influenza_england_1978_school$in_bed
n_days <- length(cases)
ts <- 1:n_days

# Extract posterior predictive checks
pred_cases <- as.matrix(as_draws_df(as_draws_rvars(draws)$pred_cases))[, -(15:17)]

bayesplot::ppc_ribbon(y = cases, yrep = pred_cases,
                      x = ts, y_draw = "point") +
  theme_bw() +
  ylab("cases") + xlab("days")

to
# posterior predictive check using the pred_cases generated quantity

install.packages("bayesplot")
library(outbreaks)
library(posterior)
library(ggplot2)

# load from data
d <- jsonlite::read_json('./data.json')
cases <- unlist(d$cases)
n_days <- d$n_days
ts <- unlist(d$ts)

# Extract posterior predictive checks
pred_cases <- as.matrix(as_draws_df(as_draws_rvars(draws)$pred_cases))[, -(15:17)]

bayesplot::ppc_ribbon(y = cases, yrep = pred_cases,
                      x = ts, y_draw = "point") +
  theme_bw() +
  ylab("cases") + xlab("days")

This will be even nicer if the data has some randomization to it, in which case re-running the same code in analysis would not recover the same data, but this would allow it to

I wonder if creating an additional copy of an in-memory JSON data file could further tax the scarce memory resource in the case of models with very large data, but the increased utility is probably worth the risk in this case. Especially as the copy doesn't have to exist until after the sampler's been run.

If this does become a problem, I think we could work around it by using FS.createLazyFile, but this would require extra machinery to 'host' the file at a URL, so I didn't tackle it here. If you know a good way, we definitely could do that sooner rather than later

To be clear--yeah, I don't have an answer here, or even evidence that it's going to be a problem; I suspect any such situation is either massively over-provisioned with data or is going to run into problems while still in the sampler phase, so realistically I'm not worried about it.
We can solve it if it's ever an issue.


Analyticalloopholes-Waikiki

I am not sure of a few things and if I am doing something wrong I want to get feedback about this device and give help in reference to a OTA trouble shoot solution. Thank you!

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

ID: 546e8122-8074-7a9f-0ec5-de27f6c27637
Version Independent ID: 827d1628-ecba-4f3f-51f2-0a5c9dd1424f
Content: Create a custom code analysis rule set in Visual Studio - Visual Studio
Content Source: docs/code-quality/how-to-create-a-custom-rule-set.md
Product: visual-studio-dev15
GitHub Login: @gewarren
Microsoft Alias: gewarren

@dannygriffin000 Are you trying to give feedback about the code analysis rule sets topic? It seems like you're referring to troubles with a mobile device, so I'm not sure how this issue got here.


⚠ Bofrost.lu has degraded performance

In 3261add, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 961 ms

Resolved: Bofrost.lu performance has improved in 9c8792d after 6 minutes.


[Feature Request]: Add support for removing importer annotations

🔮 Relevant Command
New command
🗂 Language Type
YAML
🔎 Request Details
Importer annotations are to ensure the same file content can be created by simple importer update.
But there are some cases where you want to use Importer once, and don't need to keep track of the importing target once imported.
It would be useful to have some command such as importer remove-markers, or importer marker remove subcommand.
Main use case would be for YAML, but other languages could perhaps benefit from this as well.

This should be the default behaviour when importer generate is used and the output file is not in the same directory. This is because Importer Markers are based on relative path, and the target file being on a different path would result in all those paths to be not resolvable.
Instead, when output file is in a different directory, the generated file should be able to track back which file was used to create it, by having such a comment at the top of the file.


Scaling opni alerting as a microservice OEP

Reduces complexity of gateway and improves resiliency of individual alerting component failures.

Will each operation be a separate service in the initial implementation?  What are the latency impacts if any of having each separated?  What are the failure modes if one of the microservices goes down?


Allow export of data

Allow the export of the raw data, e.g. as csv would be awesome. Even better: API for it

There's already an API to download the raw data for a specific tag. But, admittedly, its current JSON data format is not very re-usable. Let's add an option to have it export CSV data directly.

Let's add an option to have it export CSV data directly.

done (example: http://taghistory.raifer.tech/node/amenity/drinking_water?format=csv) and updated the documentation in 8920198
Still needs some kind of UI, though.


added installation instructions in the quick start docs

Updated the docs to include installation instructions for fluid packages.
This update is to close: #4260

@Flavyoo Thanks for the PR! I agree the docs are lacking info for adding Fluid packages to existing or new projects. This is a great start to that documentation. I think it might warrant its own section, linked from the quick start. @SamBroner @skylerjokiel what do you think?

Assigning to myself to handle the merge once the PR is approved.

@Flavyoo Merged! Thank you again for this PR!


Render functions in meta don't get composed into stories

Describe the bug
If you have a story file with a render function in the meta, this render function is used correctly when viewing the story in Storybook, but not when composed using @storybook/testing-react
To Reproduce
Steps to reproduce the behavior:

Create a new story file
In the meta for the story file, specify a render function
Compose stories for that file

Expected behavior

The render function in the meta should be used as the render function for the composed stories.

Closed by #103, should be available in 1.3.0! Thank you so much @TeaSeaLancs !


default boundary and fill_value for grid axes

[x] Closes #149

@rabernat What do you think of something like this?

Thanks @dcherian, I think this would be a great improvement for the xgcm workflow. In particular it makes it a lot easier to write more complex functions (with many .diff() and .interp() calls on the same grid object) in a general matter.
I have been writing budget reconstructions and this would enable me to do something like budget_ds  = calculate_heatbudget(ds, grid), very easily.

Should boundary be an Axis property?

Codecov Report

Merging #152 into master will decrease coverage by 0.43%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #152      +/-   ##
==========================================
- Coverage   88.49%   88.05%   -0.44%
==========================================
  Files           4        4
  Lines         617      628      +11
  Branches      133      133
==========================================
+ Hits          546      553       +7
- Misses         40       42       +2
- Partials       31       33       +2

Impacted Files
Coverage Δ

xgcm/grid.py
88.65% <66.66%> (-0.74%)
: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 cac66af...4471161. Read the comment docs.

Should boundary be an Axis property?

I think this would make sense. I like the approach of frontloading more of the configuration. The user would have to look into the model config once, figure out metrics, grid layout, boundaries etc and enter this at the creation of the grid object, then everything else becomes agnostic to the grid for the user. This will also make code highly general and reusable, the only thing needed to change is the grid object.

I like the implementation so far. I guess we would need some more tests and revise the docs? Thanks for the work @dcherian.

I like the implementation so far. I guess we would need some more tests and revise the docs?Thanks for the work @dcherian.

What's going on with the tests? Do we need a rebase here?

What's going on with the tests? Do we need a rebase here?

Yup, those should all be sorted out in the latest master

I rebased but won't work on this since I'm out of town. One of you should take over :)

using np.minimum is fine as of xarray 0.10.2 (for some reason I can't reply to that comment).

Now with fill_value as constructor kwarg. The xfailed boundary="interpolate" tests are unrelated and should be fixed in a different PR (I think).

None of the tests failed ?! This is ready for another review
=========== 3564 passed, 28 xfailed, 12 xpassed in 141.74s (0:02:21) ===========

The command "py.test xgcm -v --cov=xgcm --cov-config .coveragerc --cov-report term-missing" exited with 0.

Done. Your build exited with 1.

Merged master.

Also, sorry for having to wait so long @dcherian , I really appreciate all the hard work on this!

All done!

LGTM!

Dont forget an entry in whats-new.rst! I would also suggest to at least add one example of this feature in the docs. Thanks for the great work @dcherian, I was working with many models yesterday and really wanted this feature hehe.

I added #207 for the docrep issue.

LGTM, indeed!

!

Back from vacation. I'll merge now. But @jbusecke - you should feel free to merge stuff too!

But I am on vacation now 😆. Will do next time.

But I am on vacation now 😆. Will do next time.

Is a man really on vacation if he responds to github notification within 15 minutes? 🤣

Thanks! Enjoy your vacation Julius

Is a man really on vacation if he responds to github notification within 15 minutes?

And thats why I fled to the woods! Haha. But I am back in full, relaxed force.


fix(travis): don't test on go1.6

We don't need to test on golang 1.6 since even centos has moved
to golang 1.8.
# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)

# go version
go version go1.8.3 linux/amd64

Checkout the build time on golang1.9 guys, super fast!


Starting Docker Container Using Variables in Volume Mounting

Currently, in the application.yml, we can specify paths that to be mounted to run the container for each Shiny app. @fmichielssen mentioned on shinyproxy.io that we can specify environment variables such as $HOME in the path by docker-volumes: [ "${HOME}/path1:/container/path1" ], but as he pointed out,

they refer to the ShinyProxy’s process daemon, not the ShinyProxy logged-in user

this way doesn't really make the program dynamic.
So he suggested making variables like SHINYPROXY_USERNAME available in the context,

docker-volumes: [ "/host/mnt/${SHINYPROXY_USERNAME}/path1:/container/path1" ]

this would be very helpful for a lot of use-cases regarding user files.
If this is something you guys think is useful, I can investigate into it and try implementing it.
Another issue is in our Docker container, the Shiny Server is run under user 'shiny', and the volume mounted in could be owned by any logged in user(on the host), therefore, the Shiny app in the docker container does not have the right permission to access these files. I guess this is not really a shinyproxy issue, rather a volume related issue of Docker.
Thanks.

Hi Keqiang,
Good idea if you ask me!
Could be useful, maybe to indicate the scope using a prefix as in
${shinyproxy: SHINYPROXY_USERNAME}

to differentiate between environment variables as known to the Docker host vs. variables related to ShinyProxy properly speaking (?)
Best,
Tobias

Hi @tverbeke
I guess since the name is already prefixed by "SHINYPROXY_", it should be fine. It's just misleading because we are using the environment variable syntax to evaluate these variables. Maybe we should figure out a different syntax to refer specifically to these per-user variables such as for each app's configuration, use an option 'make-available: SHINYPROXY_USERNAME, SHINYPROXY_LDAP_CN' and then in other parts of this app's configuration, we can directly refer to these variables using another syntax rather than '${}'

Hi @keqiang,
A mechanism to choose which variables are exposed, sounds very good to me. And you are right that SHINYPROXY_ is already a prefix by itself.
Regarding the syntax, I believe it would be fine to use ${}, as this may already refer to more than just environment variables. The full list is given here:
https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html
And I think what we would be doing, is just adding one item to the list, the so-called 'shinyproxy user variables'.
Regards,

The application.yml file supports SpEL (Spring expression language) since ShinyProxy 2.0.4. This allows to mount user-specific volunes for Shiny apps. Small example:
    container-volumes: [ "/home/#{proxy.userId}/app/storage:/app/storage" ]


Alternative would be parsing the nuget.config but due to varying nuget rules across version we don't want
to get into parsing and understanding configs at this point (especially with the future being the
credentialProvider flow where nuget continues to own the nuget.config discovery and parsing)

:shipit:


Agrirouter dependencies not available on Gradle Build

Describe the bug
While integrating Agrirouter in our project we added the dependencies (api,impl,convenience) as stated in the readme.
On "gradle build" the dependencies (.jar files) are not available from the sonatype repo.
To Reproduce
Use a gradle project, add the following repo definition and dependencies and build it.
Repo definition:
maven {      	url "https://oss.sonatype.org/content/repositories/snapshots"     	mavenContent {             snapshotsOnly()         }     }
Dependendencies:
compile group: "com.agrirouter.api.lmis", name: "agrirouter-api-java-api", version: "0.0.1-SNAPSHOT", classifier: "jdk8", changing: true
compile group: "com.agrirouter.api.lmis", name: "agrirouter-api-java-impl", version: "0.0.1-SNAPSHOT", classifier: "jdk8", changing: true
compile group: "com.agrirouter.api.lmis", name: "agrirouter-api-java-convenience", version: "0.0.1-SNAPSHOT", classifier: "jdk8", changing: true
Expected behavior
Clean build without missing dependencies
Desktop (please complete the following information):
Building environment is Gradle 5.5.1 on Windows 10
Additional context
It seems that the underlying repo link to the JDK8 dependencies is mixed with the version of the JKD10 or JDK11 dependencies. Gradle tries to download from a link that matches the most recent updated resource in the given repo (in this case the JDK11 version) and just replaces the classifier with JDK8.
-> resource not found

@akurte Could you attach a simple example as project? I"ll check on it.

@saschadoemer The requested project is attached. It was created with Eclipse and Buildship. Neither a build in Eclipse itself or via PowerShell does work.

AgrirouterDependencyDemo.zip

@akurte As far as I could see the dependencies are not pushed to the directory correctly. There"s only one version which can be found. I"ll have a look at that and keep you up to date. This behaviour did change with the last build.

@akurte The deployment skripts for the last snapshot did fail - therefore the dependencies are currently missing. I will restart the logs and check on the outcome again - last error was a problem with the sonatype repos and access during the build.

@akurte Seems to be a short outage of the sonatype repo during the last deployment into the snapshot repo. With the lastest build the dependencies should be resolved correctly - but I currently not a different problem with the SNAPSHOT resolving. The parent POM is deployed multiple times, therefore I could be the case, that you retrieve the wrong version during dependency resolution. This would be fixed by using a release version - which does not exist or changing the deployment mechnism. I"ll check on that as well.

@akurte Nothing I can resolve today - current solution would be building the jars locally and install them to the local repo. I need to check multi release configurations for the maven release process to be sure about the deployment to sonatype.

@saschadoemer ok..we will download the latest jars from the sonatype repo and use them locally for now.
I hope this will be fixed soon ;)

@akurte Soon...
This night I was able to finish the release prep and pushed the artifacts to the maven central.

These are just the release candidates, but the shoul fix the error.

@saschadoemer works great..thanks
now the build is a lot easier ;)


Add blacklisting Sampler.

To allow for blacklisting of certain spans by a name pattern.

Codecov Report

Merging #2034 into master will decrease coverage by 0.00%.
The diff coverage is 81.25%.

@@             Coverage Diff              @@
##             master    #2034      +/-   ##
============================================
- Coverage     83.06%   83.06%   -0.01%
- Complexity     2251     2258       +7
============================================
  Files           319      320       +1
  Lines         10529    10545      +16
  Branches       1048     1051       +3
============================================
+ Hits           8746     8759      +13
- Misses         1446     1447       +1
- Partials        337      339       +2

Impacted Files
Coverage Δ
Complexity Δ

...opencensus/trace/samplers/BlacklistingSampler.java
80.00% <80.00%> (ø)
6.00 <6.00> (?)

...in/java/io/opencensus/trace/samplers/Samplers.java
100.00% <100.00%> (ø)
5.00 <1.00> (+1.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 5be7044...d67103a. Read the comment docs.


Fixed/mapper

[x] fixed mapper result republish.

Codecov Report

Merging #130 (6d9377a) into main (764d6e3) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #130      +/-   ##
==========================================
- Coverage   27.21%   27.10%   -0.12%
==========================================
  Files          49       49
  Lines        4112     4129      +17
==========================================
  Hits         1119     1119
- Misses       2893     2910      +17
  Partials      100      100

Impacted Files
Coverage Δ

pkg/service/topic.go
0.00% <0.00%> (ø)

pkg/statem/statem.go
6.44% <0.00%> (-0.17%)
: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 764d6e3...6d9377a. Read the comment docs.


Change CSS of iframe

I'd like to change the background color of the iframe that's containing my component, is there any way to do this in the current version?

The files option of the ReactPlugin should do it! https://github.com/carteb/carte-blanche#reactplugin-options

@simeg did you get it to work?

Thanks for the replies guys. but I have not got it to work yet. The file doesn't seem to load, I didn't have too much time to debug it. I'll keep you posted.


auto generate FPM/* files

[X] translation-status
[X] original-status
[x] package-info

Here the interface matching and the fallback to the default interface has been taken care of.
The location of the translation-status-page, original-status-page and package-info page has been hard coded to their respective files in the package-info package. @amitu review and let me know if it looks okay.


cmd/cover: failing TestFuncWithDuplicateLines

What version of Go are you using (go version)?

$ go version
go version go1.11.1 linux/amd64

built version:

root@ubuntu18:/go/src/golang/go# ./bin/go version
go version devel +cb8054a6b6 Fri Mar 15 04:15:59 2019 +0000 linux/amd64
root@ubuntu18:/go/src/golang/go#

Does this issue reproduce with the latest release?
No. The issue is there with the upstream master.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build733849470=/tmp/go-build -gno-record-gcc-switches"

What did you do?
git clone https://github.com/golang/go.git && cd go/src && ./all.bash
What did you expect to see?
all the tests should have passed
What did you see instead?
ok  	cmd/compile/internal/test	0.023s [no tests to run]
ok  	cmd/compile/internal/types	0.035s
--- FAIL: TestFuncWithDuplicateLines (3.26s)
    cover_test.go:553: running [/go/src/golang/go/bin/go test -toolexec=/tmp/gotestcover178375904/toolexec.exe /tmp/gotestcover178375904/cover.exe -cover -covermode count -coverprofile /tmp/gotestcover178375904/linedup/linedup.out]
    cover_test.go:553: go: cannot find main module; see 'go help modules'
    cover_test.go:553: exit status 1
FAIL
FAIL	cmd/cover	6.872s
ok  	cmd/doc	0.047s
ok  	cmd/fix	13.342s

Fixed by https://golang.org/cl/167740.


Rewrite mockgyver from gen_fsm to gen_statem

Credits for original rewrite goes to Wojciech Antosiewicz in #10. Compared to that PR, this one is rebased, and I took some precautions to preserve code layout and doc rendering (edoc/edown) so no internal functions go into the doc.
The docs for gen_statem say that it was introduced in Erlang 19, so this PR makes mockgyver require Erlang 19+. Do you want to preserve compatibility with older Erlang versions? (I'm referring to the phrase "mockgyver still works on the older Erlang/OTP versions, given that an older parse_trans is used." in the commit message for 31fb60d) If so, I can add ifdefs and compatibility functions to still work with gen_fsm when gen_statem is not available.

Hi,
Thanks!  OTP 19 should be sufficient at this point. Anything else you'd like to address, otherwise I'll merge this.
/Klas

OTP 19 should be sufficient at this point. Anything else you'd like to address, otherwise I'll merge this.

Super! Then I think it is ready to go as is.

Thanks! Merged.


[chore] clean up

@addyosmani
A little clean-up.
Please review it. Thank you.

I'm going to go ahead and merge. :)


Peer dependencies for webpack 3 ?

We are having a warning from browser-sync-webpack-plugin after upgrade to webpack 3, do you want to add webpack 3 in your peer dependencies ?

done