ContextManagerTest.testSetProviderTwice testcase failed

version:1.0.3
[ RUN      ] ContextManagerTest.testSetProviderTwice
1970-01-01 05:10:45.976 [  1] 0 ContextManager:updateStateLocked:action=updatedState,state={"playerActivity":"PLAYING","offsetInMilliseconds":5,"token":""},namespace=SpeechSynthesizer,name=SpeechState
1970-01-01 05:10:45.976 [  1] 0 ContextManager:updateStateLocked:action=updatedState,state={"playerActivity":"FINISHED","offsetInMilliseconds":0,"token":""},namespace=AudioPlayer,name=PlaybackState
1970-01-01 05:10:45.986 [  8] 0 ContextManager:updateStateLocked:action=updatedState,state={"playerActivity":"FINISHED","offsetInMilliseconds":0,"token":""},namespace=SpeechSynthesizer,name=SpeechState
1970-01-01 05:10:45.987 [  9] 0 ContextManager:updateStateLocked:action=updatedState,state={"playerActivity":"FINISHED","offsetInMilliseconds":0,"token":""},namespace=AudioPlayer,name=PlaybackState
1970-01-01 05:10:45.988 [  a] 0 ContextManager:buildContextSuccessful:context={"context":[{"header":{"namespace":"AudioPlayer","name":"PlaybackState"},"payload":{"playerActivity":"FINISHED","offsetInMilliseconds":0,"token":""}},{"header":{"namespace":"SpeechSynthesizer","name":"SpeechState"},"payload":{"playerActivity":"FINISHED","offsetInMilliseconds":0,"token":""}}]}
/home/alexa/workspace/sdk/Code/out//obj/source/component/alexa/avs-device-sdk-1.0.3/ContextManager/test/ContextManagerTest.cpp:522: Failure
Value of: m_contextRequester->waitForContext(DEFAULT_TIMEOUT)
Actual: false
Expected: true
[  FAILED  ] ContextManagerTest.testSetProviderTwice (346 ms)

Hi @zhongxiaoma , which version of SDK are you using? And on what OS? Apart from the failure in running the unit test, is the SampleApp working for you?

I see you are using v1.0.3

my system is arm linux.
/KWD/test/AbstractKeywordDetectorTest
./ADSL/test/MessageInterpreterTest
./ADSL/test/DirectiveRouterTest
./ADSL/test/DirectiveSequencerTest
./ADSL/test/DirectiveProcessorTest
./ACL/test/MessageRouterTest
./ACL/test/HTTP2StreamPoolTest
./ACL/test/HTTP2StreamTest
./ACL/test/AVSConnectionManagerTest
./ACL/test/MimeParserTest
./AuthDelegate/test/AuthDelegateTest
./CapabilityAgents/AIP/test/AudioInputProcessorTest
./CapabilityAgents/SpeechSynthesizer/test/SpeechSynthesizerTest
./CapabilityAgents/System/test/StateSynchronizerTest
./CapabilityAgents/System/test/EndpointHandlerTest
./CapabilityAgents/System/test/UserInactivityMonitorTest
./ContextManager/test/ContextManagerTest
./MediaPlayer/test/MediaPlayerTest
./AFML/test/FocusManagerTest
./AVSCommon/Utils/test/TimerTest
./AVSCommon/Utils/test/ConfigurationNodeTest
./AVSCommon/Utils/test/LogEntryStreamTest
./AVSCommon/Utils/test/RequiresShutdownTest
./AVSCommon/Utils/test/ExecutorTest
./AVSCommon/Utils/test/LoggerTest
./AVSCommon/Utils/test/TaskThreadTest
./AVSCommon/Utils/test/SharedDataStreamTest
./AVSCommon/Utils/test/UUIDGenerationTest
./AVSCommon/Utils/test/TaskQueueTest
./AVSCommon/Utils/test/JSONUtilTest
./AVSCommon/AVS/test/ExceptionEncounteredSenderTest
./AVSCommon/AVS/test/CapabilityAgentTest
./AVSCommon/AVS/test/AlexaClientSDKInitTest
./AVSCommon/AVS/test/HandlerAndPolicyTest
./AVSCommon/AVS/test/DialogUXStateAggregatorTest
./AVSCommon/AVS/test/AttachmentTest
./AVSCommon/AVS/test/AttachmentReaderTest
./AVSCommon/AVS/test/NamespaceAndNameTest
./AVSCommon/AVS/test/AttachmentWriterTest
./AVSCommon/AVS/test/AttachmentManagerV2Test
for these ut case, only ContextManagerTest  and MediaPlayerTest   executed failed.  MedaiPlayer rely on our adapation, we are checking it, but ContextManager is an common componenet, so we are strange it ?

We do not see any failure on raspberry Pi which is also arm based linux. Are there any changes to the code of ContextManager?

No, i did not  modify any code ,  just cross compiled, and then deployed to a myb board .

Hi @zhongxiaoma, I have checked with the team and found out that this particular test is flaky if it's run on a slow hardware or the system has other load on it.  Please disregard this failure.  Thanks!


Initial Razor support

This is identical to the earlier PR (#2554) that was merged then reverted, except that in package.json, the dependency URLs have been updated to ones we are ready to be used for the initial preview.

Now all that's needed is an omnisharp-roslyn update 😉

@NTaylorMullen https://github.com/OmniSharp/omnisharp-vscode/pull/2573

Beauutiful!

@SteveSandersonMS How we can test it?

Great work!!!
@SteveSandersonMS How we can test it?

@jonathanperis If you install https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.17.0-beta5 release you can then open Razor files in C# projects and get C# completion/IntelliSense. We definitely appreciate the help all help in verifying the Razor functionality!

Apparently the C # part does what it should do. Works well. Now we need to check the issue of color highlights, something like works on the full VS, would be perfect. In some scenarios the color combination does not fit very well, especially when using C # outside of the keys, followed only by @. But this is not a matter of language support being tested here.

Ya totally hear you on color highlights, we wish we had time to fix that. That is a known issue that we plan to fix in our next release 😄

I will follow this work closely. I'm very interested in this feature.

@jonathanperis glad to hear! Keep an eye on https://github.com/aspnet/Razor.VSCode. It's closed-source right now so this link is most likely dead; however, we plan to open source it soon!

I already added in my favorites to follow when you open source it.

@jonathanperis it's now open source 😉


Web Hydration Example with Axum and build pipeline

Specific Demand
There is a big gap in the documentation on how to implement a properly hydrated web implementation.
Absolutely no project i found had a good implementation. All just had a loader for the wasm and none had proper pre-rendered html.
It would be nice to have a starter template that sets up a core-frontend-backend arch with out of the box dev tools.
Or maybe at least document how it is expected to be handled.
The questions:

Should the backend handle the frontend compilation ?
How to pre-render routes and hydrate them properly ?

and probably many more i'll discover.
Implement Suggestion
I'll maybe publish a template if i find a way to get it to work nicely.

https://github.com/DioxusLabs/dioxus/pull/916 adds fullstack examples for axum, salvo, and warp that illustrate how server functions, ssr, and hydration work together. It also includes a example to illustrate how SSR + Hydration work with the router


Signal an error when number of index argument exceeds array dimension

Currently, index access to arrays and ufuncs via operator() implements very permissive semantics: When passing too many arguments, only the last D are used, where D is the dimension. I'm convinced that this will lead to errors that are hard to debug. Instead, the function should throw an exception (if D is only known at runtime) or a static_assert (if D is known at compile time). I can't see any negative side effects of this change.

Actually, assuming a is a 2D expression and  b is a 1D expression, the following code should be valid:
auto expr = a + b;
double res = expr(2, 3); // This is computed as a(2, 3) + b(2, 3);

More formally, we want the following to be true, whatever the dimensions of a and b are:
(a+b)(i0, ..., in) = a(i0, ..., in) + b(i0, ..., in);

This is not possible if we forbid more arguments than the dimension.

Then the cleanest solution would be to provide two functions:

b(2, 3) signals an error
b.broadcast(2, 3) implements the current behavior and makes explicit that this is intended (maybe find a shorter name).

BTW, numpy also signals an error when too many indexes are provided and still manages to implement broadcasting.

Another solution to the broadcasting problem worked successfully in my vigra2 prototype: Embed the smaller array in an array view with the correct dimension and set the stride of the missing dimensions to 0. This has the additional advantage that one can broadcast over any dimension, not just the first.

Numpy implements broadcasting for expression assignment only, it does not provide unevaluated expressions with evaluation upon element access (which is what we're doing in the example that I posted above).
When assigning an expression, the broadcasting mechanism in xtensor is different from the one described here; we use iterators and steppers instead of the strides index scheme to avoid computing inner product.
I don't really see how allowing more index arguments than the dimension can be hard to debug, as long as the behavior is specified in the documentation (which is something we should really do).
Also I'm not sure to get what you mean about broadcasting over any dimension and not just the first ones. Do you mean something like the following?
xarray<double> a({3, 1, 4});
xarray<double> b({3, 3, 4});
auto expr = a + b;
double res = expr(2, 2, 2);

That is, broadcasting w.r.t. to the second dimension ?

Do you mean broadcasting w.r.t. to the second dimension ?

Yes. But I suppose this already works?
"Hard to debug" refers to the case where one accidentaly writes more indices than intended, and the code silently produces incorrect results. If the results are not too far off, it may take a long time until one even notices that something is worng.

About the broadcasting over any dimension, indeed that already works.
Considering an additional broadcasting method, we would have
(a+b).broadcast(i0, ..., in) == a.broadcast(i0, ..., in) + b.broadcast(i0, ..., in);

but (a+b)(i0, ...., in) may throw if a and b do not have the same dimension. Thus if I write some code that must work with any kind of expression, I will end up using the broadcast method everywhere instead of the operator(), to be sure I don't have any exception.
If the problem is debugging, maybe a better solution would be to turn on exceptions according to a compilation flag (just like we do for bound checking), or add an element access method that throws when it is provided too many arguments . Besides, this would be more "C++ish" (sorry for this barbarism), where the operator() can be very permissive, and other functions (like at) perform additional checks and may throw.

The desired behavior is that if too many indices are provided, we drop the first until we reach the right number. For containers, it is to prepend with zeros until we reach the right number. We narrowed this recently and some expressions still don't implement correctly the case where too few arguments are provided, (namely xview and xgenerator).
This is the only rule that guarantees that (a + b)(i0, ..., in) = a(i0, ..., in) + b(i0, ..., in) with the broadcasting rules when a and b have different dimensions.
I feel very strongly that this is how it should be across the library and that throwing exceptions on dimension mismatch is actually a mistake

but (a+b)(i0, ...., in) may throw if a and b do not have the same dimension.

I didn't mean to be that strict. (a+b)(i0, ...., in) would only throw if n was larger than the maximum dimension of a and b (or if the shapes were not compatible). Thus, it would be implemented as
(a+b)(i0, ..., in) == a.broadcast(i0, ..., in) + b.broadcast(i0, ..., in)

after checking that the number of indices on the LHS is valid.

maybe a better solution would be to turn on exceptions according to a compilation flag

That's also a possibility. I generally follow this rule: if the check doesn't significantly affect performance, turn it on by default, otherwise have the user turn it on explicitly. One should not forget that the C/C++ tradition of having very permissive functions originated in a time when computers were really slow. We don't have to continue like this just for historical reasons when the performance argument is no longer valid (e.g., a bounds check may incur no performance hit at all if the CPU pipeline gets branch prediction right). Every diagnostic is helpful for the user!

For containers, it is to prepend with zeros until we reach the right number.

I don't argue against this rule at all. I just refer to the case when there are too many indices on the outermost expression/access.

Even with the less strict implementation
(a+b)(i0, ..., in) == a.broadcast(i0, ..., in) + b.broadcast(i0, ..., in)

writing code that must work with any kind of expressions, whatever the dimension, will end up using the broadcast method everywhere. One of the use case we have is a 2D PDE solver where coeffecients may be constant over a direction (or even the two). In that case, to save memory space, we use 1D (or 0D) expressions but access them as if they were 2D (so the same code works with every kind of coefficients).
About the C++ tradition,  my point was more on the intuitive part of it: having used the STL, we expect operator[] / operator() of containers to not check their arguments, and to have dedicated functions for that (the counterpart of the vector<T>::at function). I find it more intuitive to keep this scheme, that is operator() / operator[] does not throw, specific method such at or safe_access do. Thus the user has the choice, he can work with the safe API if he needs to debug or if this does not hit performances on his machine, or with the one guaranteed to be the fastest.

Every diagnostic is helpful for the user!
I strongly agree with you

So here is what I'll do for fixing that:

add an at method that checks dimension and bounds
add a compilation flag to activate dimension checking for operator(), for debugging purpose.

Thanks a lot. One can now even compare the speed with and w/o ckecking code activated and eventually keep the check active at places were it doesn't hurt performance or usability.

I forgot to mention, checking the dimension requires to compute the shape of the expression, which may add some overhead for some kinds of expressions where the shape is computed the first time it is asked.
This won't cause any performance hurt in most of the cases since the shape will be evaluated when assigning the expression, however this could give strange results in benchmarks.

If the expression only involves arrays whose dimension is known at compile time, the dimension check can be done in a metaprogramm followed by static_assert and costs nothing at runtime. This is probably the most powerful variant of the check i can think of.

This is especially useful because arrays with static dimensions are anyway the preferrable alternative in many situations.


Call for maintainers

Since I'm no longer actively developing an app that uses synced-cron, I've lost touch with the codebase and the project. I'm looking for folks to take over development and maintenance, please raise your hand if you're interested.

I'm interested

Thanks very much @adrianbadarau . I've given you commit access to the repo. A good place to start might be to clean up the issues/PRs. If things go well we'll call you out as the official maintainer. Please let me know your Meteor Developer Account so I can give you permission to publish new releases.

Hi @zol, I will start using the package this week, and will analyze the codebase. I would like to volunteer to maintain the package, but I first need to have a look and check my availabilty - just wanted to give you an early feedback. I'll get back with a final answer.

I'm interested!

Thanks @TheGame2500 . I've given you commit access. Please co-ordinate with @adrianbadarau on tasks and releases.

I'm interested also guys, currently using this package in a production app so would love to keep it maintened

Thanks @tomtom87, I've given you write access to the repo.

@zol very appreciated will start looking at issues when I have some time later

Hi! :)
Any progress with maintaining this repo?

Sure, I didnt get to a PR yet but been answering some usage issues people where having..  what are you enquiring regarding?

On 26 Aug 2016, at 19:56, RJ<EMAIL_ADDRESS>wrote:
Hi! :)
Any progress with maintaining this repo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/percolatestudio/meteor-synced-cron","title":"percolatestudio/meteor-synced-cron","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/percolatestudio/meteor-synced-cron"}},"updates":{"snippets":[{"icon":"PERSON","message":"@rudza in #91: Hi! :) \r\n\r\nAny progress with maintaining this repo? "}],"action":{"name":"View Issue","url":"https://github.com/percolatestudio/meteor-synced-cron/issues/91#issuecomment-242727858"}}}

