[BUG]:Can't load the activity log

Describe the bug
A clear and concise description of what the bug is.
Unable to load the activity log or view test report links when running on the playwright service
To Reproduce
View playwright service dashboard
Expected behavior
See runs and test reports that I have run
Screenshots
If applicable, add screenshots to help explain your problem.

Setup information (please complete the following information):

Azure Subscription Id: 4dabc48d-ccda-4182-b789-2d8303fc12f0
Workspace Name: ExPUXE2EAME
Service trace Id (if available):
Log snippet (if available):
Browser on which tests are executed (if applicable): Edge
Time range (in PST) when the issue was experienced: 12/3/2024 12:45 - 3PM PST
Playwright Version: Latest
Client machine OS: Windows 11 Enterprise (SAW)
OS requested on Service: Linux

Additional context
Not sure if this is an issue on Playwright side or on my side. I have Owner role access for the subscription
Contact @mictaylor

Hi @mike-taylor99, I think you are trying to use AME tenant from secured machine, where one of our domain is not allowlisted. Allow us some time to allowlist it.

Hi @mike-taylor99 , We have completed the allowlisting and now it should work. please try.

Hi @puagarwa , thank you so much for the quick turnaround. I indeed am able to see the test runs and open the panel with the initial information and attachments for each test. I however am still encountering an issue when I try to view the stack trace for a test. Is this also AME related?

@mike-taylor99 , yes this is known issue because trace.playwright.dev domain is not allowlisted in secure machine. This would take some time to get resolved as its not microsoft.com domain.
Meanwhile, you can download the trace file in below manner and then browser trace.playwright.dev from non-secured machine and open the trace to proceed debugging.
How to download trace:
Url looks like this in browser when you try open trace: https://playwright.microsoft.com/workspaces/XXX/runs/XXXX/tests/XXXX/trace?trace=https://.....
you can copy everything after "trace=" and open it in new tab, which should download the trace zip file locally.
I will keep you updated on our progress to allowlist this domain.

Hi @puagarwa ,
I followed the steps mentioned above to download the stack trace and noticed that I can access the trace using the trace URL on my non-AME account. Could this be a potential SFI issue? The purpose of having this workspace on AME is to ensure that any sensitive data from our stack trace remains secure and isn’t easily accessible by others.

Hi @mike-taylor99 ,
Your purpose to use AME account make sense, I am working with security team to allowlist it.

Hi @puagarwa,
Awesome! Thanks for working to allowlisting it on AME. I have a concern regarding the link that directly downloads the stack trace. Is there any restriction on who can download the trace file if they acquire the link? I’m worried this could pose a security vulnerability if the stack trace link accidentally falls into the wrong hands. One of our reasons for using the AME workspace was to control where information can be retrieved from, but I’m concerned that posting the direct stack trace download link might put us at risk since there’s no restriction on who can download it.

HI @mike-taylor99 ,

Is there any restriction on who can download the trace file if they acquire the link?

Yes, the SAS url only generated when person can login into this portal using thier AME credential and have RBAC role, and then this SAS is valid for 1 hour from the time you generate it from our portal. Hence, it is safe.
Though, i agree getting this data out from Secure device may not be best security practice hence allowlisting this trace url would help so that you dont need to take it out of secure device.

HI @mike-taylor99 ,  Now the urls are allowlisted, you should be able to view trace from secure machine. please try and confirm.

Yes, it works now. Thank you so much for your help @puagarwa


gemini-pro-vision with streaming fails

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
import os
os.environ['GOOGLE_API_KEY'] = '<api key>'

import requests
import base64

image_url = "https://picsum.photos/seed/picsum/300/300"
content = requests.get(image_url).content

image_bytes = base64.b64encode(requests.get(image_url).content).decode("utf-8")

image_url = f"data:image/jpg;base64,{image_bytes}"

from langchain_core.messages import HumanMessage
from langchain_google_genai import ChatGoogleGenerativeAI

llm = ChatGoogleGenerativeAI(model="gemini-pro-vision")
# example

content = [
        {
            "type": "text",
            "text": "What's in this image?",
        },  # You can optionally provide text parts
        {"type": "image_url", "image_url": image_url},
    ]

message = HumanMessage(
    content=content
)

stream = True

if stream:
    for chunk in llm.stream([message]):
        print(chunk.content)
        print('---')
else:
    res = llm.invoke([message])
    print(res)

Error Message and Stack Trace (if applicable)
google.api_core.exceptions.InternalServerError: 500 An internal error has occurred. Please retry or report in https://developers.generativeai.google/guide/troubleshooting

Description
streaming with gemini-pro-vision fails with internal server error.
System Info
Using latest google packages
langchain==0.0.354
langchain-anthropic==0.1.3
langchain-community==0.0.8
langchain-core==0.1.6
langchain-experimental==0.0.47
langchain-google-genai==0.0.11
langchain-groq==0.0.1
langchain-mistralai==0.0.2

google-ai-generativelanguage==0.4.0
google-api-core==2.17.1
google-auth==2.28.2
google-generativeai==0.4.1
google-search-results==2.4.2
googleapis-common-protos==1.63.0
langchain-google-genai==0.0.11

Linux Ubutnu 22
python 3.10
but new langchain does same.

Transferred to the langchain-google repo that that integration lives in, and cc @lkuligin !

@markdaoust it looks like smth is flaky on genai side, the integration side has been failing from times to times recently.
it looks like streaming returns 500 from time to time.

This case it's 100% repro of failing, just FYI.

I found The Probleme With the Image URL , When I replace it with a Local Image path it Works
This my Code :
from langchain_core.messages import HumanMessage
from langchain_google_genai import ChatGoogleGenerativeAI
import os
from dotenv import load_dotenv
load_dotenv()
GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
llm = ChatGoogleGenerativeAI(model="gemini-1.5-flash",api_key=GOOGLE_API_KEY)
Image_Path = r"C:\Users\hp\Downloads\IMG_20240727_041422_037 (1).jpg"
message = HumanMessage(
content=[
{
"type": "text",
"text": "What's in this image?",
},  # You can optionally provide text parts
{"type": "image_url", "image_url": Image_Path},
]
)
response = llm.invoke([message])
print(response)


[Java] Configurable buffer size limit

Question
Since https://github.com/apache/fury/commit/01f1b66383a127a801f22ebe7fac5ca54d675878  Fury's internal MemoryBuffer is reset to 128k after every use.
The change makes sense because it reclaims memory that could otherwise sit unused, but it will cause massive allocations if most of the object graphs you serialize are >= 128k. In this case, a new buffer is allocated for every serialization.
In my application, most object graphs are 64k-512k leading to very frequent reallocation of the built-in buffer.
Currently, my only option is to manage a pool of MemoryBuffers myself and pass them to Fury instead of relying on the built-in buffer, but this makes using Fury significantly more complex.
Would it make sense to make the buffer size limit configurable? In my case, a 1MB limit would be ideal.

Make sense, would you like to add a new field at FuryBuilder/Config and use that value for Buffer reset

@chaokunyang: I pushed a PR for this, but I'm not sure if it is the right approach. Do you have any feedback?


url helper with relative_url_root

the gist is https://gist.github.com/1390486
# So I was trying to use named route helpers in sprockets, and the app was hosted in a subdirectory.
# This is what I came up with. Please share your hackeries.
#
# using named routes in sprocket Rails 3.1
# you can use this in app/assets/javascripts/bam.js.erb
# or any other erb sprocket asset

Rails.application.routes.url_helpers.bam_path(
  :script_name => ApplicationController.config.relative_url_root
)

any neater solution?

All of the url helpers are part of Rails.


fix: revert back to use normal query as pk is throwing error

[ ] make sure to check every query and mutation

done by #534


add StringFrom for std::nullptr_t values

In C++11, the nullptr_t type was introduced, and in some projects NULL
is defined as nullptr. In this case, the C++ compiler will produce
warnings when trying to convert NULL to a string, because it is
ambiguous which conversion is used.
test.cpp:89:2: error: call to 'StringFrom' is ambiguous
CHECK_EQUAL(NULL, actual);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/CppUTest/UtestMacros.h:127:3: note: expanded from macro 'CHECK_EQUAL'
CHECK_EQUAL_LOCATION(expected, actual, NULL, FILE, LINE)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/CppUTest/UtestMacros.h:138:52: note: expanded from macro 'CHECK_EQUAL_LOCATION'
UtestShell::getCurrent()->assertEquals(true, StringFrom(expected).asCharString(), StringFrom(actual).asCharString(), text, file, line);
^~~~~~~~~~
/usr/local/include/CppUTest/SimpleString.h:138:14: note: candidate function
SimpleString StringFrom(const void* value);
^
/usr/local/include/CppUTest/SimpleString.h:139:14: note: candidate function
SimpleString StringFrom(void (*value)());
^
/usr/local/include/CppUTest/SimpleString.h:141:14: note: candidate function
SimpleString StringFrom(const char *value);
^
/usr/local/include/CppUTest/SimpleString.h:137:14: note: candidate function
SimpleString StringFrom(bool value);
^
/usr/local/include/CppUTest/SimpleString.h:157:14: note: candidate function
SimpleString StringFrom(const SimpleString& other);
^
/usr/local/include/CppUTest/SimpleString.h:171:14: note: candidate function
SimpleString StringFrom(const std::string& other);
These warnings can be resolved by providing a StringFrom which takes the
nullptr_t as the argument, avoiding the need for conversions at all.
According to the C++ standard, the define __cplusplus is set to a value greater
than 199711L when C++ 11 is supported. Thus, we'll check this when implementing
the function, in order to allow building on older C++ standards.
Additionally, avoid a compiler warning due to the expected unused parameter in
the implementation of StringFrom.
Signed-off-by: Jacob Keller<EMAIL_ADDRESS>

Coverage remained the same at 99.874% when pulling 1bf992e641a499cf424890b2fcdd68175b928574 on jacob-keller:jk-nullptr-type-cpp11 into 2edc6bb96c792f5a097013bff54111b1700f8db0 on cpputest:master.

This should fix https://github.com/cpputest/cpputest/issues/1158

The appveyor tests appear to be failing due to MinGW installations missing?? I don't think that's related to this patch.