@tomtom87 persistent storage for Jobs, maybe? ;)

I'd be interested in helping with the repo, although my time is limited.  @toomtom87 can someone review this pull request: https://github.com/percolatestudio/meteor-synced-cron/pull/112 and merge it in, if happy with it? Thanks!

Hey Guys,
Also super keen as we're using this in production, and will likely use it on at least two other production apps this year.  Let me know if you're in need of another set of helping hands.
P:)

@spawn-guy how could we implement this? Doesn't the cronHistory already take care of this?

@ElegantSudo cronHistory is exactly for what is in the name. for History and _Sync_ing
Jobs are added and held in memory. When the "schedule" function result time is right - the Job is fired. When the job is fired - the document is added to cronHistory collection. If you have multiple backend servers running - they all check for that document existence. and if there is one and "running" - the other servers do not fire this same Job.
good thing is when you write your Jobs in the Code - if server restarts jobs are reloaded.
bad thing is when you Generate Jobs on the fly in the runtime - if the server is restarted you have to regenerate(re-add) all the Jobs.
obstacles:

i dunno how to load/save Closure functions from the database
maybe not all the Jobs need to be stored in cronJobs collection, as you might have a bunch of "recurring jobs" in the code and another bunch of "delayed one-timers".
2.2) also "one-timers" should be cleaned up from memory/cllection after firing.

This is an interesting problem. Maybe I'll likely fork this repo sometime within the next month and solve it.

+1 @cwebbdesign @tomtom87 #112

I'm interested!

Not quite the same, but I've almost finished a Meteor-first jobs queue that could address the same needs as this package.
https://github.com/msavin/stevejobs--meteor-jobs-queue

Is someone still maintaining this?

@zol have you passed Meteor account access to anybody yet? If not, I think @TheGame2500 is actively looking to maintain and release

I've given admin access to all maintainers including @TheGame2500

Thanks everyone!


function where given a gene set it deletes all scores

delete all columns from the obs matrix given a gene set file.

This is essentially:
andata.obs.drop(columns=score_varnames, inplace=True)

This is implemented.
However, if the table columns only partially match the incoming gene set names. It will throw an error.

fixed.  Previously set gene set scores will now be dropped. All or just a subset.


plan-all output file contains plan for only a single module

Hi :wave:
Apologies if this is a duplicate issue.
Running terragrunt plan-all -out=/tmp/output.plan in a structure like the following:
root
├── module-1
│   └── main.tf
├── module-2
│   └── main.tf
├── module-3
    └── main.tf

The output.plan file only contains the plan for one of the modules at the end of execution.
Looking at the terragrunt output this makes sense as it's running terraform plan -out=/tmp/output.plan in each module thus overwriting the plan file each time.
Possibly an easy fix to append a prefix/suffix to the output file name during execution. Will try to contribute a PR when I can.

Using -out with an absolute path definitely won't work, as all of the plan commands will write to the same file. Using a relative path might work...


error, loop on make a session. when select option 3

Input your choice : 3
[2024-08-31T23:28:43.091] [INFO] - [Running gramJS version 2.22.1]
[2024-08-31T23:28:43.099] [INFO] - [Connecting to <IP_ADDRESS>:80/TCPFull...]
[2024-08-31T23:28:43.513] [INFO] - [Connection to <IP_ADDRESS>:80/TCPFull complete!]
[2024-08-31T23:28:43.555] [INFO] - [Using LAYER 181 for initial connect]
? Enter your Telegram Phone Number ?

after creating session, just cancel the bot and restart again, after that choose 3 for start the bot, if you still got that problem it maybe there something wrong on session creation, try to reset session and create again


Accept subdivision feature

Desired behavior
I desire to be able to export the model I worked hard for Gazebo projects. See the first picture and second picture.
In blender:

In Gazebo:

It was due to not take subdivision feature from Blender
Alternatives considered
I just accept the PS1 resolution and take the defeat.
Additional context
Here is the blender project in case if you want to look or check with the sdf exporter.py
blender_project.zip

Nevermind, I just realized I could just export it as STL then re-import the STL and use the blender-exporter.py.
:facepalm:
Closing as this can done on our own.


Event names are barely legible

MWE:
# %%
import mne

sample_dir = mne.datasets.sample.data_path()
sample_fname = sample_dir / 'MEG' / 'sample' / 'sample_audvis_raw.fif'

raw = mne.io.read_raw_fif(sample_fname)
raw.crop(tmax=60)

events = mne.find_events(raw, stim_channel='STI 014')
event_id = {'auditory/left': 1, 'auditory/right': 2, 'visual/left': 3,
            'visual/right': 4, 'face': 5, 'buttonpress': 32}

raw.plot(events=events, event_id=event_id)

Produces:

Turquoise on white seems like a very sub-optimal choice, at least doesn't work for my eyes.

Yes, I like this idea

@hoechenberger if this is an easy/good first issue shall I try for the same?

@Dev-satish Thank you having a look into this.
But I think this event-color issue might better be resolved within mne itself, where the event-colors are set with _make_event_color_dict

Would you agree @hoechenberger?

Sounds like a plan!


fix hibernate warning

2016-05-03 10:55:56,892 WARN  HibernateJpaDialect.java:347 :
JDBC Connection to reset not identical to originally prepared Connection
- please make sure to use connection release mode ON_CLOSE (the default)
and to run against Hibernate 4.2+ (or switch HibernateJpaDialect's prepareConnection flag to false

After upgrading Spring 4.2 above logs are frequently seen. We may face the resource leak eventually. Fix is necessary.

Fixed


Update elasticsearch to 6.8.17

This resolves a single bug:
https://www.elastic.co/guide/en/elasticsearch/reference/6.8/release-notes-6.8.17.html
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

https://buildkite.com/chef/chef-chef-server-master-omnibus-adhoc/builds/2878#395b8827-313c-4b35-9d99-600e2be6dc6f


Add general load/save functions to pandas.* namespace, and update docs

Preferable to using DataFrame.load

Done, but still need to add to docs


Bug fix

Thumbnail generator

Fixed an issue where the asset aspect ratio wouldn't be kept when changing the background aspect ratio

Other

Updated French localisation

Goat 🙏


[Feature request] Create a client method to check remote availability in Workplace search

In Logstash's Enterprise Search plugin, for the Workplace output we use a method to check the connections to the remote:
https://github.com/logstash-plugins/logstash-integration-elastic_enterprise_search/blob/8ff2f8fc982f8036772430c670d1717895333a97/lib/logstash/outputs/elastic_workplace_search.rb#L103-L105
With version 8.0 of Workplace search the underlying http endpoint has been removed, made some test to fail as described in https://github.com/logstash-plugins/logstash-integration-elastic_enterprise_search/issues/14.
The solution could be to use other methods, that implicitly prove the connectivity.
The Workplace client should provide an explicit API to check the connectivity, so that's future proof.
Elasticserach Ruby client provide a similar feature, as reference: https://www.rubydoc.info/gems/elasticsearch-api/Elasticsearch/API/Actions#ping-instance_method

Hi @andsel, I'll talk to the Workplace Search team about a health API endpoint in our weekly meeting tomorrow.
I assume Enterprise Search's health endpoint wouldn't work since it's using a Workplace Search client and there would be different authentication for the Enterprise Search APIs.

Thanks @picandocodigo, the EnterpriseSearch output return a rich information, could be useful but return a lot of context.
Suppose you only have to check if the servers responds to an HTTP request, using the provided credentials, returning all that information could be abundant.
I had in mind something like https://github.com/elastic/elasticsearch-ruby/blob/88916fcf40f217bf8f31126e8b416141e65973cf/elasticsearch-api/lib/elasticsearch/api/actions/ping.rb#L27 that return true or false where true is "you are good to connect to the server".

@markjhoy thanks for looking into this!

I'm not sure why the list_all_permissions call is used for checking the connection here

The original implementation was provided by @davishmcclurg so maybe has good insights for this. It uses the workplace-search-ruby client, and maybe that client doesn't provide the content source API

@andsel - David no longer works for Elastic, however, I do see that that last PR was dated in May of last year - so, it's quite possible that a lot has changed since then (and IIRC, the content source endpoint didn't exist when this was written)... but - regardless - I would think the Content Source GET endpoint linked above should provide a feasible workaround.

and IIRC, the content source endpoint didn't exist when this was written.

So in my use case, the LS output plugin, which could potentially connect to such old versions, I can't use an API that's available only the latest versions.


symphony/process requirement conflict

Deployer version: 4.3.0
Deployment OS: osx monterey

Trying to install with another package "spatie/browsershot" and get the following:
Problem 1
    - deployer/deployer[v4.3.0, ..., v4.3.4] require symfony/process ~2.6|~3.0 -> found symfony/process[v2.6.0, ..., v2.8.52, v3.0.0, ..., v3.4.47] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires deployer/deployer ^4.3 -> satisfiable by deployer/deployer[v4.3.0, ..., v4.3.4].

Deployer version: 4.3.0

Wow 😯
Try to upgrade to v7-rc.

I should mention this was running composer require deployer/deployer which seems to be locked on ^4.3.0 - have since specifically run composer require deployer/deployer:v7.0.0-rc-8 which installed fine.


spirv-fuzz: TransformationAddParameter has instroduced a regression

https://github.com/KhronosGroup/SPIRV-Tools/blob/fba90d6b0a23ae2331273aedabc569a3816750ac/source/fuzz/transformation_add_parameter.cpp#L104-L106
parameter_type_id might have been created after old_function_type. This piece of code will then make old_function_type reference id of an instruction that is defined below the old_function_type which causes a segmentation fault in the type manager.
There is a bigger concern here, though. If this behaviour is invalid, then the validator should've raised an error. If it is valid, then the type manager shouldn't have caused a segmentation fault. Either way, segfault should've never occurred.

I believe it's the case that all the parameter types of a function need to be declared before the function.
Regarding whether the validator should have raised an error: are you able to write a unit test that applies a transformation in a manner that leads to an invalid module without a segfault occurring first?  That should indeed lead to a validator complaint if you do IsValid to check whether the module is valid.
The validator will only complain if run explicitly, though - is it being run explicitly in the scenario you are concerned about?

You are correct. It seems that validator works as expected. The reason for the crash is that we were applying multiple transformations in the FuzzerPassAddParameters and if one of those transformations invalidates the module, the next one might or might not crash (the validator is not executed between two consecutive transformations). In our case, the crash happens in the type manager when we try to create a constant instruction for the next transformation. The bottom line is that there is nothing wrong with either the validator or the type manager.


Protoactor Go project positioning and future plans?

I recently bumped into proto.actor and very interested in the Go parts of the project. But I have some questions..
Recently the DotNet project seems more active. They are independent codebases. How are they related, i.e. kept in sync functionality / compatibility wise? Is Golang part of the long-term roadmap of proto.actor as something with prolonged commitment / support?
Related: The documentation is mostly focused on C# .. is Golang the 2nd-class citizen?
How does Asynkron fit into the picture? What is your revenue model and relationship to proto.actor as an open-source project?
Related to #343 and #307

OT: I will also tell you a bit about the use case I am interested in, namely "easing federated app development for the Fediverse". If you find it interesting to discuss this in more detail, I can move to a separate issue.
W3C AtivityPub Recommendation is an actor-based protocol that allows federated communication based on a simple HTTP API where Actors (Person, Organization, Service, Application) exchange JSON-LD messages via inbox & outbox endpoints. This extensible protocol is the basis of the Fediverse where a large number of diverse apps interoperate and more than 5 million users interact.
It makes sense for a federated app to be actor-based internally as well, where server-to-server messages are handled by a Federation actor and delegated to e.g. Person actors referenced in the message. In my app design modularity and extensibility are key, and I intend to use domain-driven design ports & adapters architecture (similar to ftpgogo example project).
I won't be using gRPC over the network (where I use AP), but was intending to use Hashicorp's go-plugin (which uses gRPC) to have a dynamic plugin system and ability to add/remove module extensions dynamically at runtime. I still need to check if/how this can be combined with proto.actor (Proto.Remote?).
As for where DDD kicks in, I feel most for Alexey Zimarev's approach to have actors in the application layer and keep the domain layer free of actor concerns (in contrast to Vaughn Vernon who talks about turning domain aggregates into actors).
Would be lovely if you could shine a light, give some feedback on this setup as it relates to proto.actor..

Hello @aschrijver
Absolutely, Inlining per question here:
Starting in reverse order:

How does Asynkron fit into the picture? What is your revenue model and relationship to proto.actor as an open-source project?

I'm the founder of Asynkron and the Proto.Actor project.
Asynkron as a company is the owner of the Proto.Actor trademark.
The opensource projects are also under a Contributors License Agreement, which grants Asynkron the signed license to use the contributed code.
Under Asynkron, we offer consulting services around scalability, distributed systems, workshops, training sessions around the actor model in general, and Proto.Actor as a framework, e.g. helping clients architect and implement Proto.Actor systems.
We are currently in negotiations with a potential partner company for setting up a full set of support plans for Proto.Actor.
Offering developer support and full-fledged 24/7 SLA production support.

How are they related, i.e. kept in sync functionality / compatibility wise? Is Golang part of the long-term roadmap of proto.actor as something with prolonged commitment / support?

The plan is to keep the two fully in sync. currently working on porting over all the new cluster features from .NET to Go.
Which project gets the most attention depends very much on where there currently are the most contributors, and what clients we are working with. e.g. I am working full time with a .NET customer right now, which leads to more progress on the .NET version.
Personally, I do believe Proto.Actor Go has a brighter future as Go generally is more used in the high-scalability world.
Hope this sheds some light on your questions?
Let me know if there is anything that I can elaborate on

Wow, thanks for the quick response (way quicker than expected, as I just cross-posted to the forum). I will move further discussion to this forum topic.

I won't be using gRPC over the network (where I use AP), but was intending to use Hashicorp's go-plugin (which uses gRPC) to have a dynamic plugin system and ability to add/remove module extensions dynamically at runtime. I still need to check if/how this can be combined with proto.actor (Proto.Remote?).

This is an interesting topic, we are sketching on how to offer this out of the box.
We have two similar but different in scope size approaches for this.
The first is to allow for actor plugins, e.g. making it possible to hook the actor receive pipeline to a chain of external services.
@alexeyzimarev is involved in this also. as the primary use-case is for our shared client project.
The other approach we have is to offer a Proto.Serverless module, which would build on a form of shapeless actors which only hold raw state in binary form, which then push this state and incoming messages to external services over gRPC.
allowing actor logic to be written in any language.
This is the same approach as Akka.Serverless and Dapr uses.

I will post the OT part to a new forum topic.. it has a bit too many links for a trust level 0 user, so I was posting some other stuff first :)

Moved my replies there too. 👍🏻


Fix include & broken link

Per Jason's email, this PR removes an include from the internal contributor guide because the include linked to an article that this guide doesn't have access to. I kept the language of the include but fixed the link to point to the correct article in this guide.

#sign-off


Incorrect Image: Create virtual machine scale set

Hi there, Please update the image on the section for 'Create virtual machine scale set'.
At least update the current document (With a Note:) about the features which are in Preview, so that customers are not confused.
When I try to create the VM Scale Set, the experience is totally different.
Below is the one which I don't see on the documentation section of 'Create virtual machine scale set'

The sections are not matching with the document image.
I don't see 'Orchestrator'
Instance details also don't match.
Azure Spot Instance is missing.

Below is the screengrab of my experience.

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

ID: e0ac55b8-8be8-1f86-e3b1-3fe3f6c340c1
Version Independent ID: c26d3fc8-b62c-4895-3687-2fc7364c6383
Content: Quickstart - Create a virtual machine scale set in the Azure portal - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/quick-create-portal.md
Service: virtual-machine-scale-sets
Sub-service: ****
GitHub Login: @ju-shim
Microsoft Alias: jushiman