/home/travis/build/cpputest/cpputest/tests/CppUTest/SimpleStringTest.cpp:581:34: error: zero as null pointer constant [-Werror,-Wzero-as-null-pointer-constant]
    CHECK_EQUAL(nullptr, (void *)0);
                                 ^
                                 nullptr
/home/travis/build/cpputest/cpputest/include/CppUTest/UtestMacros.h:127:34: note: expanded from macro 'CHECK_EQUAL'
  CHECK_EQUAL_LOCATION(expected, actual, NULLPTR, __FILE__, __LINE__)
                                 ^

I was trying to see if nullptr and 0 would compare properly in the new test case, but it turns out this causes warnings. Any suggestions?

Perhaps cast it to nullptr_t ?

Perhaps cast it to nullptr_t

Maybe. I was trying to avoid that to see whether we actually treat nullptr_t and 0 as the same when checking null pointers..

Ok, this should be complete. I've got checks for the C++ version, and a test case to ensure that stringfrom works, and that CHECK_EQUAL works.

The travis build is still failing though ?

Ok, so it doesn't like type casting 0 to a nullptr...

`
C:\cygwin\bin\bash.exe : configure.ac:11: installing './compile'
At line:1 char:1

C:\cygwin\bin\bash.exe --login -c 'cd /cygdrive/c/projects/cpputest/c ...

  + CategoryInfo          : NotSpecified: (configure.ac:11: installing './compile':String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

configure.ac:11: installing './config.guess'
configure.ac:11: installing './config.sub'
configure.ac:4: installing './install-sh'
configure.ac:4: installing './missing'
Makefile.am: installing './INSTALL'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
Executing <../configure> in </cygdrive/c/projects/cpputest/cpputest_build>
checking for a BSD-compatible install... /usr/b
`
Not sure what the problem is here?

I don't understand the failure on cygwin...

Seems to be caused by network. I restarted, now it is good.


Enable GIT_TRACE

Only process stdout when shelling out to git instead of combined stdout + stderr. In most cases, we want to silence stderr because we attach a custom error message to failure scenarios. In some other cases, have stderr be attached to stderr of parent process.
Fixes https://github.com/github/hub/issues/2134

Thanks!


Desktop Version RWD

Your project looks great so far, we can see a good effort on it 👌.
Please take into account the following comments:

[ ] Please try to align the items of your project according to sigma template design.
[ ] Please place the labels above each input and text area field.
[ ] Please define the height of the text area field in order to not be modified by the user.
[ ] Please see each detail from the desktop version as they could change from the mobile version in Figma.

We hope these comments can help to improve your project.

Well developed code!!! 🥳
I really have nothing to say.
Why not consider deleting the parts of the code you used and commenting out?
Non-useful code comments could make your code look less than clean.

Happy Coding 🍾


clean commandline arguments

I want the commandline arguments to be well documented and interchangeable. Right now all the options have to appear in one specific order. i want that to be unnecessary

done in  4d95fa0


CCRL compliance

Hi Ellie,
I'd like to test your engine for our rating list but I'm afraid the engine is not ready for CCRL testing conditions yet. We use x time for y moves time controls (for the 40/15 list) and x base time + y increment time for the blitz list. As I see it, the only way I could use Homura is with time controls of time per move but then the opponent has to use the same time control (no GUI I know is capable for using different time control for white and black), which is a handicap for it. Also, I'd have to set the time for move to a relatively low value lest time forfeits occur.
Gabor Szots
CCRL testing group

Hi Gabor,
I am sorry for my delay in responding. I have been very busy at my new job for the last few weeks, and I am finally checking GitHub again. I would love to see how Homura does on the CCRL's! I will try to add the necessary UCI commands sometime within the next few months.
I am in the process of obtaining new hardware to run quick SPRT tests and determine what is gaining/losing ELO. I am taking a little break in the meantime.
I may push the time control changes to this repository, but I plan to leave the rest of the code here as-is since the engine is described in detail in my honors thesis paper. After the time control changes, I intend to continue working in a different repository.
Ellie


Added Data8 course and inferential thinking link

Issue #74

Data8 course link
Computational and Inferential Thinking textbook link.

Sub-points include:

Definition of data science as per the textbook
Idea behind the course as described by Prof. Micheal Jordon in the youtube video

Let me know if this looks good to you.
Thanks.

This is a good spot to add it. After that link change, ready to merge.

Ping. Want me to finish this up? I certainly don't mind.

Oops. I somehow thought we were just waiting few days to see if the certificate issue on Datascienceweekly.org resolves itself(from domain owners). I will take care of it by Wednesday if that's ok(currently on the move).

No problem, no rush :-)
On Sun, Oct 22, 2017 at 5:01 AM Ankit Kulshreshtha<EMAIL_ADDRESS>wrote:

Oops. I somehow thought we were just waiting few days to see if the
certificate issue on Datascienceweekly.org resolves itself(from domain
owners). I will take care of it by Wednesday if that's ok(currently on the
move).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hangtwenty/dive-into-machine-learning/pull/78#issuecomment-338472077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTv0EZn3sbAwzHgG7UOWlkvmwALFi1xks5suy57gaJpZM4PzPcN
.

--
Michael

@hangtwenty I triggered another build and now few other links are throwing error. Can you please advice me if I am doing something wrong or this is expected. Also, when I visit the links directly I get a successful response.
https://travis-ci.org/hangtwenty/dive-into-machine-learning/builds/292946825

@ankitkul You didn't cause any issue. It was just flaky connectivity as you suggested. I have merged. Apologies for the delay! Very hectic week over here. Thanks again.

@hangtwenty Awesome...Not an issue, I can understand. Thanks.


TAH 1.4, Fix nestId

TAH 1.4: Update to support Token Action HUD Core 1.4.
Fix nestId: Fix nestId in default layout.

Try this.
I've replaced the nestId in the default layout as it needs to be a combination of the parent and child, e.g., parent-group_child-group.
You will probably need to clear out any previously saved data. You can either execute these two functions: game.tokenActionHud.resetAllActorData() and game.tokenActionHud.resetAllUserData() or just delete the 'token-action-hud-core' folder in your 'data' directory (not in 'modules').


README still references darlingdata.tech

README still references https://darlingdata.tech, should reference https://roady.tech

resolved


[Bug] internal error when click the run_id of a child workflow in temporal web