@koneni
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@ju-shim
Can you please check and add your comments on this doc update request as applicable.

Hi @VikasPullagura-MSFT
Is there any update on this issue? Wanted to know if the documentation is updated or not.

@mimckitt Can you please add your comments on this.

Fixed. Should be live by end of the day.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/142237
#please-close

Fixed. Should be live by end of the day.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/142237
#please-close


Finishing Touches

Re-touched a bunch of the other spline docs so they all agree and use the same style. I don't think Alice will mind doing this here, as she was asking for docs on some stuff already not touched by this PR (like the characteristic matrix of a normal BSpline).
I replaced all "Knot Vector" and "Weight Vector" language with "knots" and "weights". Less verbose.
Knots are now normalized such that the intervals between knots form an exact cover of [0, N] where N is the number of curves. This makes both nurbs and b-splines have the same parametric domain.
RationalSegement now tracks the size of it's parametric domain, as derived from the knot vector.
RationalCurve now allows for different sizes of segment, and clamps the parameter to the curve domain. The output of RationalCurve::segment is mapped to [0, 1].
Added detailed references to the papers where possible.

Marked another place where CI errors

Made those fixes and finally got the circular arc test right. Ready for merge and final reviews?


GMNA OM

✖ Error launching browser
Error: Failed to launch the browser process!
/home/runner/.cache/puppeteer/chrome/linux-1108766/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://pptr.dev/troubleshooting
at Interface.onClose (/home/runner/BocchiBot/node_modules/@puppeteer/browsers/lib/cjs/launch.js:262:24)
at Interface.emit (node:events:525:35)
at Interface.close (node:internal/readline/interface:536:10)
at Socket.onend (node:internal/readline/interface:262:10)
at Socket.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

✖ Failed to launch the browser process!
/home/runner/.cache/puppeteer/chrome/linux-1108766/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://pptr.dev/troubleshooting
Error: Failed to launch the browser process!
/home/runner/.cache/puppeteer/chrome/linux-1108766/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://pptr.dev/troubleshooting
at Interface.onClose (/home/runner/BocchiBot/node_modules/@puppeteer/browsers/lib/cjs/launch.js:262:24)
at Interface.emit (node:events:525:35)
at Interface.close (node:internal/readline/interface:536:10)
at Socket.onend (node:internal/readline/interface:262:10)
at Socket.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Error: Failed to launch the browser process!
/home/runner/.cache/puppeteer/chrome/linux-1108766/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://pptr.dev/troubleshooting
at Interface.onClose (/home/runner/BocchiBot/node_modules/@puppeteer/browsers/lib/cjs/launch.js:262:24)
at Interface.emit (node:events:525:35)
at Interface.close (node:internal/readline/interface:536:10)
at Socket.onend (node:internal/readline/interface:262:10)
at Socket.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Install Chrome.
https://openwa.dev/docs/get-started/installation#chrome-issues-on-linux-based-systems

tpi gua run di replit bang

tpi gua run di replit bang

replit gabisa , mending rdp
kalo mau pake replit coba pake library bot wa yang lain

Oh gtu ya bang, gapunya rdp hwhw


PlexonIO incomplete event loading

In Neo-0.3.1-py2.7 PlexonIO has been incompletely loading events for some event channels. (I think that the .plx files were from plexon version 102.) It seems that the imported eventarray has only 1 event for each event type for a total of the number of event labels. Some of the markers have only 0 to 1 events but some event channels should have imported hundereds of events.

If you are using PlexonIO, see my answer in issue #347.


Check for undefined source.symbol when elaborating unmatched properties

Fixes #37014

Forgot to include baselines 🤦♂

@typescript-bot cherry-pick this to release-3.8


[Solved] Environment conflict: Caffe2 Compilation VS Conda Packages

Caffe2 compilation requires system protobuf, leveldb, gflags, opencv, etc rather than those installed from conda. Please refer to this issue from Caffe2.
According to README.md, we install these packages by conda first, and then compile Caffe2, which will lead to errors like:
undefined reference to google::protobuf::internal::AssignDescriptors(std::__cxx11::basic_string
undefined reference to leveldb::Status::ToString[abi:cxx11]()
undefined reference to google::protobuf::internal::empty_string_[abi:cxx11]
I've solved this problem by:

Add -DCMAKE_CXX_FLAGS=-D__GLIBCXX_USE_CXX11_ABI=0 to the cmake command.

Use system versions of gflag, protobuf, opencv, or leveldb (try installing with apt-get). Uninstall these libraries from Anaconda and try to build again.

Finally successfully build on:

Ubuntu 16.04
Anaconda (python 2.7)
OpenCV 3.4.1
GCC 5.4
CUDA 9.0
cuDNN 7.1.2
numpy 1.14.3

Great, thanks for sharing!


feat: remove redirect to '/Nav' on successful login

BREAKING CHANGE: this should be done in mainservice.init instead
this is for this change https://github.com/fielded/nav-integrated-state-dashboard/commit/44d09fb752d19048d07b6ffea121aaee89a82b80#diff-fb7316a4ae49d04b95801fa107d21facR63
thats related to this issue: https://github.com/fielded/van-orga/issues/434

thank you!


tensorflow is shown on listing packages using pip list or conda list but you can't import in Python

Same issue happened even with using pip install https://storage.googleapis.com/tensorflow/mac/cpu/tensorflow-2.3.0-cp38-cp38-macosx_10_14_x86_64.whl
as mentioned in https://www.tensorflow.org/install/pip#package-location
tensorflow is shown on listing packages using pip list or conda list but you can't import in Python
When I try to import TensorFlow the kernel restarting and then I have the message
[SpyderKernelApp] WARNING | No such comm: 7843964a725e11eb900a1e29c0108246
[SpyderKernelApp] WARNING | No such comm: 81501ed4725e11eb900a1e29c0108246

@nayrr25,
In order to expedite the trouble-shooting process, could you please provide the following details

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version:
Python version:
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

and the exact sequence of commands / steps that you executed before running into the problem. Thanks!

Also, looking at the messages it seems like the issue is with Spyder IDE. To confirm if TensorFlow is successfully installed please run the below code snippet.
import tensorflow as tf
print(tf.reduce_sum(tf.random.normal([1000, 1000])))

Thanks!

When I run that code:
import tensorflow as tf
print(tf.reduce_sum(tf.random.normal([1000, 1000])))
I receive that message:
Kernel died, restarting
Restarting kernel...
[SpyderKernelApp] WARNING | No such comm: 7843964a725e11eb900a1e29c0108246
[SpyderKernelApp] WARNING | No such comm: 81501ed4725e11eb900a1e29c0108246
[SpyderKernelApp] WARNING | No such comm: e012dd08725e11eb900a1e29c0108246
[SpyderKernelApp] WARNING | No such comm: b8bfbb76726411eb900a1e29c0108246
[SpyderKernelApp] WARNING | No such comm: f1fb85aa726411eb900a1e29c0108246
[SpyderKernelApp] WARNING | No such comm: 24454e6e726b11eb900a1e29c0108246
[SpyderKernelApp] WARNING | No such comm: d8eaf940726b11eb900a1e29c0108246

@nayrr25,
Please try importing TensorFlow in the macOS terminal i.e. outside the conda environment and check if you are facing the same issue. Thanks!


[BUG] Command failed with status 400 bad request

helix-editor version
helix 24.3
helix-gpt version
0.34
OS: Windows 11
build from source to binary with bun all required env variabels added to the system
HANDLER=copilot
Describe the bug
executing code action result in following message

helix-gpt logs
Helix GPT output logs. Pass --logFile /app/helix-gpt.log to save them.
note   not sure how to get that on windows ☝
helix logs
helix.log

I get 400 too when ctrl+x with Codeium
Fetch failed with status 400 body {"code":"invalid_argument","message":"validation error:\n - document.editor_language: value length must be at least 1 characters [string.min_len]: validation error:\n - document.editor_language: value length must be at least 1 characters [string.min_len]","details":[{"type":"cockroach.errorspb.EncodedError","value":"Ep4p...","debug":{"wrapper":{"cause":{"wrapper":{"cause":{"wrapper":{"cause":{"wrapper":{"cause":{"wrapper":{"cause":{"leaf":{"message":"validation error:\n - document.editor_language: value length must be at least 1 characters [string.min_len]","details":{"originalTypeName":"github.com/bufbuild/protovalidate-go/internal/errors/*errors.ValidationError","errorTypeMark":{"familyName":"github.com/bufbuild/protovalidate-go/internal/errors/*errors.ValidationError"}}}},"message":"validation error:\n - document.editor_language: value length must be at least 1 characters [string.min_len]: validation error:\n - document.editor_language: value length must be at least 1 characters [string.min_len]","details":{"originalTypeName":"github.com/cockroachdb/errors/errutil/*errutil.withPrefix","errorTypeMark":{"familyName":"github.com/cockroachdb/errors/errutil/*errutil.withPrefix"},"reportablePayload":["validation error:\n - document.editor_language: value length must be at least 1 characters [string.min_len]"],"fullDetails":{"@type":"type.googleapis.com/cockroach.errorspb.StringPayload","msg":"validation error:\n - document.editor_language: value length must be at least 1 characters [string.min_len]"}}}},"details":{"originalTypeName":"github.com/cockroachdb/errors/withstack/*withstack.withStack","errorTypeMark":{"familyName":"github.com/cockroachdb/errors/withstack/*withstack.withStack"},"reportablePayload":["\ngithub.com/Exafunction/Exafunction/exa/connect_utils.(*validateInterceptor).WrapUnary.func1\n\texa/connect_utils/validate.go:36\ngithub.com/Exafunction/Exafunction/exa/language_server.initServers.NewRemoteModeInterceptor.func9.1\n\texa/connect_utils/remote_mode.go:28\ngithub.com/Exafunction/Exafunction/exa/connect_utils.(*LogErrorsServerInterceptor).WrapUnary.func1\n\texa/connect_utils/interceptor.go:53\ngithub.com/easyCZ/connect-go-prometheus.(*Interceptor).WrapUnary.func1\n\texternal/com_github_easycz_connect_go_prometheus/interceptor.go:73\ngithub.com/Exafunction/Exafunction/exa/connect_utils.(*SentryErrorInterceptor).WrapUnary.func1\n\texa/connect_utils/interceptor.go:214\nconnectrpc.com/connect.NewUnaryHandler[...].func2\n\texternal/com_connectrpc_connect/handler.go:70\nconnectrpc.com/connect.(*Handler).ServeHTTP\n\texternal/com_connectrpc_connect/handler.go:238\ngithub.com/Exafunction/Exafunction/exa/language_server_pb;language_server_.NewLanguageServerServiceHandler.func1\n\tbazel-out/k8-opt/bin/exa/language_server_pb/language_server_connect_go_proto_/github.com/Exafunction/Exafunction/exa/language_server_pb;language_server_/language_server.connect.go:1410\nnet/http.HandlerFunc.ServeHTTP\n\tGOROOT/src/net/http/server.go:2171\nnet/http.(*ServeMux).ServeHTTP\n\tGOROOT/src/net/http/server.go:2688\ngithub.com/Exafunction/Exafunction/exa/language_server.initServers.(*Cors).Handler.func10\n\texternal/com_github_rs_cors/cors.go:231\nnet/http.HandlerFunc.ServeHTTP\n\tGOROOT/src/net/http/server.go:2171\ngithub.com/Exafunction/Exafunction/exa/language_server.initServers.(*Handler).Handle.(*Handler).handle.func11\n\texternal/com_github_getsentry_sentry_go/http/sentryhttp.go:124\nnet/http.HandlerFunc.ServeHTTP\n\tGOROOT/src/net/http/server.go:2171\ngolang.org/x/net/http2.(*serverConn).runHandler\n\texternal/org_golang_x_net/http2/server.go:2369\nruntime.goexit\n\tsrc/runtime/asm_amd64.s:1695"]}}},"details":{"originalTypeName":"github.com/Exafunction/Exafunction/exa/go_utils/*go_utils.withConnectCode","errorTypeMark":{"familyName":"github.com/Exafunction/Exafunction/exa/go_utils/*go_utils.withConnectCode"},"reportablePayload":["invalid_argument"]}}},"details":{"originalTypeName":"github.com/cockroachdb/errors/withstack/*withstack.withStack","errorTypeMark":{"familyName":"github.com/cockroachdb/errors/withstack/*withstack.withStack"},"reportablePayload":["\ngithub.com/Exafunction/Exafunction/exa/connect_utils.(*validateInterceptor).WrapUnary.func1\n\texa/connect_utils/validate.go:37\ngithub.com/Exafunction/Exafunction/exa/language_server.initServers.NewRemoteModeInterceptor.func9.1\n\texa/connect_utils/remote_mode.go:28\ngithub.com/Exafunction/Exafunction/exa/connect_utils.(*LogErrorsServerInterceptor).WrapUnary.func1\n\texa/connect_utils/interceptor.go:53\ngithub.com/easyCZ/connect-go-prometheus.(*Interceptor).WrapUnary.func1\n\texternal/com_github_easycz_connect_go_prometheus/interceptor.go:73\ngithub.com/Exafunction/Exafunction/exa/connect_utils.(*SentryErrorInterceptor).WrapUnary.func1\n\texa/connect_utils/interceptor.go:214\nconnectrpc.com/connect.NewUnaryHandler[...].func2\n\texternal/com_connectrpc_connect/handler.go:70\nconnectrpc.com/connect.(*Handler).ServeHTTP\n\texternal/com_connectrpc_connect/handler.go:238\ngithub.com/Exafunction/Exafunction/exa/language_server_pb;language_server_.NewLanguageServerServiceHandler.func1\n\tbazel-out/k8-opt/bin/exa/language_server_pb/language_server_connect_go_proto_/github.com/Exafunction/Exafunction/exa/language_server_pb;language_server_/language_server.connect.go:1410\nnet/http.HandlerFunc.ServeHTTP\n\tGOROOT/src/net/http/server.go:2171\nnet/http.(*ServeMux).ServeHTTP\n\tGOROOT/src/net/http/server.go:2688\ngithub.com/Exafunction/Exafunction/exa/language_server.initServers.(*Cors).Handler.func10\n\texternal/com_github_rs_cors/cors.go:231\nnet/http.HandlerFunc.ServeHTTP\n\tGOROOT/src/net/http/server.go:2171\ngithub.com/Exafunction/Exafunction/exa/language_server.initServers.(*Handler).Handle.(*Handler).handle.func11\n\texternal/com_github_getsentry_sentry_go/http/sentryhttp.go:124\nnet/http.HandlerFunc.ServeHTTP\n\tGOROOT/src/net/http/server.go:2171\ngolang.org/x/net/http2.(*serverConn).runHandler\n\texternal/org_golang_x_net/http2/server.go:2369\nruntime.goexit\n\tsrc/runtime/asm_amd64.s:1695"]}}},"details":{"originalTypeName":"github.com/Exafunction/Exafunction/exa/go_utils/*go_utils.withSha","errorTypeMark":{"familyName":"github.com/Exafunction/Exafunction/exa/go_utils/*go_utils.withSha"},"reportablePayload":["8fde..."]}}}}]} url: /exa.language_server_pb.LanguageServerService/GetCompletions

Closing as not able to reproduce anymore now works as expected


example: create example epic-stack-with-prisma-client-extensions

Adding documentation  on how to use Prisma client extensions for "enum"-like validation. [Issue #29] (https://github.com/epicweb-dev/epic-stack/issues/29)
Test Plan
N/A
Checklist

[ ] Tests updated
[x] Docs updated

Screenshots

I created an example for this here for you to look at and decide if you'd like it as an example.

Looking at the diff and your loom, I think this would make a great addition as an example. Could you please update the PR to link to the example instead of having a docs page on this? I think that's more suitable.

Removed the docs file and updated examples.md.


who at discord is responsible for this? i need names.

discord thought it was a great idea to fuck up capitalization of aria-labels very cool, imma wait and see if its a bug from discord's side and if they fix it and im planning to change the fetching of badges from aria-label's to src anyway cause language support and blah blah should be fixed in less than a week (long deadline cause i have exams currently)

I could try to do if you wanted me to?

I could try to do if you wanted me to?
nah its cool im basically done with the "colored badges" just need to fix the white ones should be done by today
~And yeah whoever is working as a dev at Discord I swear to God must be on crack~
fr

Alright, epico B)

god damn it, wasnt a discord update but me changing my language from eng us to eng uk lmao (still weird why is the uk one not capitalized)
anyway rewrote the theme to use svgs now apart from early supporter(dont think i can do anything about this) and booster badges(if someone wants to get all the 11 svgs and fix this be my guest, make a pull request or smth)


Introduce EmbeddedXlTable.defaults to store composite tag info

This PR introduces EmbeddedXlTable.defaults to store the additional info from a composite tag. Separating this info early on allows removing repeated decomposition of the composite tag.

Can't comment on the logic (which I don't really understand), but other than my one nitpick, looks good :)

Thanks! Basically, this just extracts the extra info that may be included with a tag (e.g. ~FI_T: ACT_BND) earlier. It will also make it easier to handle some other ways in which this extra info may be included.


chore(update to 1.3.2): fix types

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Screenshots/Demo

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Looks good! Merging.


Fix build wheels due to setuptools changed naming

This is due to https://github.com/pypa/setuptools/issues/4300
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

triggered https://github.com/apache/beam/actions/runs/8692146995


No such device exists

Thank you so much for creating this! I have been getting an error when I attempt to run the executable.
The SSID for my machine is "Dikun" and the dash is connected to the same network. When I run sudo find_dash Dikun the output is
/Users/timothydikun/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/dashed-0.3.0/exe/find_dash:9:in `open_live': Dikun: No such device exists (BIOCSETIF failed: Device not configured) (RuntimeError)
	from /Users/timothydikun/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/dashed-0.3.0/exe/find_dash:9:in `<top (required)>'
	from /Users/timothydikun/.rbenv/versions/2.1.5/bin/find_dash:23:in `load'
	from /Users/timothydikun/.rbenv/versions/2.1.5/bin/find_dash:23:in `<main>'

Any idea what I'm doing wrong? Thanks.

You don't want to use the SSID, but rather the network interface name for your wireless card... usually something like wlan0 or en1

Thanks, en1 did the trick. I am new to Ruby so am having a little difficulty figuring out how to create an application that is able to do something with this. Whenever you get the chance, a demo app would be really helpful. Maybe a simple one that just prints a string to the browser whenever the button is pushed. Thanks!

The readme shows an example implementation. All you have to do is add the proper requires to the top of the file:
require "rubygems"
require "dashed"

Dashed::Button.new("ff:ff:ff:ff:ff:ff", "en1").on_press do
  puts "I was pressed!"
end

The ff:ff:ff:ff:ff:ff should be the mac address for your button that you found using the find_button utility.

Ok, thanks!
On Mon, Nov 2, 2015 at 1:40 PM Justin Kenyon<EMAIL_ADDRESS>wrote:

The readme shows an example implementation. All you have to do is add the
proper requires to the top of the file:
require "rubygems"require "dashed"
Dashed::Button.new("ff:ff:ff:ff:ff:ff", "en1").on_press do
puts "I was pressed!"end
The ff:ff:ff:ff:ff:ff should be the mac address for your button that you
found using the find_button utility.
—
Reply to this email directly or view it on GitHub
https://github.com/kenyonj/dashed/issues/2#issuecomment-153135460.


Cube sphere regridder

@pp-mo @marqh Finally got the tests to pass (was missing a skipper), and I have removed the optimisation change that didn't work and wasn't necessary in this PR.

I saw you'd addressed almost all pep8 issues with analysis.trajectory
Hence my corinnebosley#3
Otherwise this all looks good to me now.
@corinnebosley please check that out + see if you're okay to merge that in here, too
- or if not, just say so + we can just skip it.
Either way, I'll merge this.

@corinnebosley#4 shows a silly bug.
We clearly need some more tests on this.
Plus, there are other improvements we really need to the code  currently in the Unstructured.
(E.G. bare "assert"s in the code; need to check passed cubes better; should handle additional properties of the passed cubes...).
I intend to address these by a separate effort after merging to master..
(promise :wink: )

Moving too fast here, made another mistake.
We now need @corinnebosley#5 here, too.