Describe the bug
I can see the parent & child workflow listed in temporal UI, when I clicked the run_id of the child workflow, it shows a error message and display nothing in the screen. Parent workflow is fine.
parent workflow history:
bash-5.0# tctl --namespace=tempo workflow showid  12117851:schedule
   1  WorkflowExecutionStarted              {WorkflowType:{Name:ScheduleInstallmentWorkflow}, ParentInitiatedEventId:0, TaskQueue:{Name:default, Kind:Normal},
                                            Input:[{"PaymentScheduleId":12117851,"WorkflowId":"12117851:schedule","DueTime":"2021-05-18T00:00:00+10:00"}],
                                            WorkflowExecutionTimeout:0s, WorkflowRunTimeout:0s, WorkflowTaskTimeout:10s, Initiator:Unspecified,
                                            OriginalExecutionRunId:9cfd1916-d414-41aa-9aca-3039195e5917, Identity:1037634@riskbox@,
                                            FirstExecutionRunId:9cfd1916-d414-41aa-9aca-3039195e5917, Attempt:1, FirstWorkflowTaskBackoff:0s}
   2  WorkflowTaskScheduled                 {TaskQueue:{Name:default,
                                            Kind:Normal},
                                            StartToCloseTimeout:10s,
                                            Attempt:1}
   3  WorkflowTaskStarted                   {ScheduledEventId:2, Identity:1037677@riskbox@,
                                            RequestId:c326b2b9-021b-4e16-8a5f-5a1fda0567b6}
   4  WorkflowTaskCompleted                 {ScheduledEventId:2, StartedEventId:3,
                                            Identity:1037677@riskbox@,
                                            BinaryChecksum:22569b8b25a13d319e617cc9962c151f}
   5  MarkerRecorded                        {MarkerName:SideEffect,
                                            Details:map{data:["2021-04-20T15:22:12.416554388+10:00"],
                                            side-effect-id:[1]}, WorkflowTaskCompletedEventId:4}
   6  TimerStarted                          {TimerId:6,
                                            StartToFireTimeout:1m0.020554535s,
                                            WorkflowTaskCompletedEventId:4}
   7  TimerFired                            {TimerId:6, StartedEventId:6}
   8  WorkflowTaskScheduled                 {TaskQueue:{Name:riskbox:bf03bc96-b8c7-44b8-a0dd-4ede7c3160e0,
                                            Kind:Sticky}, StartToCloseTimeout:10s, Attempt:1}
   9  WorkflowTaskStarted                   {ScheduledEventId:8, Identity:1037677@riskbox@,
                                            RequestId:99e92743-752b-4675-9e49-437e9f6d26b3}
  10  WorkflowTaskCompleted                 {ScheduledEventId:8, StartedEventId:9,
                                            Identity:1037677@riskbox@,
                                            BinaryChecksum:22569b8b25a13d319e617cc9962c151f}
  11  StartChildWorkflowExecutionInitiated  {Namespace:tempo, WorkflowId:12117851:attempt-1,
                                            WorkflowType:{Name:AttemptInstallmentWorkflow}, TaskQueue:{Name:default, Kind:Normal},
                                            Input:[{"PaymentScheduleId":12117851,"DueTime":"2021-04-20T15:23:12.416554388+10:00","WorkflowIdx":1,"WorkflowId":"12117851:at
                                            tempt-1"}], WorkflowExecutionTimeout:0s, WorkflowRunTimeout:0s, WorkflowTaskTimeout:10s, ParentClosePolicy:Terminate,
                                            WorkflowTaskCompletedEventId:10, WorkflowIdReusePolicy:AllowDuplicate}
  12  ChildWorkflowExecutionStarted         {Namespace:tempo, InitiatedEventId:11,
                                            WorkflowExecution:{WorkflowId:12117851:attempt-1,
                                            RunId:7f5b7a51-616f-4dca-ae9d-93aab5aa1461},
                                            WorkflowType:{Name:AttemptInstallmentWorkflow}}
  13  WorkflowTaskScheduled                 {TaskQueue:{Name:riskbox:bf03bc96-b8c7-44b8-a0dd-4ede7c3160e0,
                                            Kind:Sticky}, StartToCloseTimeout:10s, Attempt:1}
  14  WorkflowTaskStarted                   {ScheduledEventId:13,
                                            Identity:1037677@riskbox@,
                                            RequestId:a7cd7ba1-6ffe-4675-94dc-cd4da8988018}
  15  WorkflowTaskCompleted                 {ScheduledEventId:13, StartedEventId:14,
                                            Identity:1037677@riskbox@,
                                            BinaryChecksum:22569b8b25a13d319e617cc9962c151f}
  16  ChildWorkflowExecutionCompleted       {Namespace:tempo,
                                            WorkflowExecution:{WorkflowId:12117851:attempt-1,
                                            RunId:7f5b7a51-616f-4dca-ae9d-93aab5aa1461},
                                            WorkflowType:{Name:AttemptInstallmentWorkflow},
                                            InitiatedEventId:11, StartedEventId:12}
  17  WorkflowTaskScheduled                 {TaskQueue:{Name:riskbox:bf03bc96-b8c7-44b8-a0dd-4ede7c3160e0,
                                            Kind:Sticky}, StartToCloseTimeout:10s, Attempt:1}
  18  WorkflowTaskStarted                   {ScheduledEventId:17,
                                            Identity:1037677@riskbox@,
                                            RequestId:fc88b2ae-f8c0-4a4e-a480-1cb6f3d35a90}
  19  WorkflowTaskCompleted                 {ScheduledEventId:17, StartedEventId:18,
                                            Identity:1037677@riskbox@,
                                            BinaryChecksum:22569b8b25a13d319e617cc9962c151f}
  20  WorkflowExecutionCompleted            {WorkflowTaskCompletedEventId:19}

child workflow history:
bash-5.0# tctl --namespace=tempo workflow showid  12117851:attempt-1
   1  WorkflowExecutionStarted    {WorkflowType:{Name:AttemptInstallmentWorkflow}, ParentWorkflowNamespace:tempo,
                                  ParentWorkflowExecution:{WorkflowId:12117851:schedule, RunId:9cfd1916-d414-41aa-9aca-3039195e5917},
                                  ParentInitiatedEventId:11, TaskQueue:{Name:default, Kind:Normal},
                                  Input:[{"PaymentScheduleId":12117851,"DueTime":"2021-04-20T15:23:12.416554388+10:00","WorkflowIdx":1,"WorkflowId":"12117851:at
                                  tempt-1"}], WorkflowExecutionTimeout:0s, WorkflowRunTimeout:0s, WorkflowTaskTimeout:10s, Initiator:Unspecified,
                                  OriginalExecutionRunId:7f5b7a51-616f-4dca-ae9d-93aab5aa1461, FirstExecutionRunId:7f5b7a51-616f-4dca-ae9d-93aab5aa1461, Attempt:1,
                                  FirstWorkflowTaskBackoff:0s}
   2  WorkflowTaskScheduled       {TaskQueue:{Name:default,
                                  Kind:Normal},
                                  StartToCloseTimeout:10s,
                                  Attempt:1}
   3  WorkflowTaskStarted         {ScheduledEventId:2, Identity:1037677@riskbox@,
                                  RequestId:0ce213df-2ae2-4240-9acf-38a07a111ee9}
   4  WorkflowTaskCompleted       {ScheduledEventId:2, StartedEventId:3,
                                  Identity:1037677@riskbox@,
                                  BinaryChecksum:22569b8b25a13d319e617cc9962c151f}
   5  MarkerRecorded              {MarkerName:LocalActivity,
                                  Details:map{data:[{"ActivityID":"1","ActivityType":"GetPaymentScheduleActivity","ReplayTime":"2021-04-20T05:23:13.246683648Z","A
                                  ttempt":0,"Backoff":0}],
                                  result:[{"Details":{"Status":1},"OrderTransaction":{"ConsumerAccountId":3028370,"MerchantId":600123846,"PaymentMethodId"
                                  :53714,"OrderTransactionId":600124068030,"ChannelType":1,"Status":1}}]}, WorkflowTaskCompletedEventId:4}
   6  MarkerRecorded              {MarkerName:LocalActivity,
                                  Details:map{data:[{"ActivityID":"2","ActivityType":"VerifyMerchantActivity","ReplayTime":"2021-04-20T05:23:13.246954736Z","Attem
                                  pt":0,"Backoff":0}], result:[{"Enabled":true}]}, WorkflowTaskCompletedEventId:4}
   7  MarkerRecorded              {MarkerName:LocalActivity,
                                  Details:map{data:[{"ActivityID":"3","ActivityType":"GetPaymentMethodsActivity","ReplayTime":"2021-04-20T05:23:15.091033229Z","At
                                  tempt":0,"Backoff":0}], result:[{"Details":[{"Id":53714,"TopazToken":"8252010DC6244A50BFDF464C2C2AA9F3","Type":1,"Name":"John
                                  Doe","CountryCode":"AUSTRALIA","Brand":"VISA"}]}]}, WorkflowTaskCompletedEventId:4}
   8  MarkerRecorded              {MarkerName:LocalActivity,
                                  Details:map{data:[{"ActivityID":"4","ActivityType":"AttemptInstallmentActivity","ReplayTime":"2021-04-20T05:23:16.284732672Z","A
                                  ttempt":0,"Backoff":0}], result:[{"Status":0}]}, WorkflowTaskCompletedEventId:4}
   9  TimerStarted                {TimerId:9,
                                  StartToFireTimeout:2m0s,
                                  WorkflowTaskCompletedEventId:4}
  10  WorkflowExecutionSignaled   {SignalName:attempt-installment-0,
                                  Input:[{"type":"tempo-online","version":1,"workflow_id":"12117851:attempt-1","channel_name":"attempt-installment-0","Status":3
                                  ,"PaymentId":84893}], Identity:1037634@riskbox@}
  11  WorkflowTaskScheduled       {TaskQueue:{Name:riskbox:bf03bc96-b8c7-44b8-a0dd-4ede7c3160e0,
                                  Kind:Sticky}, StartToCloseTimeout:10s, Attempt:1}
  12  WorkflowTaskStarted         {ScheduledEventId:11,
                                  Identity:1037677@riskbox@,
                                  RequestId:9b969c5b-695c-4291-8b36-ee28e852e437}
  13  WorkflowTaskCompleted       {ScheduledEventId:11, StartedEventId:12,
                                  Identity:1037677@riskbox@,
                                  BinaryChecksum:22569b8b25a13d319e617cc9962c151f}
  14  MarkerRecorded              {MarkerName:LocalActivity,
                                  Details:map{data:[{"ActivityID":"5","ActivityType":"SendNotificationActivity","ReplayTime":"2021-04-20T05:23:25.176397101Z","Att
                                  empt":0,"Backoff":0}]}, WorkflowTaskCompletedEventId:13}
  15  WorkflowExecutionCompleted  {WorkflowTaskCompletedEventId:13}

desc:
bash-5.0# tctl --namespace=tempo wf desc -w 12117843:attempt-1
{
  "executionConfig": {
    "taskQueue": {
      "name": "default",
      "kind": "Normal"
    },
    "workflowExecutionTimeout": "0s",
    "workflowRunTimeout": "0s",
    "defaultWorkflowTaskTimeout": "10s"
  },
  "workflowExecutionInfo": {
    "execution": {
      "workflowId": "12117843:attempt-1",
      "runId": "946f0088-2655-4eb2-a16d-0bae97546e0f"
    },
    "type": {
      "name": "AttemptInstallmentWorkflow"
    },
    "startTime": "2021-04-20T03:12:03.539595831Z",
    "closeTime": "2021-04-20T03:12:10.233454571Z",
    "status": "Completed",
    "historyLength": "15",
    "parentNamespaceId": "e73503a7-84d1-41f2-b1a0-e3b0e7bd1231",
    "parentExecution": {
      "workflowId": "12117843:schedule",
      "runId": "7e5088f3-6fb6-4bf5-aba6-abe0e27bd872"
    },
    "memo": {
    },
    "searchAttributes": {
      "indexedFields": {
        "BinaryChecksums": "[\"f0b1e5af914b674fdd635d83f2af5f6d\"]"
      }
    },
    "autoResetPoints": {
      "points": [
        {
          "binaryChecksum": "f0b1e5af914b674fdd635d83f2af5f6d",
          "runId": "946f0088-2655-4eb2-a16d-0bae97546e0f",
          "firstWorkflowTaskCompletedId": "4",
          "createTime": "2021-04-20T03:12:03.989912616Z",
          "resettable": true
        }
      ]
    }
  }
}

bash-5.0# tctl admin cluster d
{
  "supportedClients": {
    "temporal-cli": "\u003c2.0.0",
    "temporal-go": "\u003c2.0.0",
    "temporal-java": "\u003c2.0.0",
    "temporal-server": "\u003c2.0.0"
  },
  "serverVersion": "1.8.2",
  "membershipInfo": {
    "currentHost": {
      "identity": "<IP_ADDRESS>:7233"
    },
    "reachableMembers": [
      "<IP_ADDRESS>:6939",
      "<IP_ADDRESS>:6934",
      "<IP_ADDRESS>:6933",
      "<IP_ADDRESS>:6935"
    ],
    "rings": [
      {
        "role": "frontend",
        "memberCount": 1,
        "members": [
          {
            "identity": "<IP_ADDRESS>:7233"
          }
        ]
      },
      {
        "role": "history",
        "memberCount": 1,
        "members": [
          {
            "identity": "<IP_ADDRESS>:7234"
          }
        ]
      },
      {
        "role": "matching",
        "memberCount": 1,
        "members": [
          {
            "identity": "<IP_ADDRESS>:7235"
          }
        ]
      },
      {
        "role": "worker",
        "memberCount": 1,
        "members": [
          {
            "identity": "<IP_ADDRESS>:7239"
          }
        ]
      }
    ]
  }
}

Expected behavior
I want to see the info propertly when I clicked the run_id
Screenshots

Desktop (please complete the following information where relevant):
OS: OSX
Browser: Chrome
Temporal Web Version: 1.8.1
server: 1.8.2

does this happen only when you navigate to the child workflow from the parent history page when pressing run_id (12117851:attempt-1) or this also reproes when you navigate to 12117851:attempt-1 from the /workflows page ?

also, what sdk do you use, java/go/..?

Thanks @feedmeapples , thanks for responding.
I'm using the go sdk.
It happens both when I open it from parent history page and from /workflow page.

the problem was resolved.
you could see my diff

in previous I return nil in my activity, that would cause the issue.
now I add the return value. the web can work fine.

@zYeee if that's the same issue, there was a fix in Go sdk that should address this issue https://github.com/temporalio/sdk-go/commit/8e45a8da8d8ed6ea4bfc49750029c1c53fba2f72
The versions of sdk that are newer than Feb 22 should work properly
What is the sdk version that you use?

@zYeee if that's the same issue, there was a fix in Go sdk that should address it temporalio/sdk-go@8e45a8d
The versions of sdk that are newer than Feb 22 should work properly
What is the sdk version that you use?

I'm using the version of 1.2.0

ok, then feel free to use sdk-go versions v1.5.0 or newer if you want to return nil

Thanks for supporting !

Looks like we need to revisit the GoSDK fix and then test Temporal Web if it still works.

@samarabbas @feedmeapples is there some matching issue in the SDK repo? what fix do we need to do?


Add alt to images with text

What
Updating the homepage images with alt copy.
Why
These images aren't just decorative as they contain text that's not visible AT

Previously the text in the image has been added to the body text below the image. Could be worth asking a content designer if they think that this is possible? As a bonus, this would better align with the advice for describing images.

Advised being raised directly with Coronavirus Content to update.

Closing as has been resolved:


log to console random employee

issue#12: randomly select one employee, and using template literal, log his/here full name to the console.
issue#10: log correct amount of average salary. "For-loop" is fixed: prevSalary got updated every single loop. Before: it was zero and sumSalary was not updated correctly for every single loop, so it was equal to current salary.

issue#12 is fixed and issue#10 is corrected

close Issues##10&12


Async vault usage option.

Please add async vault support if you have time. It would be nice to switch between sync and async vault in the config.
Many money plugins perform SQL queries upon money change. Most of them support async usage.
The option to use the vault api async could prevent short lag spikes resulting from SQL queries or similar
slow operation performed by the money plugin on the main thread.

Thanks for your request. As far as I can tell, Vault doesn't offer any kind of asynchronous API. Whether this is because the developers do not care to, or because not all of its operations are thread safe, I cannot say. However, as Quests does not check balances on a regular basis (mainly only to issue rewards and check requirements), the benefits would be minimal. Therefore, I am not interested in looking into this further unless you have an error report or evidence of significant time savings.

Vault just passes the call to the underlaying money plugin. Some of them support async call's some don't. Depending on the money plugin used it can take less than a millisecond or up to half a second.
I wrote this because I noticed every time a player gained money by fulfilling a quest a short lagspike (150ms) was visible on our tps monitoring tool. On its own that's not much, but players could exploit this to drop the server performance.


Issue on page /notebooks/07-R.html

"x == True" is a common code smell, let's fix it in the notes:
a <- TRUE
if (a == TRUE){
    print ("a is TRUE")
    } else {
    print ("a is FALSE")
}

Yes, sorry. I copied the code verbatim to make it clear which example I was referring to. I think this should be
if (a) {
  ...

instead.

Yeah. I don't like truthy tests, on balance. Better to be explicit about what the test value is expected to be. If test_var is a bool: sure, PEP8 says if testvar: is canon, but otherwise it can lead to hard bugs.

Closed, keeping it explicit, with a note comparing Pythion to R. Also made revisions to Python I for this.


Error in get_dataset.py

Hello,
I was very impressed by your fascinating research. It is truly excellent and commendable.
However, I encountered some issues with the data while attempting to replicate the results. Following your instructions, I installed Qlib by running: git clone https://github.com/SJTU-DMTai/qlib.git
During this process, I applied the instruction to “copy the contents of the DropExtremeLabel class from MATCC/util/DropExtremeLabel.py to qlib/data/dataset/processor.py.”
I have a couple of questions regarding this:

Additional Code in DropExtremeLabel.py: The DropExtremeLabel.py file contains other code besides the DropExtremeLabel class. Should I also copy these additional codes into the qlib folder and replace the existing contents?
Boolean Differences in Some Codes: I noticed that some boolean values differ from the original Qlib implementation. For example, in the case of DropnaLabel, the is_for_infer method returns True, which is the opposite of Qlib’s return value. Could you please explain the reason behind this structure?

Additionally, when I only copy the DropExtremeLabel class and paste it into processor.py, I encounter the following error:
File "data/get_dataset.py", line 57, in <module>
    h.to_pickle(h_path, dump_all=True)
  File "/opt/conda/lib/python3.8/site-packages/qlib/utils/serial.py", line 133, in to_pickle
    self.get_backend().dump(self, f, protocol=C.dump_protocol_version)
PicklingError: Can't pickle <class 'data_DropExtremeLabel.DropnaLabel'>: it's not the same object as data_DropExtremeLabel.DropnaLabel

I would greatly appreciate your assistance in resolving these issues. Thank you very much for your time and support.

Really appreciate your detailed explanation.


Free trial billing page remove onboarding flow and minor text changes.

discussion: https://chat.zulip.org/#narrow/stream/273-kandra-billing/topic/Drop.20special.20text.20from.20.2Fbilling.20page.20for.20free.20trials.20.2327685

before
after

Looks great to me!

Should this be marked as closing #27685? Or do we want to keep it open to track making billing frequency into a dropdown?

Merged, thanks @amanagr!

Opened #27855 to track adding dropdown.


Stub out the RSS project

A number of stub files were added for classes that are expected to be needed in the RSS project.  A few additional files were copied from the arxiv-zero project and modified for use here.  Sample blueprint code was copied from the arxiv-browse project in order to confirm that the development environment and initial routes code was being executed and running correctly.
Later submissions will build the RSS functionality from the top down.
I am sure I included things here that aren't needed and failed to include other things that are necessary.  I look forward to your feedback!

Looks good in general; I can't speak to whether using celery makes sense here. I've not used it myself. The mypy.ini may be a bit off as we've changed it a bit; here's a more modern one (just change [browse.*] to [rss.*]`: https://raw.githubusercontent.com/cul-it/arxiv-browse/develop/mypy.ini
The directory hierarchy (and thus the module hierarchy) is pretty flat at the moment, but I think that is fine until more complexity is added.


Make sure all schematic symbol names are lowercase, all files names are lowercase, and add Typescript check that all symbols are lowercase

[ ] schematic symbol names are lowercase
[ ] all schematic symbol files names are lowercase
[ ] Typescript check that all symbols are lowercase

Go for it! I think youre a new contributor, we don't do assignments to prevent people from hanging on to issues

hey @seveibar im working on the issue can you please elaborate what are the requirements from typescript


Multi DB with SequelRails (issues and possible solution way)

When multiple databases used with Sequel' s internal system, SequelRails tries to log connection and using this connection for all models even if model belongs to another connection.
Problem
SequelRails has an ActiveSupport Notification instrument. When anything goes to this, primary (default) connection is used for all models regardless which model belongs to which connection.
See below stack trace. You will see that emails table does not exists. It's because SequelRails executes this in primary database which has no emails table. When I debug line-by-line, I see that conn value is my primary database and not secondary.
How I solved this?
Not quite correct but commenting/removing this line: https://github.com/TalentBox/sequel-rails/blob/master/lib/sequel_rails/sequel/database/active_support_notification.rb#L21
solves my problem. Simply I tell SequelRails to only log but not raise error.
Question.
Do you have any other idea how we can overcome on this? Monkey-patch using lib/ dir or any other idea?
Stack error:
I, [2018-12-24T15:27:23.097385 #6287]  INFO -- : Refreshing Gem list
Sequel::DatabaseError: PG::UndefinedTable: ERROR:  relation "emails" does not exist
LINE 1: SELECT * FROM "emails" LIMIT 1
                      ^
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:152:in `async_exec'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:152:in `block in execute_query'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-rails-1.0.1/lib/sequel_rails/sequel/database/active_support_notification.rb:17:in `block in log_connection_yield'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/notifications.rb:168:in `block in instrument'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/notifications.rb:168:in `instrument'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-rails-1.0.1/lib/sequel_rails/sequel/database/active_support_notification.rb:11:in `log_connection_yield'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:152:in `execute_query'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:140:in `block in execute'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:116:in `check_disconnect_errors'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:140:in `execute'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:496:in `_execute'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:314:in `block (2 levels) in execute'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:518:in `check_database_errors'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:314:in `block in execute'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/connection_pool/threaded.rb:92:in `hold'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/database/connecting.rb:270:in `synchronize'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:314:in `execute'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/dataset/actions.rb:1083:in `execute'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/adapters/postgres.rb:610:in `fetch_rows'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/dataset/actions.rb:151:in `each'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel_pg-1.11.0/lib/sequel_pg/sequel_pg.rb:81:in `each'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/dataset/actions.rb:85:in `columns!'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/dataset/actions.rb:75:in `columns'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/model/base.rb:242:in `columns'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-auditer-0.1.0/lib/sequel/plugins/auditer.rb:118:in `block in configure'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-auditer-0.1.0/lib/sequel/plugins/auditer.rb:92:in `instance_eval'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-auditer-0.1.0/lib/sequel/plugins/auditer.rb:92:in `configure'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/sequel-5.15.0/lib/sequel/model/base.rb:550:in `plugin'
  /disk5/www/gb/box/releases/20181224143406/app/models/mailbox/email.rb:4:in `<class:Email>'
  /disk5/www/gb/box/releases/20181224143406/app/models/mailbox/email.rb:3:in `<module:Mailbox>'
  /disk5/www/gb/box/releases/20181224143406/app/models/mailbox/email.rb:2:in `<top (required)>'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/skylight-core-3.1.2/lib/skylight/core/probes.rb:119:in `require'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/skylight-core-3.1.2/lib/skylight/core/probes.rb:119:in `require'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `block in require'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:257:in `load_dependency'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `require'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:378:in `block in require_or_load'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:37:in `block in load_interlock'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies/interlock.rb:14:in `block in loading'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/concurrency/share_lock.rb:151:in `exclusive'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies/interlock.rb:13:in `loading'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:37:in `load_interlock'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:356:in `require_or_load'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:334:in `depend_on'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:246:in `require_dependency'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/engine.rb:478:in `block (2 levels) in eager_load!'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/engine.rb:477:in `each'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/engine.rb:477:in `block in eager_load!'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/engine.rb:475:in `each'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/engine.rb:475:in `eager_load!'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/engine.rb:356:in `eager_load!'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/application/finisher.rb:69:in `each'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/application/finisher.rb:69:in `block in <module:Finisher>'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/initializable.rb:32:in `instance_exec'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/initializable.rb:32:in `run'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/initializable.rb:61:in `block in run_initializers'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:228:in `block in tsort_each'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:431:in `each_strongly_connected_component_from'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:349:in `block in each_strongly_connected_component'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:347:in `each'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:347:in `call'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:347:in `each_strongly_connected_component'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:226:in `tsort_each'
  /home/gencer/.rbenv/versions/2.5.3/lib/ruby/2.5.0/tsort.rb:205:in `tsort_each'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/initializable.rb:60:in `run_initializers'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/railties-5.2.2/lib/rails/application.rb:361:in `initialize!'
  /disk5/www/gb/box/releases/20181224143406/config/environment.rb:6:in `<top (required)>'
  config.ru:4:in `require_relative'
  config.ru:4:in `block in <main>'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/builder.rb:55:in `instance_eval'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/builder.rb:55:in `initialize'
  config.ru:1:in `new'
  config.ru:1:in `<main>'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/unicorn-5.4.1/lib/unicorn.rb:56:in `eval'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/unicorn-5.4.1/lib/unicorn.rb:56:in `block in builder'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:795:in `build_app!'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:139:in `start'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/gems/unicorn-5.4.1/bin/unicorn:126:in `<top (required)>'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/bin/unicorn:23:in `load'
  /disk5/www/gb/box/shared/bundle/ruby/2.5.0/bin/unicorn:23:in `<top (required)>'

Related issues: #74, #75 and #137.

@JonathanTron, two more questions:
I've monkey-patched (ugly) using initializer. Now everything works fine.
But, I still want to hear your idea. Actually, do you still support this gem? I see no improvements on issues for a while except one PR.
Thanks,
Gencer.

Hi @gencer thanks for reporting the issue.

Actually, do you still support this gem? I see no improvements on issues for a while except one PR.

Yes, I support the gem based on my usage. I currently have 3 fairly big Rails apps using it on production. So I fix issues reported when they are bugs, accept PR when they contain things I see I can continue to support in the futur, because I have limited time to work on this.

Not quite correct but commenting/removing this line: https://github.com/TalentBox/sequel-rails/blob/master/lib/sequel_rails/sequel/database/active_support_notification.rb#L21
solves my problem. Simply I tell SequelRails to only log but not raise error.

I will need to investigate further because the ActiveSupport notifier is simply hooking (via ugly monkey-patching) in the Sequel::Database#log_connection_yield (see https://github.com/jeremyevans/sequel/blob/67cc4245227a6c01ecb20d0138aaf37b05a5aebc/lib/sequel/database/logging.rb#L37-L50). So I would expect that the conn given to this method is always the correct one as it is passed down by Sequel itself.
Can you give me more info on how you configure the multiple databases and define the models? A basic rails repo reproducing the issue would be best.

Hi @JonathanTron,
Thanks for replying my issue. I also believe that sample repo will be much more understandable. I will prepare an illustration one and update here as soon as possible. I'm currently on it.
I will try with SQLite, if fails, i will try with PostgreSQL as mine if you're OK with this.
Glad that you are still working (even slightly) on this project.
Thanks,
Gencer.

I will try with SQLite, if fails, i will try with PostgreSQL as mine if you're OK with this.

Either is fine. From the error, it should not matter which database is used.

@JonathanTron, I remember now. It was working on development. However,i when I run my app on production, above errors shows up. I will re-try to reproduce on my end. Sorry for previous comment. (i've deleted it)

Well, well, and well.
I've found the traitor. :=)
It was my own gem that causes this problem. I will fix this on my own gem.
Issue fixed here. no need to do anything on SequelRails-side.
@JonathanTron, Sorry for few emails and making trouble there but at leas I heard news from you and know that project is very much alive.
Gencer.

Glad you were finally able to pinpoint the problem.


Added logging when Zipping Fails

Added reason for zipping fails
'Zipping artifacts failed.' is not enough to determine what when wrong.
When I added this line, I got the error "Please ensure your build artifacts path exists. which immediately Pointed me towards the issue.
Description of changes:
Added console.log to zipping error
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4199   +/-   ##
=======================================
  Coverage   60.67%   60.67%
=======================================
  Files         327      327
  Lines       14368    14368
  Branches     2862     2862
=======================================
  Hits         8718     8718
  Misses       5214     5214
  Partials      436      436

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 8097671...ea41592. Read the comment docs.

@aprowe thanks for the PR, unfortunately console.log is not used in the CLI we have context.print methods to print errors. I am closing this PR as we cannot take as it is, but will look into how could we surface this error in a better way in the future.


Sprite is rendered as a black rectangle on mobile browsers

Hi,
I have an issue where sprite is rendered well on a desktop browser but appears as a black rectangle on mobile browsers. I have tried and checked on possible causes but couldn't come up with a solution. Please do you have an idea of what the issue could be and if possible a solution too.

What's the size of the texture?

The size of the texture is 497 KB

In pixels :)

I left it as autodetectrenderer and the size of the image is 11820 * 501

I dont know limitations of your device, but most mobile devices have limt of 4096 or 8192 on texture size. 11820 doesnt fit.

Also, png size affects only networking. In videomemory that thing costs 118205014 = 23MB, several of them will can clogg your app.

Alright thanks a lot, I'll definitely keep that in mind. I also just tried a texture with a much smaller size and it happened to display well on mobile, so I guess the texture size was the problem after all :)


DingTalk early warning support according to the phone number @ designated person

Describe：
In the nail custom robot through keyword early warning function
On the basis of adding the designated mobile phone number @ designated person and @ owner function implementation
The new configuration parameter is in Alert.properties：
1.dingtalk.isAtAll=true/false
2.dingtalk.mobileList=00000000000,11111111111
中文描述：在钉钉自定义机器人通过关键字预警的基础上增加指定手机号@指定的人及@所有人的功能实现
新增配置的参数在alert.properties
1.dingtalk.isAtAll=true/false 是否@所有人
2.dingtalk.mobileList=00000000000,11111111111 配置@指定人的手机号

hi, can you develop on the plugin_design branch? Currently we are developing Alert-SPI on this branch, and the code of the dev branch will be deleted later.

hi, @liangpingliu , good beginning, good job
as @CalvinKirs said, please submit this PR to branch will be better: https://github.com/apache/incubator-dolphinscheduler/tree/alert_plugin_design
if you have any question, please let me know, thx

hi, @liangpingliu , good beginning, good job
as @CalvinKirs said, please submit this PR to branch will be better: https://github.com/apache/incubator-dolphinscheduler/tree/alert_plugin_design
if you have any question, please let me know, thx

ok  Has been operating on  https://github.com/apache/incubator-dolphinscheduler/tree/alert_plugin_design branch


[flutter_tools] Refactor Flutter SDK to support installation in read-only directory

This would support being installed by root by a package manager. This would require:

Providing an upgrade mechanism that is not dependent on git
Allow the tool to determine its version without calling git commands that may write to .git
Provide Flutter SDK version resolution (e.g. flutter --version) not dependent on git tags
Moving the Flutter cache directory outside of the repo
Tracking the Flutter SDK version file outside the repo (perhaps in the cache?)
Ensuring that pub does not try to write to the repo while doing pub get

This is relevant for nixpkgs too and we have some patches there to move the cache: https://github.com/NixOS/nixpkgs/pull/173200#issuecomment-1146783427
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/flutter/patches/move-cache.patch
Is this a reasonable way to do this?

This is relevant for nixpkgs too and we have some patches there to move the cache: NixOS/nixpkgs#173200 (comment) https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/flutter/patches/move-cache.patch Is this a reasonable way to do this?

@NANASHI0X74 Oh neat! I would say the fact that the path is hard-coded is a bug, we would ideally have some method that can easily be configured, and all other code in the tool calls that method to determine the path to the cache.

Providing an upgrade mechanism that is not dependent on git

What exactly would the upgrade mechanism be? Especially if you're using the distro vendored version of the Dart SDK?

Using the dart pub tool. If your Dart SDK is too old for the newest version of Flutter, then you upgrade it using the same method that used to install it.
Besides the convenience of quickly getting the latest Flutter release, what are the reasons for the existing upgrade mechanism? There must be some right? Otherwise, I don't see why the Flutter team would expend engineering effort to duplicate functionality already provided by the Dart package manager.

Is it because the Flutter engine isn't actually a Dart package?

Using the dart pub tool. If your Dart SDK is too old for the newest version of Flutter, then you upgrade it using the same method that used to install it.

You would always have to update your Dart SDK. Thus, when users want a new version of Flutter, there would be a level of indirection, where they would need to update to the corresponding Dart SDK version that their desired Flutter version depends on, before they can get a valid pub version solve. I think this is counter-intuitive to how users reason about pub.
Also, if you're installing the Dart SDK distributed with your linux distro, you may not have options about which Dart version to install.

Besides the convenience of quickly getting the latest Flutter release, what are the reasons for the existing upgrade mechanism? There must be some right? Otherwise, I don't see why the Flutter team would expend engineering effort to duplicate functionality already provided by the Dart package manager.

The release infrastructure is not really duplicating what pub does. The paradigm for Flutter's release tooling is that the user selects a channel they are interested in (stable, beta, or master). By default (either with a git clone or via pre-built bundle on the website) they will receive the latest version of that release. They can continue to use a particular Flutter version for as long as it still builds, but can also easily upgrade to newer versions of that channel via the flutter upgrade command.
Pub on the other hand, is solving the problem where the user has a set of dependencies and constraints, and it does a version solve for determining the transitive set of all of dependencies and the "best" version that meets all constraints...and then it fetches them. From my understanding, vendoring the Flutter SDK via pub is only leveraging the last part, downloading a remote file, which the user could do with curl.

The release infrastructure is not really duplicating what pub does.

Thanks for pointing this out. I assumed that one could easily subscribe to prereleases of a dart package, but it seems that Dart's version specification is not very complex. It only has like 4 comparison operators and no wildcards, so you can't ask for uuid:4*-beta
I think my whole argument is moot however because the Flutter engine isn't a Dart package and can't be distributed via Dart pub. Only the Flutter tools would be distributable. This wasn't immediately obvious to me because the Engine is its own repo.

Let reconsider the checklist for a hypothetical read-only Flutter/Engine/Dart SDK installed using a system package manager.

Providing an upgrade mechanism that is not dependent on git

The upgrade mechanism for read-only install is getting a new pre-build Flutter SDK from the distro/package manager. Read-only flutter does not update itself; it's read-only.

Allow the tool to determine its version without calling git commands that may write to .git

git describe --tags doesn't write to disk

Provide Flutter SDK version resolution (e.g. flutter --version) not dependent on git tags

Why? As mentioned above git describe is a read-only operation.

Moving the Flutter cache directory outside of the repo

Which cache? The Dart .pub-cache or ./bin/cache? .pub-cache can already be redirected with the PUB_CACHE environment variable.

Tracking the Flutter SDK version file outside the repo (perhaps in the cache?)

For read-only the version doesn't change, so it should be fine to keep inside the repo.

Ensuring that pub does not try to write to the repo while doing pub get

Once again, if we're talking about the Dart .pub-cache we can just move that to a writable user directory using PUB_CACHE. For read-only Flutter all the lockfiles should just be in place for the repo because it's read-only.

Providing an upgrade mechanism that is not dependent on git

The upgrade mechanism for read-only install is getting a new pre-build Flutter SDK from the distro/package manager. Read-only flutter does not update itself; it's read-only.

You have to also consider users who are not on Linux, and may not have a package manager. If we force Windows users to use a package manager like chocolatey, the flutter team has to help maintain that workflow. I know with homebrew on macOS, we have resisted officially endorsing it because they do not provide a way for a team to own a package, and thus ensure that users who type brew install flutter will certainly get a build that was signed on Flutter's CI systems, rather than a malicious copy.

Allow the tool to determine its version without calling git commands that may write to .git

git describe --tags doesn't write to disk

git fetch --tags does. Also, by default, it will sometimes try to either garbage collect or re-compress its data when you run what would appear to be read-only commands. I don't remember what errors off-hand, but at one point I installed flutter with root-only-write permissions and tested it out to create this list.

Provide Flutter SDK version resolution (e.g. flutter --version) not dependent on git tags

Why? As mentioned above git describe is a read-only operation.

Ditto.

Moving the Flutter cache directory outside of the repo

Which cache? The Dart .pub-cache or ./bin/cache? .pub-cache can already be redirected with the PUB_CACHE environment variable.

bin/cache.

Tracking the Flutter SDK version file outside the repo (perhaps in the cache?)

For read-only the version doesn't change, so it should be fine to keep inside the repo.

This is true, but the mechanism for writing this is the tool. This should be an easy fix, though.

Ensuring that pub does not try to write to the repo while doing pub get

Once again, if we're talking about the Dart .pub-cache we can just move that to a writable user directory using PUB_CACHE. For read-only Flutter all the lockfiles should just be in place for the repo because it's read-only.

We always vendor a pre-populated .pub-cache directory with pre-built SDK packages, so that users can immediately start development without network access. On the first run, if the user already has a user-global .pub-cache in their home directory, we will copy it there. See https://github.com/flutter/flutter/issues/53833 for more context. This can be worked around, but it would take some design considerations.

Providing an upgrade mechanism that is not dependent on git

The upgrade mechanism for read-only install is getting a new pre-build Flutter SDK from the distro/package manager. Read-only flutter does not update itself; it's read-only.

You have to also consider users who are not on Linux, and may not have a package manager. If we force Windows users to use a package manager like chocolatey, the flutter team has to help maintain that workflow. I know with homebrew on macOS, we have resisted officially endorsing it because they do not provide a way for a team to own a package, and thus ensure that users who type brew install flutter will certainly get a build that was signed on Flutter's CI systems, rather than a malicious copy.

For clarity, supporting read-only Flutter SDK does not preclude writable Flutter SDK. I agree that you should not force users to use a package manager. We're talking about modifying the SDK, so that it can function as a static system provided toolkit (to be provided by a distro or a system maintainer (person)).

We always vendor a pre-populated .pub-cache directory with pre-built SDK packages, so that users can immediately start development without network access.

This is not true for 3.3.10? The releases are pre-populated, but many of the flutter commands (including build) will fail without internet access (by calling pub get)! Are you referring to features not yet in a stable release?

This is not true for 3.3.10? The releases are pre-populated, but many of the flutter commands (including build) will fail without internet access (by calling pub get)! Are you referring to features not yet in a stable release?

I did not say that ALL commands will work offline (notably if there is some dependency required remotely). Also, I think you need to provide the --offline flag in order for pub get to be invoked without trying to call the network.

Hmmm... My mistake. I thought flutter build automatically calls pub get every time, but that seems to not be the case.
OK. Here's my plan of attack:

[ ] Adjust flutter initialization/doctor scripts so they don't try to re-write ./bin/cache/*.stamp files if they already match the what is cached.
[ ] Do something with ./bin/cache/lockfile handling. So that if it is read-only, Flutter still checks the cache, but doesn't try to edit it. Can someone help with an explanation of what this file is locking?

I think once these are implemented, it should be possible for a Flutter SDK to be initialized, and other non-priviledged users to use it as read-only.

Here's my proposal for working with read-only Flutter:
Modify Flutter so it only updates ./version if it is different.
Add new --read-only option to CLI which hides commands that could update the Flutter SDK cache
Then,

Packager prepopulates the Flutter SDK cache with flutter precache -a
Packager marks the Flutter root as read-only
Package provides an alias flutter = FLUTTER_ALREADY_LOCKED=true flutter --read-only

Assuming the precache step cached all of the things properly, then the user should be able to run flutter without any blocking errors.

I've implemented a prototype of the above comment available on my fork, but I've run into a snag. It seems that if you move PUB_CACHE (or create a new one), the Flutter CLI wants to rebuild the flutter_tools package. However, this involve writing to FLUTTER_ROOT/packages/flutter_tools (the pubspec.lock file is updated). Moving the PUB_CACHE should be expected for read-only installs because each user of the SDK should have their own PUB_CACHE.
I feel like there should be a way to compile these Dart packages once during setup, then reuse the binary instead of recompiling every time the Dart cache moves.

This is the latest NixOS patches that they maintain on the Flutter stable channel to get this working: https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/compilers/flutter/patches/flutter3

Here's my proposal for working with read-only Flutter:
Modify Flutter so it only updates ./version if it is different. Add new --read-only option to CLI which hides commands that could update the Flutter SDK cache

Unfortunately today any Flutter command might hit the cache. I think the better solution would be to allow the cache to be user configurable, and instruct the user to set it to a user-owned path.

Assuming the precache step cached all of the things properly, then the user should be able to run flutter without any blocking errors.

I think there might be other things we write to the cache other than just caching binaries.
Also you have to consider the .git directory.

cc @andrewkolos

Providing an upgrade mechanism that is not dependent on git
Allow the tool to determine its version without calling git commands that may write to .git
Provide Flutter SDK version resolution (e.g. flutter --version) not dependent on git tags

For these things I think rather than hiding them (which may lead to confusion if some installations just straight up don't have some CLI commands for people trying to follow along online resources), each specific distribution should implement its own functionality as to what happens. It can even be as simple as just printing a message to the console.
For example if using a package manager, it'd obviously be preferred that the package manager be used to upgrade flutter , so if someone tries to do flutter upgrade, we can say
Since installed via <package_manager>, use package_manager> upgrade flutter
For flutter --version too we could do something similar, but also might be able to actually implement something that interfaces with the package manager's CLI to find the version
flutter channel I think can just be a print prompting people to install via the official archives, since I think package_managers (atleast brew) doesn't prefer putting multiple distribution channels of a package

Tracking the Flutter SDK version file outside the repo (perhaps in the cache?)

Should be kept track of using the package-manager. If our aim is to introduce a --no-version-check option even without a package manager to override this, then I think it makes sense to have a file in $FLUTTER_ROOT which can have data such as version (or maybe even with package managers we can have such a file, and this file can have info about which channel this flutter was installed through)

Unfortunately today any Flutter command might hit the cache. I think the better solution would be to allow the cache to be user configurable, and instruct the user to set it to a user-owned path.

While the user configurable cache path is a nice additional feature, is that required for making this read only, since if we move bin/cache into .pub_cache, (which according to  #53833 is in the users home directory and thus editable) would that be an issue? Or is the intention to make a version of flutter which doesn't write anything to disk at all (which seems crazy given we wont even be able to add a package)

Ensuring that pub does not try to write to the repo while doing pub get
Again it should be writing to the home directory pub cache

I'm not sure we should do this.
The Flutter SDK is designed specifically to allow people to step through the framework code, adding print and changing the code in other ways, to aid debugging and so forth. The correct way to install Flutter is in a writable user directory, where it can be manipulated via git.
I think it's fine for OS package managers to download Flutter, install it in userspace, and configure the user's path. But I don't think we should make the flutter tool work differently when installed via an OS package manager than when installed directly. That would complicate testing and support in a way that's quite expensive, it would confuse users with documentation that doesn't match what they find works on their machine, it would prevent them from using some of the debugging tools, etc.

I'm not sure we should do this.
The Flutter SDK is designed specifically to allow people to step through the framework code, adding print and changing the code in other ways, to aid debugging and so forth. The correct way to install Flutter is in a writable user directory, where it can be manipulated via git.

This is a good point. In my opinion, the biggest reason we SHOULDN'T do this is developers would essentially be "stuck" using the version of the Flutter SDK that their package manager is packaging, unless for example Debian decided to package every stable Flutter as a different package. Even then, if there were a critical bug that was fixed in beta but not stable, they would have to go and clone flutter anyway.

This is a good point. In my opinion, the biggest reason we SHOULDN'T do this is developers would essentially be "stuck" using the version of the Flutter SDK that their package manager is packaging, unless for example Debian decided to package every stable Flutter as a different package. Even then, if there were a critical bug that was fixed in beta but not stable, they would have to go and clone flutter anyway.

While this is problematic for most package managers, Nix (and to an extent, Arch Linux's pacman) make it quite easy to rebuild a package with forked source code or additional patches applied.
This is part of the reason we'd like Flutter to work better with package managers - you get all the powerful features of the package manager. Nix, for example, would let you apply different custom patches to Flutter per-project, which is a lot nicer than managing a clone manually.

rebuild a package
Since flutter doesn't really build from code as such, and just uses that dart code directly how exactly does this system work?

the biggest reason we SHOULDN'T do this is developers would essentially be "stuck" using the version of the Flutter SDK [initially installed].

In a classroom setting I would be happy to live with this limitation for the length of a term.

The Flutter SDK is designed specifically to allow people to step through the framework code, adding print and changing the code in other ways, to aid debugging and so forth. The correct way to install Flutter is in a writable user directory, where it can be manipulated via git.

Flutter installed through a package manager does not necessarily have to be read only - temporary changes for debugging can be made, so long as users don't expect them to persist with upgrades. We'd like the Flutter tooling itself to avoid modifying its own installation directory as much as possible to make upgrades from a package manager easier.

Maybe what we should do is provide tooling that package managers can ship as "flutter" that is actually just a shell script that downloads flutter to the user's home directory. That way Flutter keeps working as designed, but you can obtain it via the package manager UI. Basically a /bin/flutter that does something like:

if $HOME/flutter does not exist, git clone flutter to $HOME/flutter.
Defer to $HOME/flutter/bin/flutter.


jesse: fix handling of -0.0 for OTP-26.1/27.0

Matching of floating-point zeroes will change in OTP-27 so that -0.0 will no longer match a non-negative 0.0. OTP-26.1 warns about such constructs, which in jesse results in:
===> Compiling src/jesse_validator_draft3.erl failed src/jesse_validator_draft3.erl:865:5: matching on the float 0.0 will no longer also match -0.0 in OTP 27. If you specifically intend to match 0.0 alone, write +0.0 instead.
===> Compiling src/jesse_validator_draft4.erl failed src/jesse_validator_draft4.erl:1019:5: matching on the float 0.0 will no longer also match -0.0 in OTP 27. If you specifically intend to match 0.0 alone, write +0.0 instead.
===> Compiling src/jesse_validator_draft6.erl failed src/jesse_validator_draft6.erl:997:5: matching on the float 0.0 will no longer also match -0.0 in OTP 27. If you specifically intend to match 0.0 alone, write +0.0 instead.
Fixed by switching from matches to numerical comparisons.

Dupe of #128 ?

Dupe of #128 ?

Yes

I merged #128, so closing this one.


Instance: Eduardo Rossener

Cloud Computing Instance Flavor
g3.xl - GPU instance (32 CPUs, 125 GB RAM and A100 GPU)
Description
I am a Master's student from University of São Paulo and I am taking the SlicerMorph course
ORCID
0009-0000-3358-7213
Email
U2FsdGVkX18//nHQqWQIx/ThyrMKjsK9brXcVq5A7GRcU5j+RkLb+bhbvE9Wk0i4
Confirm Email
U2FsdGVkX18//nHQqWQIx/ThyrMKjsK9brXcVq5A7GRcU5j+RkLb+bhbvE9Wk0i4
Instance Name
instance-137
The instance name is derived from the GitHub issue number using the template instance-NNN. The instance may also be located in the exosphere interface using this name.
Volume Name
My-Data-137
The volume name is derived from the GitHub issue number using the template My-Data-NNN. The volume may also be located in the exosphere interface using this name.

/create


Hapistrano can't deploy from Windows

Expected Behavior
I want to deploy from Windows to a UNIX system using the same files I would use if I ran hapistrano from Linux.
Actual Behavior
I'm getting this error when deploying from Windows.
> hap deploy -c deploy/staging.yaml…Aeson exception:…Error in $['deploy_path']: InvalidAbsDir "/var/www/staging"…

Other details
Hapistrano uses the path library. path has support for windows. However, path makes a distinction to expose certain behavior according to the system it is being compiled on:
{-# LANGUAGE CPP #-}
#if defined(mingw32_HOST_OS)
module Path(module Path.Windows) where
import Path.Windows
#else
module Path(module Path.Posix) where
import Path.Posix
#endif

That means that if hapistrano is compiled on Windows, it will validate that all paths on the server.yml files have valid deployment paths. If the target is Unix, the path will still appear as invalid since path's validation relies on the system it was compiled on.

I'm going to close this issue for now since it was labeled as wontfix. We can reopen it in the feature since no one else has requested to take a look at it.


artist section in eigen (iphone) is linking to the wrong place

correct order:
https://m.artsy.net/artists  to https://m.artsy.net/gene/emerging-art
right now we go to native gene pages which are not organized by artist and therefore are confusing to arrive at. We should instead link to the microgravity view instead

correct order:
https://m.artsy.net/artists  to https://m.artsy.net/gene/emerging-art
right now we go to native gene pages which are not organized by artist and therefore are confusing to arrive at. We should instead link to the microgravity view instead

@katarinabatina This is only easily and fast done if we decide that there’s no place that should link directly to the overview of a gene, because then we can decide to not route that URL, but if there are places where such a URL should route then it’s going to get hard.
I don’t know from the top of my head if there are any other places. Seeing as our ‘all genes’ overview is native as well, it won’t be a problem there.

@alloy As in, from the category pages?

@alloy As in, from the category pages?

Yeah, because our category pages are native, it won’t be a problem there if we’d re-route the https://artsy.net/gene/NAME URLs. So I think re-routing will be fine.

yeah I think desired end result would be to only have this affect coming through the artist section if possible and leave the category entry points as is

The alternative is to ask Force/Martsy to show these ‘artists by gene’ under /gene/:name/artists so that when we do ever need to route to just our native gene view it can be done with /gene/:name.
@craigspaeth Does that sound feasible to you?

Filed a Martsy ticket https://github.com/artsy/microgravity/issues/960

Filed a Force ticket https://github.com/artsy/force/issues/3209

This is fixed in Martsy, just needs deploying.

Gonna move to the next sprint to keep an eye on, but at least we’ll be able to close this milestone.

@anipetrov Assigning this to you to keep an eye on, as it is a cross-team dependency.

This should all be fixed upstream by now.


Audio Engine V2

Same as IndexedDB, we need to modernize and solidify our WebAudio support
The Audio Engine is due for a refresh.

[ ] Tech investigation, in particular:
Clean code
Add support for async / promises
Allow the user to control the graph
[ ] [More milestones to be defined with tech investigation]

Design Goals

[ ] Competitive analysis

Compare audio capabilities from other industry solutions (Unity, Unreal, Playcanvas)
Revisit Audio Editor design from FHL (Jason Syltebo)
Create user flows for audio use in Babylon

[ ] User Interface

Determine where UI of audio lives (inspector only, VSM, new interface)
Determine what new components may be needed for UI beyond shared components
Design for UI as needed

This should include #11590.
Closing the other issue.

Hi,
I was wondering, if I can suggest an idea for the Audio engine v2, to add the possibility of recording live sound spatialized when speaking into a microphone.
Basically, I would like to create a voice chat with spatial sound. But currently the engine just allows you to play audio files, not to save them.
Hope you find this might be a good idea.
Here is an example of a chat with spatial sounds in video of what I would like to achieve with the new generation Audio engine (which Babylon should absolutely have) It would be great to have this for Babylon in a way to be able to create games like MMO, Metaverse...
https://f.hubspotusercontent40.net/hubfs/5066246/2021 Website/Videos/SpatialAudioDemo-Spatialized.mp4

Hi,
I was wondering where the progress of the audio engine V2 was ?
If there was any idea of when this might be available/planned ?
Thanks

Hi,
I was wondering where the progress of the audio engine V2 was ? If there was any idea of when this might be available/planned ?
Thanks

We're hoping to have the Audio Engine V2 core ready for the next major release, Spring 2024.

OK thank you for the information.

Hi,
I was wondering where the progress of the audio engine V2 was ? If there was any idea of when this might be available/planned ?
Thanks

We're hoping to have the Audio Engine V2 core ready for the next major release, Spring 2024.

This is great news!  Will there be a PR for this soon to test drive?

This update will probably not be included in 7.0, but I will wait for @docEdub to be sure.

I proposed this for my part for the V2 of the Audio engine ;
https://github.com/BabylonJS/Babylon.js/issues/12576#issuecomment-1212470389
This new audio engine has been moved several times. Will it be for version 8 or is it abandoned?

Will it be for version 8 or is it abandoned?

It is not abandoned. I am hoping to spend more time on it after the 7.0 release.

@docEdub Do you want to keep this issue?

@docEdub Do you want to keep this issue?

Closing this for now. I will reopen or make a new ticket when work starts on the new audio engine.


[master] Bump Mesos to nightly master 6a98857

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/9127c792c5a20aee2f31a2e56854c2490a9ca608...6a98857cf429580b72cd97ddd749a074c3e4524d
https://github.com/dcos/dcos-mesos-modules/compare/26d11daee118055ab0975b0eaa0a25b6cf1a35c3...29561f11a12372752b77839be73418d1d75abe63

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee


Added tests for step 4.

Coverage increased (+6.9%) to 43.678% when pulling 424e931b0ae81540260c2211671bff07da97a517 on JakeBrown:pycon2016 into a5390a50b6e8ab83c47c6c64c379c4daf10aa4dc on keeppythonweird:master.


Gatsbyconf banner

This PR adds a banner for gatsby conf

closing at it include related-pages.json


Change application.scss to application.scss.liquid

Creating a new theme recently, I found that the default application.scss file wasn't compiling, leaving me with a 404 error for what should have been the theme CSS file.
Some searching led to this post and on to this blog post that suggested the scss file needed a missing .liquid extension.
I changed the file to application.scss.liquid and it worked!
This PR proposes changing the file to be application.scss.liquid by default, and adds comments to flag that SASS gets compiled on deploy, and that @import isn't supported.

What's the difference between ?


is this still being work on?

hey @nharris85
thank you for putting this together.
I noticed on your last commit stating the test are still failing.
Do you need help to resolve those issues and if you are still working on this?

hey @M1chaelTran
This has definitely fallen off my radar. My project moved on to a different DB before I could finish this. I have other projects that I expect will use DynamoDB but haven't had the time to circle back around to this.
I welcome any help you want to offer. I think it was really close to being done.

@nikordaris @M1chaelTran I'm on a project now looking into which backend we're going to use with node_acl. I think we're going to try to use this dynamodb backend, so I've taken a quick stab at getting the tests to work. I have a fork where I have the tests all passing, but I've made some changes I thought I should run by you if you want to keep this project going:

I just removed the encodeURIComponent and decodeURIComponent as it was causing the tests for user<EMAIL_ADDRESS>to fail. I don't know if these need to be re-instated in order to resolve some other issue I'm not aware of. I haven't yet dug into why those tests fail with this encoding logic in place. I can do that if you think it is needed.
Not needed to fix the tests, but when useSingle = false I am currently still forcing all the acl_allows* records to use a single allows table, rather than 1 per resource. This is because on my project we will have probably hundreds of resources defined and will hit the dynamo limit (we could request a limit increase but I'd like to keep the tables a little cleaner). I've seen other node_acl backends do something similar. I'm considering making this behavior another option... but haven't thought through how to make it clear.

For the other tests basically all I had to do to get them to pass were some minor tweaks:

force all keys/values to a String, to fix the tests where userId was numeric
make "remove()" use ExpressionAttributeNames, otherwise executing a remove on a "get" permission caused a problem due to "get" being a reserved word.
change the "prefix" in the default/single tests to use a different prefix, since otherwise the table acl_resources needs a different structure (range key on bucketname) for the "single" vs default, and so queries were failing.
strip out invalid chars in the table names... before I changed the "allows_*" to all be in a single table this was needed because resources like "/path/file/file2.txt" are invalid table names.
add "_bucketname" to the lodash.without() list... otherwise the isSingle=true tests fail for having this extra data in the output

You can see the diff at https://github.com/nikordaris/node_acl_dynamodb/compare/master...matthoward:fix-tests?expand=1
I don't think it's ready to merge yet - want to clean up some things first (and I used some es6 syntax I might need to redo unless you mind bumping the node engine compatibility). But if you want me to merge the fixes let me know your thoughts on the above... especially the URI encoding and the single allows_ table logic.

@matthoward great work! Please do submit a pull request when you are ready. Bumping the node engine up is a welcomed improvement.


whereis doesn't support flags or arguments anymore.

Platform: macOS 10.15.7
From man whereis:
COMPATIBILITY
     The historic flags and arguments for the whereis utility are no longer available in this version.

Is this about the content of a page? In this case, please direct your issue towards tldr-pages/tldr. Otherwise, please describe your problem in more detail :)

I'll close this for now, but you can still leave a comment if this is about teldeer!


super-tab margins

hey what is the variable of total length to slide for each tab and can that be modified to include margin offsets? i want to have a sorta no mans land in between pages for visual effect.
in this image the lime green is the margins between pages the fist page is fine but the offset is compounded with each page swiped left

So you have margins between the super-tab elements, so when the user swipes between the tabs there's spacing between the tabs?
If so, this isn't something we wish to support as it's not a common UX pattern and it doesn't follow the material design specs. Feel free to fork the repo & modify the code for your needs.

Hi, using CSS padding on slide content (maybe ion-slide) should do the trick!

@ihadeed well thanks for the reply, but i have no clue where to start with creating or changing plugins and how to implement them. thanks for the help though.

@aleygues can i have the pages keep the View life cycles with ion-slide ?


Information missing in codelab

An information is missing in this codelab: https://openthread.io/codelabs/openthread-hardware#4
It is not indicated that you should use the "nRF USB port". If you don't, you don't get the prompt when you call the screen command.

@OLmmyT , the codelab currently uses the UART_trans flag in the build command. When using UART_trans, then the instructions are as stated in the codelab:
Attach the USB cable to the Micro-USB port next to the external power pin on the nRF52840 board

The nRF USB port only applies when using the USB_trans flag.

Ok thank you Jonathan.
I have USB_trans flag because I'm following another codelab (https://openthread.io/codelabs/openthread-border-router#3) which says to follow the instructions on this page (https://openthread.io/codelabs/openthread-hardware#4).

Follow step 5 of this codelab to build and flash a nRF52840 CLI end device. But instead of having OT_COMMISSIONER and OT_JOINER enabled, the CLI node requires OT_SRP_CLIENT and OT_ECDSA features:
$ script/build nrf52840 USB_trans -DOT_SRP_CLIENT=ON -DOT_ECDSA=ON

@jwhui https://openthread.io/codelabs/openthread-hardware uses both USB_trans and UART_trans in different steps, should we change to always use UART_trans.

@jwhui https://openthread.io/codelabs/openthread-hardware uses both USB_trans and UART_trans in different steps, should we change to always use UART_trans?

I agree.

@OLmmyT , thanks for raising this issue. I submitted a proposed change in #36 .


Remove settings tabs closes #72

Coverage remained the same at 100.0% when pulling 46de1982dd7cbd492dc2c6bac18aa9670970d606 on remove-settings-tabs-#72 into f037eba862ae3a520e15fd9ecf1674376064799d on develop.


Rendered page shows warning for parameters resulting in no models being displayed in the page

Hi team,
Issue:
Upon rendering of the YAML Petstore 3.0,  the page displays warnings with text such as - No "type" specified at "/paths/~1pets~1{id}/get/parameters/0". Automatically detected: "object".
This results in page not showing definition of request or response models.
This issue was first observer 4-5 days back.
Thank you

OMG, I accidentally deployed 1.x version demo instead of the latest one as a result of a recent CI build of 1.x.
Deployed a new alpha.39 and new demo will be deployed once CI finishes (in 5-10 mins from now)
Thanks for reporting!

Thanks!
Appreciate the great work with redoc.


1648 printermanager.go:234] Failed to share printer

Hi,
I'm kindly requesting help with a problem. I have a Linux server running CUPs for my print server. It is loading fine to Google Cloud Print. I can then share my printers with now problem. However, if I reboot the server and start the cloud service again I get this error: 1648 printermanager.go:234] Failed to share printer ResourceCenter_HP_Color_LaserJet_CP3525: https://www.google.com/cloudprint/share call failed: Failed to share the printer - and all my old printers are gray (offline) on google cloud print.  Pretty much, It creates new copies of the printers and none of the sharing I did remains.
Any help will be highly appreciated.
Regards,
-Chris

I don't have any guesses so far. Please send the log file from before reboot, when the printer is registered successfully, an the subsequent log file from after reboot, when sharing fails.
After that, please describe what happens when you disable sharing.

Thank you for your reply Jacob. Is it the /tmp/connector.INFO? thanks again!
Regards,
-Chris

Yes. That's actually a link, but you can easily make a copy before reboot, then another copy after the failure.

yes yes, just wanted to make sure I was aiming to the right file. I will reproduce the issue and collect the logs for and post them. Thank you for the follow up Jacob!.

Hi, any progress here?

Hi, thank you for following up. We have had a very busy week and could not collect the logs yet but I will have them tomorrow. Thank you again. Regards,
-Chris

Hi Jacob,
I sent the logs to your email. Thank you!

How many times have you initialized a config file with your Google account?
I think automatic sharing might have something to do with this problem. The OAuth token is different for sharing; the rest of the Cloud Print API calls use a "robot" account token, while sharing uses the user's own account.

Hello,
I also have this problem with my Raspberry Pi 2 running the CUPS connector on Raspbian. Every time a reboot happens the printers registered on the connector are added to GCP again and I have to share them again too.
Expected behaviour would be that the printers would be marked offline on GCP when the server is powered down, and online when the server is up again.
It's a recurring and annoying problem and I'm happy to provide logs as soon as I can if needed.


2.4.0 release?

Is there any plan or schedule for jwm 2.4.0 release?
It would be great especially for package systems that require official release tar balls.
Thanks,

@FrostKnight do you have any tips on compiling 2.4? For 2.3.7 I'm able to download the source package from the website and compile that just fine, but when I try to compile the current state of this repository I've been running into issues. I'm compiling on CentOS7, per the steps in the readme:
[root@f8d877b67cb7 jwm]# ./autogen.sh
configure.ac: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal)
automake: error: no 'Makefile.am' found for any configure output
autopoint: *** The AM_GNU_GETTEXT_VERSION declaration in your configure.ac
               file requires the infrastructure from gettext-0.20 but this version
               is older. Please upgrade to gettext-0.20 or newer.
autopoint: *** Stop.
autoreconf: autopoint failed with exit status: 1

I'm not sure wha tthe AM_INIT_AUTOMAKE issue is about, but the gettext version also seems odd -- I've tried compiling on Ubuntu distributions as well but not even Ubunutu seems to package a version of gettext newer than 0.19.

 I am going to refresh myself so I can give you further info.

Change configure.ac, that is where you need to make the gettext depend on 0.19,
MY OS has the same issue... ;)
Its working on transitioning to a huge massive update, thus I have the same problem.
once thats changed, ./autogen.sh
./configure or in my case configure prefix=/usr which you dont need to do, :)
make
then doas make install
that should be it.

well in my case its doas for you it would be sudo heh.

Thank you @FrostKnight! I was not expecting to be able to just change the dependency version like that, but changing to 0.19 does allow to complete compilation (as long as gettext-devel is installed.

@neandrake I did something similar to get dosbox-x working without a new enough ffmpeg version. :P
And other software too... :)
My point? Sometimes being willing to try insane shortcuts works! :)
For software anyways... never try this for hardware like stuff though... like a friggin bios. :P
Anywho, glad it helped you! Keep this in mind for other types of software, it might help a lot!

Finally pulled the trigger on this one!