steerActualDelay actual value

Description
Controls tunables shouldn't be offset outside of interface.py, otherwise, the values will not work as expected. if the new MPC needs higher delays, that's fine; but let's make the values in interface accurate.
Verification
Should be obvious

The values in the car interfaces are only for the steering actuator. As the comment says, the other 0.2s is an estimate of the delay in other parts of the stack.

steerActuatorDelay is calculated by looking at the steer cmd and the torque output. If this delay if left in, regardless of where the lag is in controls, the calculated value will be skewed +0.2s
@pd0wm what are your thoughts here? steerActuatorDelay is a kludge that's used anyway to account for full stack delay and isn't represented by the actual plant model, anyway.

The 0.2 is about an upper limit of the time it takes to go from light hitting the sensor to reach plannerd. There are many steps from exposure, reading out the sensor, copying the picture a couple times and running modeld. I agree with @adeebshihadeh this value shouldn't be included in steerActuatorDelay since they come from other sources. Something like indi shouldn't use this extra 0.2 and only the actual steer actuator delay.

@pd0wm @adeebshihadeh
Maybe you guys can revert the .2s hack now that the stack lag is coming down, see @geohot 's enhancement here:
https://github.com/commaai/openpilot/pull/23795
from debayering, c3 cams are like 2 ms lag vs on C2 what used to be 8 and now is 3.5
C3 has a completely new camera stack vs C2

Doubt it. .2s is 200 ms. I don't think 4 ms will make a difference.


Chat-Registrations

Test registration for chat.
Does it work, is it unclear anywhere?

@IDotD/base anyone here who isn't registered? should just take 2-3 mins to test this

I think I registered an aeon of time ago, but forgot everything related to it. I actually had it on the plan a couple of times, already having some note written down to it. I am going to write more after a detailled testing.

There are two main issues I noticed when messing around with the buttons:

The chat window overlaps common information boxes, requiring one to close the chat window, closing the information box and then open the chat window again. It might be a good idea to display them in front of the chat window.
A more severe problem, information boxes of all kinds are spawned multiple times. You can see it in the screenshot on the lefthand site. Spawning one box of a kind and checking if it is still open when it should be spawned again might be a better approach.

As for registering itself, I feel as if information regarding data persistence and how to get back lost information could be helpful. What if I forget my password, what happens to chat-rooms I never log into again ( will they persist through time ?) and what should I do regarding registering multiple times, as example what should I do when I forget my information I registered with. Such questions feel unanswered to me.

What if I forget my password

You'd need a new account - or I'd need to require an email to be used for registration so a new password can be send.

what happens to chat-rooms I never log into again ( will they persist through time ?)

yes

and what should I do regarding registering multiple times, as example what should I do when I forget my information I registered with.

I'm not sure what issue you see here

nothing to do I guess :)


[Snyk] Security upgrade moment from 2.29.2 to 2.29.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

frontend/package.json
frontend/yarn.lock

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

768/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-JS-MOMENT-2944238
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

moment changelog


Adding footer

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
.
Use Case
.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Can you propose the design of it ? like a draft or some thing @mahek0620


virtualenv + python-future = broken virtualenv

Simplest reproduction:
$ virtualenv venv
$ ./venv/bin/pip install future virtualenv
Collecting future
  Using cached future-0.14.3.tar.gz
Collecting virtualenv
  Using cached virtualenv-12.1.1-py2.py3-none-any.whl
Installing collected packages: future, virtualenv
  Running setup.py install for future
Successfully installed future-0.14.3 virtualenv-12.1.1
$ ./venv/bin/virtualenv -ppython3.4 venv34
Running virtualenv with interpreter /usr/bin/python3.4
Traceback (most recent call last):
  File "/home/anthony/venv/local/lib/python2.7/site-packages/virtualenv.py", line 8, in <module>
    import base64
  File "/usr/lib/python3.4/base64.py", line 9, in <module>
    import re
  File "/usr/lib/python3.4/re.py", line 336, in <module>
    import copyreg
  File "/home/anthony/venv/lib/python2.7/site-packages/copyreg/__init__.py", line 7, in <module>
    raise ImportError('This package should not be accessible on Python 3. '
ImportError: This package should not be accessible on Python 3.

This is a bug in virtualenv since it's muddling up the 2.7 and 3.4 module paths. There are several similar issues reported upstream:
https://github.com/pypa/virtualenv/issues/745
https://github.com/pypa/virtualenv/issues/671
https://github.com/pypa/virtualenv/issues/625
https://github.com/pypa/virtualenv/pull/697
Better to use pyvenv that comes with Python 3.3+ for now.

pyvenv isn't really an option for a codebase targetting 2+3 (especially considering the many edgecases that pyvenv is not-quite-correct for (and cannot be fixed due to being stranded in the stdlib)).  Would there ever be potential plans to split the useful bits (backports, moves, etc.) from the shadowing of py3 module names?

Thanks for mentioning this, Anthony. I think having a Python 2.7 site-packages folder accessible to a Python 3.4 interpreter will lead to a lot of breakage in general. So I agree with Elliott that this is a virtualenv bug. (Perhaps a resurfacing of bug #673.)
I must admit that I haven't used virtualenv for 2 years (since I discovered conda). I'll try to find some time to tinker with it further to see what's going on. But, reading https://github.com/pypa/virtualenv/pull/697, I rather suspect it's a bird's nest of brittle hacks ...

Could you address the question?  Probably fine to close as wontfix after answering I would guess.

Would there ever be potential plans to split the useful bits (backports, moves, etc.) from the shadowing of py3 module names?

@qulogic @edschofield This is actually an effect of the pythonpath mining that we do at our company. We've since factored it out.

munging*

@bukzor it's actually not, see my reproduction

I just ran into this issue, looks like it was introducing in virtualenv 12.04, I've started pinning to virtualenv 12.02 without issues

fwiw, this is the commit that enabled it to work from virtualenv's side: https://github.com/pypa/virtualenv/commit/73d46a83f6b26155398310d8dfd251015c751030
It was however reverted later due to causing issues (?) on debian.
I've created my own wrapper script for virtualenv that also solves this problem: https://github.com/asottile/virtualenv-hax

Had the same issue. Downgrading to virtualenv 12.0.2 solved the problem.

Experiencing the same issue. My version is 13.1.2. Had to downgrade to 12.0.2 as valerymelou mentioned.

downgrading to 12.0.2 worked for me too

Are they going to fix the bug or what?

For Ubuntu 14.04, this combination worked for me:

Install pip for python 3.4 (https://pip.pypa.io/en/stable/installing/):

$ wget https://bootstrap.pypa.io/get-pip.py -O - | sudo python3.4

Replace the old virtualenv (python 2.7 to python 3.4) :

$ sudo pip3.4 install virtualenv

Just to check:

$ head -n 1 /usr/local/bin/virtualenv
#!/usr/bin/python3

Now, the following commands will run:

$ virtualenv venv34
Using base prefix '/usr'
New python executable in venv34/bin/python3
Also creating executable in venv34/bin/python
Installing setuptools, pip, wheel...done.

$ ./venv34/bin/pip install virtualenv
Collecting virtualenv
  Using cached virtualenv-13.1.2-py2.py3-none-any.whl
Installing collected packages: virtualenv
Successfully installed virtualenv-13.1.2

$ ./venv34/bin/virtualenv -p python venv
Running virtualenv with interpreter /usr/bin/python
New python executable in venv/bin/python
Installing setuptools, pip, wheel...done.

$ /usr/bin/python --version
Python 2.7.6

$ ./venv/bin/pip install future virtualenv
Collecting future
Collecting virtualenv
  Using cached virtualenv-13.1.2-py2.py3-none-any.whl
Installing collected packages: future, virtualenv
Successfully installed future-0.15.2 virtualenv-13.1.2

$ ./venv34/bin/pip install future
Collecting future
Installing collected packages: future
Successfully installed future-0.15.2

To avoid compilation errors from Python extensions written in C or C++ (ref):

$ sudo apt-get update
$ sudo apt-get install -y build-essential
$ sudo apt-get install -y python3.4-dev
$ sudo apt-get install -y python3-software-properties

Now, tox runs beautifully :)

Hi guys I saw your opinions, and fernandojunior recomendations work for me however rigth now i update my virtualenv to 14.0.5 and the trouble are fixed in this version, currently i am working in my host with linuxmint 17.3 x64

I'm getting this error without using virtualenv at all (as far as I can tell), as a result of ubuntu's use of py3:
$ asdfasdf
Traceback (most recent call last):
  File "/usr/lib/command-not-found", line 23, in <module>
    import gettext
  File "/usr/lib/python3.4/gettext.py", line 49, in <module>
    import locale, copy, io, os, re, struct, sys
  File "/usr/lib/python3.4/locale.py", line 17, in <module>
    import re
  File "/usr/lib/python3.4/re.py", line 336, in <module>
    import copyreg
  File "/usr/local/lib/python2.7/dist-packages/copyreg/__init__.py", line 7, in <module>
    raise ImportError('This package should not be accessible on Python 3. '
ImportError: This package should not be accessible on Python 3.
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 53, in apport_excepthook
    if not enabled():
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 24, in enabled
    import re
  File "/usr/lib/python3.4/re.py", line 336, in <module>
    import copyreg
  File "/usr/local/lib/python2.7/dist-packages/copyreg/__init__.py", line 7, in <module>
    raise ImportError('This package should not be accessible on Python 3. '
ImportError: This package should not be accessible on Python 3.

Original exception was:
Traceback (most recent call last):
  File "/usr/lib/command-not-found", line 23, in <module>
    import gettext
  File "/usr/lib/python3.4/gettext.py", line 49, in <module>
    import locale, copy, io, os, re, struct, sys
  File "/usr/lib/python3.4/locale.py", line 17, in <module>
    import re
  File "/usr/lib/python3.4/re.py", line 336, in <module>
    import copyreg
  File "/usr/local/lib/python2.7/dist-packages/copyreg/__init__.py", line 7, in <module>
    raise ImportError('This package should not be accessible on Python 3. '
ImportError: This package should not be accessible on Python 3.

What to do when the same error is gotten but using conda environments?

Closing as this conversation has stalled and there appears to be no remaining action for python-future.  Please reopen if I may be mistaken :)

yep yep! This got worked around in the virtualenv project


Add annotation access controls at the folder level

Transferred from DigitalSlideArchive/HistomicsUI and PR #217
Adds the ability to change the access list for all annotations in a folder (and optionally all annotations in the subfolders of the folder). The control can be found as an entry in the 'Folder actions' dropdown menu; it appears as long as the user owns at least one annotation in the folder (or it's subfolders) and only alters the permissions on the annotations that the user owns.
Closes DigitalSlideArchive/HistomicsUI issue #27

@eagw Can you merge master?  A recent change to one of the upstream libraries broke CI and there is a fix on that was merged to master.

This is working well in my test case.  After the last few comments are addressed, we can merge this.  I'd like to have a follow-on PR to add some tests of the end points, so at least we know we don't break them in the future.


Text in Text Editor with active dark mode is unreadable

Describe the bug
The text is black with a black background. This Bug was added with 5.8.2.

Firefox
Additional context
Firefox v100, Manjaro Linux
Relevant log output
No response

My stylesheet was still in the cache. After clearing the cache, the text is white again. If this is planned behavior, the issue can be closed.

Please confirm that you can switch back and forth without getting the above-mentioned issue again.

I am not 100% sure if switch back and forth on the exercise page would have solved the bug. But I am sure was re-opening the exercise multiple times. A shift+reload (reload without cache on firefox) solved the issue several minutes later.

I'm not asking whether this would have solved the issue (if it's because of the caching, it wouldn't have), but whether you can reproduce the issue now after clearing the cache when switching back and forth.

No, I cannot reproduce the issue with disabled cache. But I also cannot switch between Artemis Versions, which, in my opinion, most likely caused this issue.

With caching such an issue can occur for various reasons, e.g. if the cache gets corrupted.
As it works right now and it's not reproducible by switching back and forth between the modes, the most likely reason would be a caching issue.
I, therefore, close this issue as already suggested. In case this occurs again, feel free to reopen this with more information or write another issue.


Demo elementwise lowering of tensor to loops

Adds the MemRefElementTypeInterface to the polynomial type, and demonstrates the lowering to affine loops
bazel run //tools:heir-opt -- --convert-elementwise-to-linalg --one-shot-bufferize --convert-linalg-to-affine-loops $PWD/tests/polynomial/elementwise.mlir

The strange part is that lowering linalg to loops requires de-tensorizing the inputs to linalg.generic, which inserts bufferization.to_memref and bufferization.to_tensor as materializations. To completely eliminate those requires converting everything to memrefs, see https://github.com/google/heir/blob/main/tools/heir-opt.cpp#L85-L99
I tried running --polynomial-to-standard after this, but ran into another issue
/home/j2kun/fhe/heir/tests/polynomial/elementwise.mlir:8:8:
error: failed to legalize unresolved materialization from
'!polynomial.polynomial<<cmod=33538049, ideal=#polynomial.polynomial<1 + x**1024>>>'
to 'tensor<1024xi25>' that remained live after conversion
  %0 = polynomial.add(%arg0, %arg1) : tensor<2x!poly>
       ^
/home/j2kun/fhe/heir/tests/polynomial/elementwise.mlir:8:8:
note: see current operation: %7 = "builtin.unrealized_conversion_cast"(%6) :
 (!polynomial.polynomial<<cmod=33538049, ideal=#polynomial.polynomial<1 + x**1024>>>) -> tensor<1024xi25>
/home/j2kun/fhe/heir/tests/polynomial/elementwise.mlir:8:8:
note: see existing live user here: %8 = arith.extsi %6 : tensor<1024xi25> to tensor<1024xi26>

The strange part is that lowering linalg to loops requires de-tensorizing the inputs to linalg.generic, which inserts bufferization.to_memref and bufferization.to_tensor as materializations. To completely eliminate those requires converting everything to memrefs, see https://github.com/google/heir/blob/main/tools/heir-opt.cpp#L85-L99

That's a bit unfortunate, but it's great to see that there is a way after all ❤


Go module replace doesn't work when 2 levels deep

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

$ go version
go version go1.13.3 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/karl/.cache/go-build"
GOENV="/home/karl/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/karl/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/karl/tmp/c/go.mod"
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-build553992755=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I created 3 modules in the following directory structure:
.
├── a
│   ├── a.go
│   ├── a_test.go
│   └── go.mod
├── b
│   ├── b.go
│   ├── b_test.go
│   └── go.mod
└── c
    ├── c.go
    ├── c_test.go
    └── go.mod

The go files are just enough to form dependencies c -> b -> a:
a/a.go:
package a

import "fmt"

func DoIt() {
	fmt.Printf("Doing it\n")
}

b/b.go:
package b

import "github.com/test/a"

func DoA() {
	a.DoIt()
}

c/c.go:
package c

import "github.com/test/b"

func DoB() {
	b.DoA()
}

The test files are all empty, just enough to run go test successfully:
a/a_test.go:
package a

import "testing"

func TestNothing(t *testing.T) {

}

... b and c are the same.
The modules have replace statements:
a/go.mod:
module github.com/test/a

go 1.13

b/go.mod:
module github.com/test/b

go 1.13

replace github.com/test/a => ../a

c/go.mod:
module github.com/test/c

go 1.13

replace github.com/test/b => ../b

What did you expect to see?
$ cd a
$ go test
PASS
ok  	github.com/test/a	0.001s
$ cd ../b
$ go test
PASS
ok  	github.com/test/b	0.001s
$ cd ../c
$ go test
PASS
ok  	github.com/test/c	0.001s

What did you see instead?
$ cd a
$ go test
PASS
ok  	github.com/test/a	0.001s
$ cd ../b
$ go test
PASS
ok  	github.com/test/b	0.001s
$ cd ../c
$ go test
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>invalid version: git fetch -f https://github.com/test/a refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/karl/go/pkg/mod/cache/vcs/c0c8a2e25befe4efbfc70a367829c70c25266a092b79a63d54afae917f3e6b65: exit status 128:
	ERROR: Repository not found.
	fatal: Could not read from remote repository.

	Please make sure you have the correct access rights
	and the repository exists.

This is working as designed. Per https://golang.org/cmd/go/#hdr-The_go_mod_file:

Exclude and replace apply only in the main module's go.mod and are ignored in dependencies.

If you want to apply both replacements simultaneously, then you need both of those replace directives in the main module's go.mod file. (The “main module” is the module in whose directory the go command was invoked.)


on demand loading of shard and node data

remove the one time binding in this view because it prevented from seeing the relocation

Codecov Report

Merging #481 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #481   +/-   ##
=======================================
  Coverage   31.35%   31.35%
=======================================
  Files          20       20
  Lines        1974     1974
  Branches      237      237
=======================================
  Hits          619      619
  Misses       1307     1307
  Partials       48       48

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 c0a3b44...5dccd84. Read the comment docs.


INVOCATION endpoint error handler fails if exception has an empty args attribute

https://github.com/tavendo/AutobahnPython/blob/master/autobahn/wamp/protocol.py#L805 throws an UNHANDLED IndexError in that case.

ok. this is another instance similar to https://github.com/tavendo/AutobahnPython/blob/303d289de4993b5ffa9bf90c6fed71364f3521e7/autobahn/twisted/websocket.py#L111
py2/py3/tx can't agree if there is .message, .args and if there is .args if it is a tuple, and if so if it is of non-zero length.
we'll address that

Just found another bug/logical error: https://github.com/tavendo/AutobahnPython/blob/master/autobahn/wamp/protocol.py#L805 assumes that err is a twisted.Failure and thus have a value attribute which is an exception.
However https://github.com/tavendo/AutobahnPython/blob/master/autobahn/wamp/protocol.py#L820 indicates that this hasn't to be the case all the time (I guess if asyncio is used?).

@Paranaix those 820-823 checks are no longer required, as txaio ends up providing a wrapper so that it always has .value (in Twisted, it's always a Failure and in asyncio it's a FailedFuture provided by txaio).

@oberstet

py2/py3/tx can't agree if there is .message, .args and if there is .args if it is a tuple, and if so if it is of non-zero length.

The code should be careful when accessing exception attributes directly, specially if they may be user-defined ones, because user can change things like the availability of args etc.
For the purpose of extracting exception messages from possible user-defined exceptions (which is the case of this bug), the best approach IMHO is relying on __str__(). From the documentation:

The except clause may specify a variable after the exception name. The variable is bound to an exception instance with the arguments stored in instance.args. For convenience, the exception instance defines str() so the arguments can be printed directly without having to reference .args. One may also instantiate an exception first before raising it and add any attributes to it as desired.

Fixed by https://github.com/tavendo/AutobahnPython/pull/520


Composer loses focus in Internet Explorer 11

Hi,
First of all, I'm not a fan of IE, but some of my users (must) use it. And I suppose you want RainLoop to function with IE too :)
When I login and create a new email message the composer is in HTML mode in my setup. When I set it to plain text and then go about typing an email, the composer loses focus in about 1 to 5 seconds, making us unable to input text.
This also happens when I reply to a plain text email message because the composer will be in plain text mode. I don't see this behavior in Firefox.
I don't expect to see a message in the log about this, but enabled logging in application.ini anyway. But it doesn't show anything useful I think.
Can you (or anybody) reproduce this?
Thanks.

Can you (or anybody) reproduce this?

Unfortunately, I can't :(
Have you tested it with last version?
There are some fixes in the mail composer.

Of course. I forgot to mention. I updated to the latest version before logging this bug. I'll try to figure out what is going on. Could anyone give me some tips on how to debug this in IE?

I can confirm the problem. It still happens with current version of rainloop. The editor is not usable in plain text mode with IE 11. (I am on Windows 7 if that matters.)
Unfortunately I cannot investigate further because I am only using Windows at work and they pay me for debugging something else.

This issue is still present. When replying to an email using the plain text editor in IE/Edge, the cursor looses focus.
When using HTML editor, everything is working.


invoke tests directly with pytest

Fixes #353
Also fixes some test failures, let's see...

let's see now
gotta say that fc31's python-gitlab is pretty ancient: the errors were so bizzare


build(modern_bpf): relax bpftool version test.

What type of PR is this?
/kind cleanup

Any specific area of the project related to this PR?
/area build
/area driver-modern-bpf

Does this PR require a change in the driver versions?

What this PR does / why we need it:
For most use cases, bpftool version checking works fine, However, when using bpftool compiled from a kernel with backported patches, the version might not be the most reliable way to see if the required capabilities are avilable. As an example, RHEL 8.8 uses a bpftool with versions that match 4.18, but because of it having backported patches the modern probe can be compiled without errors. With this patch we move from checking a specific version to trying to catch if bpftool supports the gen command.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

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

Needs approval from an approver in each of these files:

driver/OWNERS [Molter73]

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

/cc @Andreagit97
LGTM btw :) waiting for the modern bpf expert ehhe

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

Needs approval from an approver in each of these files:

driver/OWNERS [Molter73,incertum]

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

LGTM label has been added.  Git tree hash: d5b7cc1916c727a639be64435e3a35cc4a4d68fc

/milestone 0.14.0

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

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97,Molter73,incertum]

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


Add character: 1 to font: boomer

Character :
Font :

Okay assign this issue to me

@rishavr920 would you like to take this?

yes sir plzz

Ok done


FuelError content is empty if "Content-Type" header is not provided by a server

Description
FuelError content is empty if Content-Type header is not provided by a server
To Reproduce
import com.github.kittinunf.fuel.core.Request
import com.github.kittinunf.fuel.core.FuelError
import com.github.kittinunf.result.Result

suspend fun <T> Request.requestWithAuthKey(
    clazz: Class<T>,
    permanentKey: String
): Unit {

    val (_, _, fuelResult) = appendHeader("AuthKey" to permanentKey)
        .authentication()
        .basic(userName, password)
        .awaitByteArrayResponseResult()

    when (fuelResult) {
        is Result.Failure -> logError()
        else -> { /* don't care */}
    }
}

fun Result.Failure<FuelError>.logError()

    val bytes = error.response.data // empty if Content-Type header is missing, OK, if present
    val len = error.response.contentLength; // always OK, number of response's bytes
    val body = error.response.body().asString("text/plain") // empty if Content-Type header is missing, OK, if present
}

Expected behavior
Error content should be extractable no matter whether or not response contains Content-Type header.
Development Machine
Complete the following information if applicable
Windows 10, Kotlin 1.3, Android Studio 3.6.3
Smartphone or Emulator
Xiaomi Redmi Note 8 Pro or Genymotion
Additional context
###Response headers
Date | Mon, 11 May 2020 15:44:59 GMT
-- | --
Server | Apache/2.4.35 (Win64) OpenSSL/1.1.1b PHP/7.2.19
Content-Length | bytes count here
Connection | close
Content-Type | application/json; charset=UTF-8 (or absent)

Response body
{  "testCyrillicValue": "абвгдеж"  }

If Content-Type is not given, we can not extract any content, because we don't know what the content is. We could expose the data stream and then you can use that directly -- or perhaps allow this behaviour for string content only, because that's generally safe.

@SleeplessByte , sorry if I've opened an issue for no reason.
The response could be octet/stream or whatever. And there's no any hint for library to guess what it should be. That's understood.
Which I cannot get is below:
my error.response.contentLength is 96 for example.
error.response.data is a byte array type. Why it's length is zero instead of 96?
If I try to get my response as stream it's also to no avail because of it's zero length.
So the more precise question is there any way I can get the same result with Fuel?

    val url = URL("http://localhost:8082")

    val connection = url.openConnection() as HttpURLConnection
    connection.apply {
        doOutput = true
        requestMethod = "POST"
    }

    if (connection.responseCode != 200) {
        connection.errorStream?.let {
            val bytes = it.readAllBytes() // not empty array is I'm expecting it with Fuel
            println (String(bytes, Charsets.UTF_8))
        }
    }

If you agree with me that this is an issue, and there is not too much to rewrite, we can discuss about me creating a Pull Request to fix that. (In my opinion, byte array length I get from Fuel should match the content length. Otherwise it's a leaky abstraction)

Content-Length ís a leaky abstraction. You can not use the Content-Length to determine the actual content-length, as soon as you have a chunked, gzip or br or deflate encoding. That's how it's specced up in HTTP standards. Nothing we can do about that.
Data should not be empty if there really is an error message. That is a 🐛 bug. We would love to fix that 👍 😄

Any news on resolution?
I'm worried that this problem occurs not only with errors but only with common response. If Content-Type is not provided the response is an empty byte array and so far I have not found a solution for this.
How can I do?


Optimize requests for comments

Right now a request for every comment is sent every time the post updates in the modal and that triggers a new request for every comment that comes from getting the avatar of the user.
Possible options:

Make a dictionary:

key: users name
value: the image source

Do not trigger a comment update upon post update after the first time the comments were pulled from the server

Optimized in 6695848c29003af401abe8fcd1e6d9fd72d4b550

Another fix in 6748ad23db05dc8f0be63f1b0ce486ea376e6293


Fixed gutter padding

There was no padding to the left of the line numbers.

Added in manually due to some file restructuring.


Fix nil selectrum--previous-input-string in CRM

When hitting the return key on a candidate while existing candidates have been selected already, I get (wrong-type-argument char-or-string-p nil).
I figured out it's because selectrum--previous-input-string is a buffer-local variable, which I think makes it nil later on inside with-temp-buffer which is used to clean up the candidate list and append on the selected one.
I'm pretty new to emacs and elisp in general, so while this fix works for me, maybe you can suggest a better one?

Thank you, this was introduced when reworking the session management, as all these variables are no longer let bound but buffer local now.

Thank you very much, looks all good to me now, is this ready to get merged from your side?

My pleasure. Yup, ready to merge. Did a final smoke test and still works fine for me.


[docs] Mention Toolpad in Example projects section

'Example projects' made more sense over Discover more -> 'Related projects' as the placement for Toolpad.
Also linked example folder from Toolpad repo.
Preview: https://deploy-preview-44391--material-ui.netlify.app/material-ui/getting-started/example-projects/

On what's the right place for linking Toolpad, it feels like it's the exact same case as https://github.com/mui/material-ui/pull/44315#discussion_r1827036286.

So if we want to proceed, I think we need to rewrite this whole section:

Did these changes. Removing /examples should be ok as all links take the user to their respective example folders.


Broken Click after upgrading to 0.12.0

Steps to reproduce
Tell us about your environment:

Puppeteer version:0.12.0
Platform / OS version: Mac OS Sierra
URLs (if applicable): Testing on LocalHost

What steps will reproduce the problem?
My existing working test started failing after upgrading to 0.12.0.
I was looking into similar issues with click. However, this seems different to me and this is the very first Step in my test. Is this because of the 'href' property in my css selector?
First step after launching browser, is to click on a main menu item and then on sub menu item, code for which is provided below.
This was very well working before upgrade.
This is NOT the ONLY place, where Click suddenly started failing. I am getting the "Error: Protocol error (DOM.getBoxModel): Could not compute box model. undefined" for various other buttons.
Please include code that reproduces the issue.
await page.click("div.menus ul.main a[href='#abc']");
await page.waitForSelector( "div.menus ul.sub a[href='#abc/childOfabc']", { visible: true } );
//I added the below focus just to verify its working and my selector is being recognized
await page.focus("div.menus ul.sub a[href='#abc/childOfabc']");
await page.click("div.menus ul.sub a[href='#abc/childOfabc']");
What is the expected result?
Expected is that Click works normally.
What happens instead?
Nothing happens. After default time out the test fails. Below is the error message.
(node:52818) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: waiting failed: timeout 30000ms exceeded
(node:52818) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The main problem here should be fixed by #1299, which properly handles retina display with DOM.getBoxModel. But I am very curious about the error Error: Protocol error (DOM.getBoxModel): Could not compute box model. undefined. Do you have a repro case for that? Thanks!

@divyamvn @patrickeakin can you guys please share a repro case where you experience the DOM.getBoxModel error?
Error: Protocol error (DOM.getBoxModel): Could not compute box model. undefined

I can confirm this also happens for<EMAIL_ADDRESS>

Thank you for the response.
One of the instances where the DOM.getBoxModel error occurs for me...
await page.focus( div.core-provider-appmenu-IndividualSearch input.searchinput.i-input );
await page.click( div.individualSelect.individualSelectAppMenu input.searchinput.i-input );
await page.type(div.individualSelect.individualSelectAppMenu input.searchinput.i-input, firstName + ' ' + lastName);
await page.waitFor("div.genericSearchResults div.button-wrap button");
//Error occurs on the below click
await page.click("div.genericSearchResults div.button-wrap button[data-buttonindex='0']");

@divyamvn can you please share the HTML as well? The issue seems to be with some specific property of the element you click.

The button wrap appears after searching for any text in an input field. The error occurs on clicking the buttons in the button-wrap.

No Results.

a
b
c

@divyamvn still doesn't reproduce for me. Can you please also paste CSS rules applied to the <button class="primary-btn" data-buttonindex="0">a</button>?

My current hypothesis is that the button is in the dom, but it is set to display: none, or a parent of it is set to display: none. This would make sense if the drop down didn't open in time. Then the error Error: Protocol error (DOM.getBoxModel): Could not compute box model. undefined will be thrown.
I have a patch #1309 which should make this error message clearer: Node is not visible

Thanks for the update.
@JoelEinbinder Shouldn't the waitForSelector visible or any of the wait methods work then?
I used waitForSelector for the button with visible true before clicking on it, which should help me wait until the button is visible right?
I anyway don't see any display: none rule on the element or any parent of it
Moreover the test never failed before I upgraded to 0.12.0.

 I have a follow up patch to make waitForSelector more robust, but right now it doesn't check the visibility of parent nodes.
Having the CSS applied to the button and button-wrap would be very helpful.

@JoelEinbinder @aslushnikov
I am getting the same " Error: Protocol error (DOM.getBoxModel): Could not compute box model. undefined" when trying to click the options on browser default combos.

await page.click("select.ui-datepicker-month");
await page.waitForSelector("#ui-datepicker-div > select.ui-datepicker-month > option");
await page.click( "#ui-datepicker-div > select.ui-datepicker-month > option:nth-child(4)");

If we think the combo dropdown is not showing up quickly and hence node is not found. How can I make any of the combos work? Only using keyboard inputs?
The page.select is not working for me on any of the combos including these. page.select results in this

I could resolve these issues as well, putting some extra hard coded waits.
You can close the issue. Thanks much!!

You should be able to use the visible option of waitFor now. See #1354.