Adding process tracing

This PR implements #159
Continuing the discussion from that issue:

Should we not show the bars if the process already exists or should we show the bar from beginning to end?

At the moment I have the bar starting when a process is spawned and stopped when it exits (both of which have to be present during the trace in order for the bar to appear). In other words, it doesn't look like Mermaid renders anything unless there is both an actor activate and deactivate. That and it doesn't look like we can start bars at arbitrary points on the sequence. Rather it looks like they have to start and stop on events. All this to say, I think if we want to keep the bars, they'll only be present when a process starts and stops during the trace.

Regarding the messages, can we do any sort of mouse over thing? Keep only the label and when you mouse over, you see the whole message?

I'll have to explore this a bit more. I tried setting up a pop up Actor Menu as described in the docs...but the menu never popped up lol.

There are some dotted arrows after the messages... is this the "receive" event? If so, I think we can ignore it. Another option would be for the arrows to not be horizontal, but point to when the messages are received in the other process timeline, but that may be too complicated?

I think the Mermaid diagrams only allow for horizontal lines and cannot be linked back to another event. Do you want me to remove all receive events and just have send events? Or only in certain circumstances? Here is an example with no receives for reference:

We also need to check if we trace :DOWN messages from Process.monitor.

It has been done! I also added that to the example code :).
I have a couple more things that I need to clean up and fix so I am opening this up as a draft PR. Should have those wrapped up during the weekend :). Thanks in advance for the review and have a great weekend!

@jonatanklosko the current implementation discards the result of the function given to trace and I don't like that. We could instead return {res, kino_markdown}, but then the result of course won't be printed. So here is my suggestion:

Have this function return both {res, kino_markdown}
Also add Kino.Process.render_trace, that calls trace/2, renders the trace behind the scenes, and returns only res

WDYT?

Thanks for the review @josevalim! Really appreciate it. I reworked the exception handling a little so that the call to the tracer GenServer was not part of the trace capture. I also need to rework that last reduce to handle the scenario when a process is started prior to the trace, but terminated during the trace. Mermaid throws an error if you attempt to deactivate an actor without it being activated prior.
After that I think it is good to go :). Thanks!

You can also do nested trys. The nesting is uglier but less code duplication and perhaps easier to understand?
try do
  try do
    fun.()
  after
    stop_trace
  end

  get_trace_events
after
  GenServer.stop
end

You can also do nested trys. The nesting is uglier but less code duplication and perhaps easier to understand?
try do
  try do
    fun.()
  after
    stop_trace
  end

  get_trace_events
after
  GenServer.stop
end

It has been done :)

I fixed that last issue that was on my TODO list and switched the PR from draft to ready. Let me know if there are any other issues I should address.
I think the only open question at the moment is whether the result is kept from the trace function?

I will let you know soon. I also just realized that we could name the current process as self() in the diagram. WDYT?

I will let you know soon. I also just realized that we could name the current process as self() in the diagram. WDYT?

Sounds good :). I updated how the participating PIDs are generated and the calling PID now show up as self(). I think that makes it nice and clear for users following the trace.

Hi @akoutmos, let's please change this one to return {res, kino}. Then we will add render_app_tree, render_sup_tree and render_seq_trace that render as a side-effect. The first two will return Kino.nothing, the last one will return the result of the function. WDYT? Can you please push those final changes? :)

@akoutmos fantastic!!

Thanks @jonatanklosko!

Hi @akoutmos, let's please change this one to return {res, kino}. Then we will add render_app_tree, render_sup_tree and render_seq_trace that render as a side-effect. The first two will return Kino.nothing, the last one will return the result of the function. WDYT? Can you please push those final changes? :)

That sounds good to me :). I think I implemented it as you described in 9a5b965. Let me know what you think!

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:

Thanks for the review @josevalim and @jonatanklosko! Happy to see this merged in :)


Warning: unable to stat srcFile (common) Use --force to continue

Is something wrong with this config?:
   compress: {
            dist: {
                options: {
                    archive: 'my.zip',
                    mode:    'zip'
                },
                cwd:     '../build',
                src:     ['**'],
                dest:    '../'
            }
        },

Because I get: Warning: unable to stat srcFile (common) Use --force to continue.

I was having a similar issue, it looks like you need to add expand: true to your configuration based on grunt docs.

I was experiencing this as well, but as @benhutchins said, expand: true did the trick.

Adding expand: true also resolved the warning for me too.


Add Bintray credentials to .travis.yml

BINTRAY_SNOWPLOW_MAVEN_USER
BINTRAY_SNOWPLOW_MAVEN_API_KEY

[x] AD: add creds
[x] AD: create repo in Bintray
[ ] ER: push first M1
[ ] AD: add to JCenter
[ ] AD: activate Maven Central sync

There's a dodgy commit to fixup.

Repo created, https://bintray.com/snowplow/snowplow-maven/scala-referer-parser
I've renamed this repo too given we are getting rid of Java.

@ me when you are ready for the remaining steps.


Terrain Uber Shader

This PR replaces the TerrainShader with TerrainUberShader. I have left the code for the legacy TerrainShader in tact for now but deprecated it. The new terrain shader eliminates branching as much as possible and falls more in line with libGDX shader architecture.
There should be no visual change in terrains with this PR. The reason for switching to an uber shader is performance, as the current approach would not scale well when more terrain features are implemented.

PR merge was delayed due to a hard to track down bug that only happened some times. Ended up being blending enabled on the context, Fixed by disabling blending on terrain shader.


Python file changes are not seen in notebooks

Have two notebooks with different kernel paths.
Have them both import the same python file
Change the python file to force an error in the imports.
Expected result:
Both notebooks show the error.
Actual result:
Only one of them does.

In stable, neither of them does, so this isn't really any worse than what we had already.


ssl verify failed on Windows

My previous issue was resolved with the following commits and version 1.1.1. Thank you for that.
However, there is more. Now that the .bib file is opened properly, SSL Certificate problems arise.
The log looks like this:
==== Reading files =============================================================
Reading file 1 / 1 from 'References.bib'
Read 62 entries from 1 file

==== Completing entries ========================================================
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[unpaywall] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[crossref] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[unpaywall] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[crossref] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[unpaywall] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[researchr] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
[crossref] WARNING: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)

Again, this happens only on Windows (Python 3.9).
Modifying the HTTPSConnection in https.py to
connection = HTTPSConnection(domain, timeout=self.connection_timeout, context = ssl._create_unverified_context())
fixes this, as described in this stackexchange post.

I'm not a big fan of bypassing SSL verification, especially given those websites should all have valid certificates.
From what I've found online the certifi package provides Mozilla's root certificates, can you try running pip install --upgrade certifi and then running the script again ?
If that fixes the issue I'l make a prettier error message mentionning this solution and add it as a recommended dependency to the README. Otherwise I can add SSL bypass when on Windows

I pushed a fix in version 1.1.2.
In the end I added a new CLI flag -S or --ignore-ssl that uses ssl._create_unverified_context(), but the default behavior is still to use a verified context. I also edited the error message to mention you can either use this flag or update your certificates with pip install --update certifi.


Future-proof against potential Prelude.foldl'

See https://github.com/haskell/core-libraries-committee/issues/167
This is, of course, a bit speculative at the moment, but given that the change does not involve CPP, it should not hurt to merge it early to simplify further impact assessment.

@sjakobi @treeowl could someone please trigger CI jobs?

Yes, sorry.

@treeowl thanks, CI is green. Does the patch look reasonable?

Yes, I think so.

@treeowl could you possibly make a release with this patch please? It would allow to build with GHC HEAD.

Yes, I should be able to do that today.

@treeowl just a gentle reminder.

Oof... Time got away from me. I'll get to it shortly.
On Wed, Jan 3, 2024, 4:22 PM ˌbodʲɪˈɡrʲim @.***> wrote:

@treeowl https://github.com/treeowl just a gentle reminder.
—
Reply to this email directly, view it on GitHub
https://github.com/haskell-unordered-containers/unordered-containers/pull/480#issuecomment-1875989323,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOOF7M46X7PWPOGBVD47UTYMXDZRAVCNFSM6AAAAAAY2BO2ZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVHE4DSMZSGM
.
You are receiving this because you were mentioned.Message ID:
<haskell-unordered-containers/unordered-containers/pull/480/c1875989323@
github.com>

@Bodigrim, I'm sorry that took so long. It's all on Hackage now.

Thanks a lot @treeowl!


[Bug]: "On trying to commit for one of the app connected to a private repo, the app remains in loading state.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Observation is made when more than 3 private repo apps are present and the instance is downgraded to CE. Post downgrade the commit action is being performed for one of the apps.
Tested on DP: https://ee-2453.dp.appsmith.com/
Steps To Reproduce

On a paid version, create 4 diff apps and connect each one to a private git repo
Downgarde the instance to CE by removing the key
Open one of the app and make changes
Click on "Commit" icon
Click on "Commit and push"

observe that it remains in the loading state.
Public Sample App
No response
Environment
Deploy Preview
Issue video log
No response
Version
Appsmith Business v1.9.40

Stale


how can I attach image in notification in IOS app

I created a react native app for IOS and sending notification successfully through react native fcm.
But now I want to send image as well. Can someone guide me how to achieve this?

@evollu @benoist @moriyoshi @ibratoev @radev @zaro Someone guide me?

image in iOS notification? is it possible in native iOS?

dup of https://github.com/evollu/react-native-fcm/issues/719#issuecomment-395956329
closing this

@kartavyaparekh96 it works for me https://www.pluralsight.com/guides/creating-ios-rich-push-notifications. Good luck!

@engin145 that's helpful! Does this work after user force kill the app?

It is done in React-native-onesignal

@kartavyaparekh96 cool. is it possible for you to port it over?


[HUDI-1522] Add a new pipeline for Flink writer

What is the purpose of the pull request
This is the #step 1 of RFC-24:
https://cwiki.apache.org/confluence/display/HUDI/RFC+-+24%3A+Hoodie+Flink+Writer+Proposal
in order to add a new pipeline to avoid the single parallelism operators.
Brief change log

The new pipeline removes the InstantGenerateOperator and CommitSink, add
StreamWriteOperatorCoordinator to achieve the same function
Add HoodieOptions for configuration of all the Flink operators, this
is also useful for the SQL connectors which would be introduced in
following contributions
Add UT and IT cases for the new operators

Verify this pull request

StreamWriteFunctionTest to test the StreamWriteFunction and the related components
StreamWriteITCase is a IT to test all the operators

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2430 (7961488) into master (7ce3ac7) will decrease coverage by 41.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #2430       +/-   ##
============================================
- Coverage     50.76%   9.68%   -41.09%
+ Complexity     3063      48     -3015
============================================
  Files           419      53      -366
  Lines         18777    1930    -16847
  Branches       1918     230     -1688
============================================
- Hits           9533     187     -9346
+ Misses         8468    1730     -6738
+ Partials        776      13      -763

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudiflink
?
?

hudihadoopmr
?
?

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
9.68% <ø> (-59.75%)
0.00 <ø> (ø)

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

The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #2430       +/-   ##
============================================
- Coverage     50.76%   9.68%   -41.09%
+ Complexity     3063      48     -3015
============================================
  Files           419      53      -366
  Lines         18777    1930    -16847
  Branches       1918     230     -1688
============================================
- Hits           9533     187     -9346
+ Misses         8468    1730     -6738
+ Partials        776      13      -763

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudiflink
?
?

hudihadoopmr
?
?

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
9.68% <ø> (-59.75%)
0.00 <ø> (ø)

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

Thanks @garyli1019 @yanghua for the review, i have updated based on your comments.

@danny0405 sorry for the delay on review, I was super busy this week. The bloom index was merged to master, can we add the bloom index option to this PR as well?

@danny0405 sorry for the delay on review, I was super busy this week. The bloom index was merged to master, can we add the bloom index option to this PR as well?

@danny0405 sorry for the delay on review, I was super busy this week. The bloom index was merged to master, can we add the bloom index option to this PR as well?

I'm not planning to using the BloomFilter index in the new pipeline, instead there is a BloomFilter index backed state index in the following PR, which is more suitable for streaming write.

@danny0405 sorry for the delay on review, I was super busy this week. The bloom index was merged to master, can we add the bloom index option to this PR as well?

I'm not planning to using the BloomFilter index in the new pipeline, instead there is a BloomFilter index backed state index in the following PR, which is more suitable for streaming write.

@danny0405 oh, CI failed... Please fix it before merging, 3ks.

@danny0405 oh, CI failed... Please fix it before merging, 3ks.

@danny0405 sorry for the delay on review, I was super busy this week. The bloom index was merged to master, can we add the bloom index option to this PR as well?

I'm not planning to using the BloomFilter index in the new pipeline, instead there is a BloomFilter index backed state index in the following PR, which is more suitable for streaming write.

@danny0405 yes, using bloom index in a streaming fashion is what we are planning to do next as well. No worry for now, we can try this PR out and continue the work on top of this. Really appreciate your work! This PR LGTM.

@danny0405 sorry for the delay on review, I was super busy this week. The bloom index was merged to master, can we add the bloom index option to this PR as well?

I'm not planning to using the BloomFilter index in the new pipeline, instead there is a BloomFilter index backed state index in the following PR, which is more suitable for streaming write.

@danny0405 yes, using bloom index in a streaming fashion is what we are planning to do next as well. No worry for now, we can try this PR out and continue the work on top of this. Really appreciate your work! This PR LGTM.


Update button in Calculations

Havent really found what is causing it but sometimes i have to refresh in order to use the Update button for route calculations again as it stays purpled out.

@TurtIeSocks did something change over the last month ? just tried to reproduce it but im unable at this point.

I'm not sure, but I'll go ahead and close for now. If it happens again feel free to reopen.


fix syntax error introduced by #246

Obvious fix so merging straight away.  Just created the PR so people don't complain I'm pushing changes secretly ;-)


启动报错

已经在main里面引入 并且安装了包
import formCreate from '@form-create/element-ui'
import FcDesigner from '@form-create/designer'
app.use(formCreate)
app.use(FcDesigner)
[ERROR] Could not resolve "element-plus"
node_modules/.pnpm/@form-create+designer@3.2.2_vue@3.4.30/node_modules/@form-create/designer/dist/index.es.js:12:32:
  12 │ import { ElMessage as Sh } from "element-plus";
     ╵                                 ~~~~~~~~~~~~~~

You can mark the path "element-plus" as external to exclude it from the bundle, which will remove
this error and leave the unresolved path in the bundle.
/Users/akiraka/Documents/QuarkArcoPro/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:1472
let error = new Error(text);
^
Error: Build failed with 1 error:
node_modules/.pnpm/@form-create+designer@3.2.2_vue@3.4.30/node_modules/@form-create/designer/dist/index.es.js:12:32: ERROR: Could not resolve "element-plus"

form-create/designer/package 项目中 "element-plus": "^2.0.1", 不会安装上，这个是不是有问题


updated user messages & UI with correct spelling

not sure if branch is updated with latest commits from Releases/Official-Release


Allow RequestConfig and HttpClientContext to be injected

This allows the RequestConfig and HttpClientContext instances to be overridden.
It is done like so:
(client/request {:method :get
                 :url "http://localhost:18080/get"
                 :http-client-context my-http-client-context
                 :http-request-config my-request-config})

We thinks this allows for more flexibility. In our case, it helps us do some fancier things with proxies. We want to set an AuthCache on our HttpClientContext instance, which looks something like this:
;; Our code looks like this...
(defn additional-cljhttp-options [proxy-host proxy-port proxy-user proxy-pass]
  (let [host (HttpHost. proxy-host proxy-port "http")
        creds (doto (BasicCredentialsProvider.)
                (.setCredentials AuthScope/ANY (UsernamePasswordCredentials. proxy-user proxy-pass)))
        basic-scheme (doto (BasicScheme.)
                       (.processChallenge (BasicHeader. HttpHeaders/PROXY_AUTHENTICATE "Basic")))
        auth-cache (doto (BasicAuthCache.)
                     (.put host basic-scheme))
        context (doto (HttpClientContext/create)
                  (.setCredentialsProvider creds)
                  (.setAuthCache auth-cache))
        request-config (-> (RequestConfig/custom) (.setProxy host) (.build))]
    {:http-client-context context :http-request-config request-config}))

This seems like it would also help solve #307 and allow SOCKS authentication to be provided, and perhaps help with #225.
Feedback is welcome, especially on some of the naming and spying done in the new test.

This looks great, thanks @EvanHahn!


Trying to use Postmark

Hi I have the following:
var transporter = nodemailer.createTransport({
    service: 'postmark',
    auth: {
        user: 'myusername',
        pass: 'mypassword'
    },
    headers: {"X-Postmark-Server-Token": "mytoken"}
});

Where I have double checked the username is what I set up my account with at Postmark.The username is NOT an email address. I have just put dummy text in here for the purpose of the example structure. I have double checked the password and I have double checked the server token and they are all correctly copy pasted, but I get the following error showing in my Node console.
{ [Error: Invalid login]
  code: 'EAUTH',
  response: '535 5.7.8 Error: authentication failed: ',
  responseCode: 535 }

Maybe for each of the services in well known it would help to have some more descriptions about how to set up each service, i.e. having to add the headers for Postmark.

The specified header is for HTTP based Postmark API but this module is for SMTP. You need to provide valid credentials for Postmark SMTP and you can remove the headers field as it doesn't do anything (there are no headers in SMTP)


Fix a node reparenting warning in the editor debugger

A small mistake, probably from a bad rebase, introduced by https://github.com/godotengine/godot/pull/53546. Caused the editor to complain about bad reparenting.

Thanks!


[WebSocket Client] WebSocket url token param value optimization

Fixes #10157
Modifications
Remove the Bearer  prefix requirement for the token param value of the WebSocket url.
Verifying this change
This change added tests and can be verified as follows:

Make the WebSocketHttpServletRequestWrapper return the right token value

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


use correct cache option in example

Thanks man! Totally missed that one 🍻

:tada: This PR is included in version 2.2.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Reloading Community page results in TypeError

On latest master (running Angular 5) this error can be seen.  I'm using Windows 10.
How to Reproduce:

Startup the app (e.g. yarn start).
Visit a community page, e.g. http://localhost:3000/communities/7669c72a-3f2a-451f-a3b9-9210e7a4c02f
Click the reload button in your browser

On the console, an error similar to this will appear:
TypeError: Cannot convert undefined or null to object
    at e.t.flattenSingleKeyObject (D:\programming\dspace-angular\dist\server.js:1:1081312)
    at e.parse (D:\programming\dspace-angular\dist\server.js:1:546606)
    at MapSubscriber.project (D:\programming\dspace-angular\dist\server.js:1:1133398)
    at MapSubscriber._next (D:\programming\dspace-angular\node_modules\rxjs\operators\map.js:79:35)
    at MapSubscriber.Subscriber.next (D:\programming\dspace-angular\node_modules\rxjs\Subscriber.js:90:18)
    at CatchSubscriber.Subscriber._next (D:\programming\dspace-angular\node_modules\rxjs\Subscriber.js:126:26)
    at CatchSubscriber.Subscriber.next (D:\programming\dspace-angular\node_modules\rxjs\Subscriber.js:90:18)
    at MapSubscriber._next (D:\programming\dspace-angular\node_modules\rxjs\operators\map.js:85:26)
    at MapSubscriber.Subscriber.next (D:\programming\dspace-angular\node_modules\rxjs\Subscriber.js:90:18)
    at FilterSubscriber._next (D:\programming\dspace-angular\node_modules\rxjs\operators\filter.js:89:30)

However, the Community page loads successfully in the browser with seemingly no adverse effects from this backend error.
This error seems to only occur when reloading Community pages.  Reloading the homepage, Collection pages or Item pages does not result in any errors.

NOTE: This issue and #224 may be related, as the errors are very similar

That is indeed due to this collection having a logo in its _links section, but that logo returning an empty response.
Closing this issue as a duplicate of #224


Fixing compilation issues with go1.7+

dgraph-io/dgraph is dependent on gotomic and this PR fixes the build breakage in Go1.7. So, if you guys can merge this, it would be very useful.

Thanks!


dialog boxes

to improve speed and efficiency and continuity, dialog boxes such as those in which a user is prompted to delete a file should have standard Yes or No options which are accessible via the keyboard. This reduces time as the user does not have to click nor alter hand placement nor use multiple keys to accomplish this task. It also improves continuity in that much of Atom is currently designed for ease and maneuverability via simple keys and key combinations. Lastly it is more efficient in that it requires less work to physically achieve this goal emphasized by the speed/work ratio.

Closing in favor of #2928 - feel free to subscribe there for updates.


Is it possible to rename admin panel?

Dear all,
Is it possible to rename the admin panel from S-Cart Admin to another name for example: Mars Admin?
I tried in the configuration on the left side but it didn't work, I also found that it is seeded into the database but I searched the whole database and couldn't find anything to change.
Best Regards,
Elias,

This problem wil fix in next update

Is it fixed in 6.0.6?

V6.1


MFKZQ01LM side and to_side

For the MFKZQ01LM Intelligent Magic Cube Controller the current implementation publishes 2 different values for flip90  (from_side/to_side) but only "side" for flip180 .
This means code wise you cant simply use side or to_side as depending on how the cube is moved on one of these values is actually correct and the other is possible eronious.
As such i propose that "side" should always been published ie side == to_side for flip90
else if (value >= 512) action = {'action': 'tap', 'side': value-512};
            else if (value >= 256) action = {'action': 'slide', 'side': value-256};
            else if (value >= 128) action = {'action': 'flip180', 'side': value-128};
            else if (value >= 64) {
                action = {'action': 'flip90', 'from_side': Math.floor((value-64) / 8), 'to_side': value % 8, 'side': value % 8};
            }

To this end technically to_side could be removed or the other optionn is flip180 could also be extened to include to/from_side attributes as if we know the final side then we can work out the from_side. Unfortunetly it appears we cant use simple math to add the the sides to 5.  As sides are not ordered like a normal dice.  As such we would need a lookup of some sort it seems.

Could you make a PR as proposal?


Internal Improvements

Hi @VGoshev
Here are some internal improvements at the code. I'll continue to make PRs on your repo. I need a seafile docker container, but the official seafile container is just crap (eg. haiwen/seafile-docker#25)
Explanation of commits:

Export PATH and inherit it to childs

PATH should be exported to prevent weird errors when ProgramA finds the executable, but ProgramB not.

apk related changes:

split the list into multiple lines and sort the packagelist (see the docker best practices)
Move the base packages into a separate layer. Although it is more common to have as less layers as possible, there are actually more pros than cons for it. (rebuild is much faster because of caching).

Export and define variables in one line

Small change for readability

Remove commented code

It's an anti-pattern commenting code and checking it into git, as git already has it in its history.

the trap KILL is effectively dead code, as the KILL-signal can't get catched.
the backticks are not neccessary and actually execute the code returned from grep. But this is not necessary, as grep states in its exit code if it had a match or not.

It turns out this got quite big. Sorry for this. Also I'm now including the two commits from #8 to resolve merge conflicts.
I hope this improves code quality and gives a better basement for forthcoming PRs.

ping @VGoshev

I decided to give up on Seafile. It's simply not possible to dockerize it properly and split the seahub program from the data and configuration.
Last weekend, I developed this container further outside of this PR. I progressed so far, that I already ported all build.sh instructions into a clean Dockerfile, but I never ever could get over that seahub constraint.
Researching this topic in the GitHub bugtrackers revealed many more bad things and habits of seafile, that I even decided to drop it.
I'll close this PR, but KIM these commits are still valid and are able to get cherry picked.


Release proposal: standard v11

Planned release date: Feb 18, 2018. This release has been in beta since December.
Try it now: npm install standard@beta --global
This release has no new rules, but it does update to the latest version of eslint,
version 4, which has some significant changes to existing rules. Most updates make
the rules more strict.
Thankfully, most users will just need to run standard --fix to update code to be
compliant.
New features

Update eslint from ~3.19.0 to ~4.16.0.

The indent rule is more strict.
The padded-blocks rule is more strict.
The space-before-function-paren rule is more strict.
The no-multi-spaces rule is more strict.
Minor improvements to:
no-extra-parens,
no-unexpected-multiline,
no-regex-spaces, and
space-unary-ops

Update eslint-plugin-import from ~2.2.0 to ~2.8.0

Updated for eslint 4.0 compatibility.
Various small bug fixes included related to import/* rules.

Update eslint-plugin-node from ~4.2.2 to ~5.2.1

The no-deprecated-api rule is updated with Node.js 8 support and improved
Node 6 support.

Upodate eslint-plugin-promise from ~3.5.0 to ~3.6.0.

Update eslint-plugin-react from ~6.10.0 to ~7.6.1

Fix jsx-indent crash
Fix jsx-indent indentation calculation with nested JSX.
Fix jsx-no-undef will not check the global scope by default.
Fix jsx-curly-spacing newline with object literals bug
Fix jsx-curly-spacing schema incompatibility with ESLint 4.2.0.
Fix alignment bug in jsx-indent.

Huge thanks to @Flet for putting together most of this
release!

🗣 Standard 11 is released! Run npm install standard@latest --save-dev to update to the latest version. This will also update the version in package.json ✨
Changelog: https://github.com/standard/standard/blob/master/CHANGELOG.md#1100---2018-02-18


Add str words count function

Fix typo in function documentation , missing '.'

Duplicate PR?

Duplicate PR?

Where ? Function wordsCount already exists ?

It is a duplicate of the other two PRs you already sent.


Switch to Ruby 3.0

Coverage: 98.072%. Remained the same when pulling a9e2eb6b9d5a3137cd47042aa31bad5ce4682f8b on ruby-3 into 003789baee7af4030abebd77bc74dbde11cc25e8 on master.


TimePicker 24hour format selection

Hi. I'd like to set 24 hour format selection in TimePicker. So far I have to set if this is AM or PM, which is not pretty common in Czech format.
Environment
MahApps.Metro v<IP_ADDRESS>
Windows OS 10/7
Visual Studio 2015
.NET Framework 4.5.2

@honzasram The AM/PM comes from the Cultures properties DateTimeFormat.AMDesignator and DateTimeFormat.PMDesignator.

@punker76  Thank you for reply. However, I'm not pretty sure if I understand. What exactly should i add to code?
Even if I set up Culture to "cs-CZ" which uses 24 hour format by default, I Get this

I want to get rid of AM/PM selector (in this case dop./odp.) and get all 24 hour to hour combobox.
Code:
 <controls:TimePicker Margin="2"                                                       IsClockVisible="False" Culture="cs-CZ"                                                       PickerVisibility="HourMinute"                                                       SelectedTime="{Binding ActionSelectedTime,                                                                          ValidatesOnDataErrors=True,                                                                          UpdateSourceTrigger=PropertyChanged,                                                                          NotifyOnValidationError=True}"/>

@honzasram Ok, you're right. I found the problem and will fix it in 1.6.0 (and alpha).

@honzasram You can test the latest alpha version.


Open app with deep link

Would be nice to be able to open the app with a deep link:

For some E2E tests, we are directly starting a flow with a deep link because the logic before is handled with a different E2E test.
We also want to E2E test if the apps open correctly when we send a deep link to the system.

That is a good use case, let us think about how to add it 👍

We have introduced an openLink command: https://maestro.mobile.dev/guides/using-maestro-cli/open-link


Why?

Could you elaborate?

  Even after all that work the end result looks like garbage.  Not enough to do at google?  How's the self-driving car team doing?  Could they not use some help?  People are literally dying in preventable car crashes everyday while you guys waste time on this trash.

@quinton-ashley For note, even if these were the people that worked on the cars (which I doubt), most programmers tend to need 'fun' projects like this on occasion to help clean and reset the brain.  Things like this can substantially improve productivity when working on the more heavy/difficult problems.

Yeah at first I thought these kind of pointless joke repos were funny, like the equivalent of youtube poops of the open source programming world.  But then I started thinking that programmers have more social responsibility than some random dude with MSPaint and the trial version of Resolve.  I looked back in there commit history and there's been active work on it since April 19th.  I understand the need for 'fun' projects on occasion but I feel like this crosses the line ya know?  I'm not against joke repos in general, I made one called hendriks, but I think good joke repos are simple ideas that can be done in a few hours, not multi-month projects.

@quinton-ashley I initially assumed you must be some random person who joined GitHub just to complain, but when I looked at your profile I saw you're a pretty prolific coder, whose profile is filled with video game re-skins and other projects that are less than strictly necessary to the future of humanity.

While not strictly necessary to the future of humanity the important distinction is those projects aren't joke repos and they're not pointless.

At best a joke repo can inspire young people to take an interest in computer science.  At worst they are pointless, multi-month long, masturbatory displays of wasted productivity that somehow manage to get over 1,000 stars on github.

I don't know what you mean by a "joke repo", this is an actual program that can be installed and run. As for pointless, that's a matter of opinion; replacing textures in video games or creating a repo for changing whitespace could easily be labelled pointless.
I'm not sure how you found this project, but perhaps this will shed some light:
https://opensource.googleblog.com/2018/06/tenor-gif-for-cli.html
You wanted higher res textures in your games, I wanted an animated GIF to show up when I SSH into my workstation (and I wanted to share the code I used to do that), big diff.

These are all fun projects but I think if you asked the Dolphin developers and texture packing community if what they were doing could be as easily labelled a joke or pointless I think they would strongly disagree.  I think Dolphin and texture packs do have some real value to humanity in terms of both cultural preservation and enhancement of older video game software for future generations.  hendriks can actually be installed and run too but I would label it a joke repository because I made it so that people who've watched Silicon Valley could read the readme and at most, test it out and have a quick laugh.
I will admit I was wrong though, this isn't a joke repository or pointless to you if you're actually going to use it day to day.  I like ASCII art and moving ASCII art is cool too but I was certain this repo was a joke because watching such a poor quality degradation of a gif in a terminal window is kind of ridiculous when you could just watch it in the browser in "full" quality.  ("full" in quotes for the Deadpool 2 gif because the film was shot in 3.4k so the gif is also degradation, as many gifs are.  I probably would've had trouble recognizing it without seeing the original gif.)
After reading your blog post and your last sentence in the comment above I can tell that you would label this repo an art project and not a joke so I apologize for my interpreting it as such.  Sorry for attacking you without all the information, I wouldn't have if I had read the blog post first.  I found this repo from the github trending page and read through the readme.

 It's actually pretty cool and I can appreciate it now that I have a better understanding of programming, politics, and the world in general.
So again I'm sorry and you were right. Could you delete this issue please?


[SPARK-15587] [ML] ML 2.0 QA: Scala APIs audit for ml.feature

What changes were proposed in this pull request?
ML 2.0 QA: Scala APIs audit for ml.feature. Mainly include:

Remove seed for QuantileDiscretizer, since we use approxQuantile to produce bins and seed is useless.
Scala API docs update.
Sync Scala and Python API docs for these changes.

How was this patch tested?
Exist tests.

Test build #59651 has started for PR 13410 at commit 570c333.

Test build #59651 has finished for PR 13410 at commit 570c333.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59651/
Test PASSed.

LGTM

Merged to master/branch-2.0


DBScan clustering instead of k-means

Apply the DBScan algorithm from SKLearn on time series data
properly tune hyperparameters

Hi @MaxRonce what's the status of that issue ?


chore!: move to node 14 as minimum version

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Need to make sure that https://github.com/googleapis/node-gtoken/pull/452 goes along with the upgrade / major version bump.


Tests for ink contracts

Tests for ink contracts, to be run:

on every commit/PR on main branch
after every network upgrade

Let's wait for this PR to be merged.

@andrii-kl if you are running locally, you need to have the ice-node v0.4.58 executable available in your ts-tests/ink/assets folder


Can't add reviewers to a PR

I created a PR (in this repo actually), and then clicked the '+' Reviewers as I have many times. Instead of showing the list of possible reviewers to add, I got an error toast "e is not an iterable", which also showed in the console.
 It shows the user picker, but then shows an error "Must have admin rights to Repository"

I think I've fixed this with https://github.com/microsoft/vscode/commit/fd88fb9667a70f9b0a81dbf36ef07d7fb330d0c7
I believe you're in a state where when you signed out, the token got revoked but not removed from the keychain, and now when you try to sign out, trying to revoke it again throws, preventing it from being removed ever
Let me know if signing out and in again now works.

It seems that I'm lacking a way to sign out of GitHub. What am I missing here?

If you have a "configurationSync.store" setting, can you remove it? That should cause the accounts icon to appear, where you can sign out from

I'm wondering if maybe I should expose logout in the auth provider API and we should keep the sign out command, it seems currently very hard to discover

Done. I still get many sign in problems. The PR extension often claims I've signed out. I also appear to be lacking the scopes required (or have some other problem) to comment on a PR and to merge a PR.

I still haven't been able to reproduce the random sign outs - does it seem like it's always tied to a user action like starting a PR, or does it sometimes just happen?
For the comment/merge problem, when changing to the new authentication provider, we changed from using a first party GitHub app to a third party app. Accessing data on organization-owned private repos doesn't work by default for third party apps, and it seems like there are other operations that fail as well. I'm working on getting back to a first party app.

Closing as I believe this has been fixed by the upstream changes to the GitHub auth provider


Artifacts with Laser, BiDir and Volumetrics

Shooting a laser beam into a homogeneous volume shows a few issues:

A dark band may appear around the center of the image.
The directly visible beam (camera -> volume -> laser) appears to decay very quickly. This effect seems stronger for a large laser size.
After a glass object, the decayed beam reappears.
The direct beam appears to build up in two components: The decaying part, which renders noise-free very quickly, and a more constant beam path that renders slowly and looks similar to the result using the Path engine. I would hence assume that the decay-issue is caused by light rays rather than camera rays.
images and blend-file attached to demonstrate the problem

bidir_volume_lightrays2.zip

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

There are several versions of this bug reported here with example pics and files.

Update: The issue is not limited to lasers. observed also with a point-source that was collimated with a parabolic mirror. So, perhaps connected to paralell light beams?

As far as I know, this problem has been fixed.


Timeout should match value in read/write_timeout

Expected
Timeout value in main.go should match value in read/write_timeout env-vars (these are Golang durations)
Actual
Hard-coded to 3 seconds
This is the same in both variants of the template.
Merge criteria
For a merge this will need:

demonstrated (with console output) end-to-end testing showing timeout met and cancelled, a request within timeout limits
golang-http and golang-middleware both need to be updated including armhf versions

@ewilde PTAL?

Closed by #23


ReferenceIndex model registration

Fixes #9731, supercedes #9936
This PR proposes an alternative way to configure the models that are indexed by the ReferenceIndex system. Instead of indexing all models including non-Wagtail-related models by default, this alternative requires models to be specifically registered.
In this implementation, models subclassed from Wagtail AbstractPage, AbstractImage and AbstractDocument models, including the default Page, Image and Document models, are by default indexed, as are models registered as Snippets and with ModelAdmin. The developer can exclude these models as desired, and register their own models via an app.ready() hook, as suggested in @gasman's comment.
This implementation is a draft. All the existing tests pass without change, however some further tests are probably warranted and the documentation will need to be updated. I am submitting this at this stage to get feedback on the overall approach which I describe below, and to get the reports from the full CI testing.
As this is likely to be considered a breaking change, @gasman expressed a desire to get this into the 5.0 release, I'd appreciate a fairly swift initial review so I can make appropriate changes including the tests and documentation. Feedback on suitable additional tests and possible deprecations would also be useful.
Approach
Here are the key changes:

ReferenceIndex.model_is_indexable() is no longer being called for every updated model instance. Instead, it is used to form ReferenceIndex._indexed_models which stores the models that need to be tracked via Django's post_save signal, and which are to be indexed. This list is formed using the new ReferenceIndex.register_model() method, which is for instance called in wagtail.apps.WagtailAppConfig.ready() for the default model types. Other apps can use the same technique to register their models as required. Note that model_is_indexable() still checks the wagtail_reference_index_ignore attribute to disable indexing where required.
a new ReferenceIndex.is_indexed() method replaces ReferenceIndex.model_is_indexable() to provide a public interface to lookup the _indexed_models cached information.
in wagtail.signal_handlers the post_save and post_delete signals are used as before, but only the necessary models are being tracked (using sender=), to remove the impact on non-Wagtail apps and models.
Snippet and ModelAdmin model registration has been added.
there is a new management command show_references_index which shows which models are indexed and how many index records are currently in the database.

Existing Tests
As mentioned, the existing tests all pass without change, although it was necessary to register one model explicitly, PageChooserModel.
Below I've documented the models that are no longer being tracked within  testapp in case there are models anyone believes should be indexed by default:
wagtail.contrib.redirects.models.Redirect
wagtail.test.testapp.models.RelatedGenericRelation
wagtail.test.testapp.models.CustomFormPageSubmission
wagtail.test.testapp.models.EventPageChooserModel
wagtail.test.testapp.models.SnippetChooserModel
wagtail.test.testapp.models.SnippetChooserModelWithCustomPrimaryKey
wagtail.test.testapp.models.JSONStreamModel
wagtail.test.testapp.models.JSONMinMaxCountStreamModel
wagtail.test.testapp.models.JSONBlockCountsStreamModel
wagtail.test.testapp.models.ImportantPagesSiteSetting
wagtail.test.testapp.models.ImportantPagesGenericSetting
wagtail.test.testapp.models.SimpleTask
wagtail.test.search.models.Character
wagtail.test.i18n.models.TestNonParentalChildObject
wagtail.test.streamfield_migrations.models.SampleModel
wagtail.contrib.search_promotions.models.QueryDailyHits
wagtail.contrib.search_promotions.models.SearchPromotion
wagtail.contrib.forms.models.FormSubmission
wagtail.models.sites.Site
wagtail.models.collections.CollectionViewRestriction
wagtail.models.collections.GroupCollectionPermission
wagtail.models.GroupPagePermission
wagtail.models.PageViewRestriction
wagtail.models.WorkflowPage
wagtail.models.WorkflowContentType
wagtail.models.Task
wagtail.models.Workflow
wagtail.models.GroupApprovalTask
wagtail.models.WorkflowState
wagtail.models.TaskState
django.contrib.admin.models.LogEntry
django.contrib.auth.models.Permission

Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[x] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thanks @gasman. Assuming there are no further coding concerns, I'll work on the documentation now. I doubt I will get to any additional tests tonight.

I've prepared the documentation @gasman, including a one-line entry in the new features section - of course, you might consider this a fix or maintenance.
Realistically, this is all I can do on this tonight. Happy for you to take this forward today, and I can resume and develop some tests later tomorrow.

I've added a test for the new management command show_references_index.
I believe the existing tests adequately exercise the refactored code.
So should be good for a final review.

Rebased at #10364


Uptime Robot not wotk

Uptime Robot not work always
UptimeRobot API Key not configured.
i do all how on wiki
create monitor
put in Friendly Name *
ua.stratum[.work]
in host url of pool
in port stratum port
end for ua.www[.work]
but it now work
WTF do for it's start work ?
on pool i try put
apikey|ua.www[.work]
apikey|ua.www
apikey|ua
apikey|ua.www[.work],
how make this work ???????????

Don't use [.work], use .work. [] indicate optional variables. Then use the exact name after the monitoring specific API key. You may have to generate the key since they are not automatically generated. And don't use the master API Key.

Hello, I've been testing the api in every possible way for several days....
And i can not connect the api with mpos.
here correct format:
m77xxx09x2-8a786axx0b65f0axx2x99fa7|de.stratum.whatever
on guide example is it:
MONITOR_API_KEY|MONITOR_NAME,MONITOR_API_KEY|MONITOR_NAME,...
what am I doing wrong?

Is the Cron running? Any error in its logs?

[IMG]http://i63.tinypic.com/2ihuyas.png[/IMG]

the pool its new and i dont found any block..

yes all running..

Found the issue, UptimeRobot switched to HTTPS only without a redirect, so the hard-coded URL in the code wasn't valid anymore.
Committing a fix to a branch you can test out, it also includes a small Smarty fix for PHP 7. If you run PHP 6 please check your Apache Error log for any errors caused by this change :-)

Please try with branch issue-2565-uptimerobot.

Working fine 👍

Merged into development.

Merged and released from Dev to Master as MPOS 1.0.6.


Updating codecove action

Still not working, lets wait for the dust to settle:
https://github.com/codecov/codecov-action/issues

superseeded by https://github.com/f3d-app/f3d/pull/1406


Added tests for attached property resolution edge-cases.

What does the pull request do?
While investigating #7925 I added a few tests which tested attached property syntax and cross-referenced them against WPF. It turned out that #7925 was caused by something unrelated, but there is one slight edge-case in our attached property lookup.
In WPF, the following produces an error (although weirdly, it is allowed in a style setter):
<TextBlock TextBox.Text="Foo"/>

This is allowed in Avalonia because TextBox.Text is being resolved to TemplatedControl.Text and works because TemplatedControl.Text and TextBlock.Text actually are the same property - they're both AddOwnerd attached properties defined on TextElement.
This PR changes our attached property resolution to only search for attached properties on the stated class, TextBox in this case. We retain the same behavior as WPF in that TextBox.Text can be set on a TextBlock from a style setter.
The previous fix was incorrect: leaving the unit tests here for later.
Breaking changes
~~No API breaking changes but might be best not to port this to stable in case anyone is relying on this edge-case.## Now contains only unit tests.
Fixed issues
Fixes #7925

Actually, thinking about this some more, may not be correct.

Nope, the fix in this PR was incorrect. I've undone the incorrect "fix"; leaving this PR with a few failing tests to be addressed.


Detect use of act (running workflows locally)

Each time we would like to use act and run the workflow locally, we need to add
runs_on: ubuntu-latest  flag.
It would be great if we could detect it in magma.
Useful resources:
https://nektosact.com/usage/index.html?highlight=act#skipping-steps
Something similar could be added to the pre-job?
https://stackoverflow.com/questions/71961921/specify-runner-to-be-used-depending-on-condition-in-a-github-actions-workflow

There is no need to implement anything because we started using the -P act flag, which is useful for pointing the tag to a custom docker image.


CB-21065 Nodes placement by hints for  ENTERPRISE datalake

Context: Datalakes templates will have "hints" for multi-az node placement. This PR creates the mechanism that uses hints to decide which availability zone the node will be placed in.
Part 1: https://github.com/hortonworks/cloudbreak/pull/14640 (Wait for part 1 to be merged to review this one)
Test:
Created an ENTERPRISE datalake using the --multi-az flag then checked that the nodes were placed in the right AZs following the hints.

Closing the PR, please re-open if it's still relevant.


Add create role to interactive cli

Add new permission model to interactive cli

The following tests FAILED:
	  3 - ametsuchi_test (Failed)
	  4 - wsv_query_command_test (Failed)

Can you check it?

https://github.com/hyperledger/iroha/pull/602#issuecomment-333799218 those tests also fail on feature/permission branch

Codecov Report

Merging #602 into feature/permissions will decrease coverage by 0.01%.
The diff coverage is 36.36%.

@@                  Coverage Diff                   @@
##           feature/permissions    #602      +/-   ##
======================================================
- Coverage                43.62%   43.6%   -0.02%
======================================================
  Files                      292     292
  Lines                    11699   11729      +30
  Branches                  6325    6344      +19
======================================================
+ Hits                      5104    5115      +11
  Misses                     757     757
- Partials                  5838    5857      +19

Impacted Files
Coverage Δ

irohad/model/generators/command_generator.hpp
100% <ø> (ø)
:arrow_up:

irohad/model/generators/impl/block_generator.cpp
63.63% <100%> (ø)
:arrow_up:

irohad/model/generators/impl/command_generator.cpp
22.85% <15.38%> (-3.23%)
:arrow_down:

...ad/model/generators/impl/transaction_generator.cpp
56.41% <44.44%> (-1.66%)
:arrow_down:

irohad/model/permissions.hpp
14.7% <50%> (+14.7%)
:arrow_up:

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 5a05e8a...a7b08cb. Read the comment docs.


add haskellR example (currently not working because of ghc844)

the issue is:
https://github.com/commercialhaskell/stackage/issues/4216

Closing this example too, since it is not fundamental and has been stuck for more than one yeat.


Minor optimize shared_ptr usage LogicalPlanner::plan and CallbackSink

@mbasmanova This patch minor optimize the shared_ptr usage in CallbackSink during building the operator and using it. Other usage like dynamic_cast_pointer might copying but they just copying in the LogicalPlanner and doesn't copy the data during exec


Internationalization problem in Ubuntu

Description
The Russian font is not displayed in the dialog box for opening a file or directory (see screenshot).

Steps to Reproduce

File \ Open
File \ Open directory

Versions
Ubuntu 16.04 / 16.10 / 17.10
sprint 11 build 1.11.0-17524 (release 86b5e2d4e)

Duplicate of #13738


One liner for csh

Hi, is there a one liner to activate in csh?

The one liner is the same
dircolors ~/.dir_colors/dircolors.nordtheme
where dircolors.nordtheme is the file https://raw.githubusercontent.com/nordtheme/dircolors/develop/src/dir_colors copied directly.
You can run it standalone to see if the 'setenv LS_COLORS=<>` indeed has the color config.
In your ~/.cshrc file, you can add eval \dircolors ~/.dir_colors/dircolors.nordtheme`somewhere to set theLS_COLORS` env var.


Entity viewer analytics hook

Type

[ ] Bug fix
[ ] New feature
[x] Improvement to existing feature

Related JIRA Issue(s)
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-1368
Description

Updated the analytics service to handle feature as a dimension
Created the analytics hook for entity viewer
Added the tracking events to track the tab changes

Deployment URL
http://ev-ga-hook.review.ensembl.org
Views affected
Entity viewer -> Change tabs

How does setting a custom dimension work? How long is it reported?
In the following scenario, for example: Species Selector -> Entity Viewer -> Species Selector, when user returns to species selector from the entity viewer, will all analytics events sent in species selector contain the feature dimension set in entity viewer?

How does setting a custom dimension work? How long is it reported?
In the following scenario, for example: Species Selector -> Entity Viewer -> Species Selector, when user returns to species selector from the entity viewer, will all analytics events sent in species selector contain the feature dimension set in entity viewer?

Currently, the scope for feature dimension is set to hit and I thought it will be valid until the next hit but it doesn't seem to be the case. It is using the same value for subsequent hits as well. I guess we need to set and reset it for every hit 😞


How MAX_ITERATION is calculated in smoke_gn_vector.yaml?

Hello!
First, thanks so much for releasing the code! It has very high quality and is very tidy and concise.
I wonder how the MAX_ITERATION is calculated. Is it calculated based on the number of images on 'trainval' ? In other words, 'trainval' has 7481 images, you trained it using batch_size=32 with 60 epochs. In my calculation, the total m will be 7481*60/32 =14026 iterations. However, in your config, MAX_ITERATION is 25000, about twice times as my calculation. Do I miss anything?
Thanks in advance!

Hi @Xianpeng919,
I think your calculation is right. I assume the configured max_iteration in the config file is just some arbitrary number. If you look at the default configuration (https://github.com/lzccccc/SMOKE/blob/bc5d2bba66e2d66fa56b7b599d55457cb1a05b33/smoke/config/defaults.py#L128), you will see that 14500 iterations are used which are much closer to your calculated value.


chore: add strict types

add declare_strict_types rule to php-cs-fixer
add declare(strict_types=1)
run cs-fix by latest version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
332

Relevant Lines:
422

💛  - Coveralls


Basic Expression & Poly Differentiaton

I don't know why some additional commits are not showing...
New commits are in commit history, but not in here.


Allow UTCDateTime to be created from DateTime

Add a static method UTCDateTime::createFromDateTime(\DateTime $datetime) that returns a UTCDateTime-instance

Same for DateTimeImmutable


Release 2.4.8

Coverage remained the same at 99.5% when pulling 9d7884c4f6691f98b6d200edd2c6608738909d3f on develop into 339ad7a897ae10a1e3c27dfd41e2382b1ab30e7a on master.


Update mixin dashboard

Update and rewrite the mixin dashboard to use the grafonnet ([1]) library.
Grafana has deprecated angular plugins ([2]) as used by grafonnet-lib ([3]) with removal pending for grafana version 12. Additionally grafonnet-lib is deprecated/unmaintained in favor of grafonnet.
Therefore the mixin dashboard has been updated to use grafonnet.
[1]
https://github.com/grafana/grafonnet
[2]
https://grafana.com/docs/grafana/latest/developers/angular_deprecation/
[3]
https://github.com/grafana/grafonnet-lib
Closes: https://github.com/prometheus/alertmanager/issues/4077

Hello @gotjosh sorry for the direct ping, but you seem to be the maintainer with the most recent commits in the mixin. Could you take a quick look and give me some feedback on whether this is interesting for you at all? Thank you

Thank you so much @janhorstmann - do you mind showing me an example of how the mixin looks like after your changes? It's easier if I don't have to manually test it myself.

This is a screenshot of my test instance with the new mixin dashboard. I tried to follow the original as closely as possible. Let me know if you notice any differences


Several updates (see desc)

surprised robot to happy robot transition; + some spacing fixes for stacks and composes
parser fixes : i am 96% confident i will not need to touch this parser again except for function arg stuff. colorswaps work fine now; and everything i tested rendered fine
minor text wrapping changes
buttons !! to export !! so exciting (i would recommend using the png and also setting scale in consts/variableconsts.ts to a higher number; the default res is not a lot of pixels. the buttons are ugly but we can change that later.

@adrianleh Removing the SVG functionality for now if you wanna merge it w the new changes. it should be the right sizes now


remove Exceptions module; define error type where it's used

Following up on comment here.
The logic was that, conceptually, this exception has nothing to do with DeterministicVI, and could be used elsewhere in the code. But practically, if it's only used in one place right now, with no immediate plans to use it elsewhere, I'm happy to define it where it's used and it can easily be extracted to a standalone module later if it gets reused.
(The counterargument is that putting it in a shared place to start with encourages reuse by making it easier for developers to find. But it's speculative, and I'm not concerned.)

Thanks Steve!


Memory leak with SSL enabled

I download the example.
admin@dev:~/collect-v2/clients/cclient$ wget https://raw.githubusercontent.com/zhaojh329/libuwsc/master/example/example.c
--2020-01-08 14:39:29--  https://raw.githubusercontent.com/zhaojh329/libuwsc/master/example/example.c
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4317 (4.2K) [text/plain]
Saving to: ‘example.c’

example.c                                            100%[=====================================================================================================================>]   4.22K  --.-KB/s    in 0.002s

2020-01-08 14:39:29 (2.69 MB/s) - ‘example.c’ saved [4317/4317]

I compile it.
admin@dev:~/collect-v2/clients/cclient$ gcc -I/usr/local/include/uwsc -I/usr/include/json-c -I/usr/local/include -L/usr/local/lib -L/usr/local/lib/uwsc -lpthread -ljson-c -lev -luwsc -o example example.c

I run the program and valgrind using -u ws://localhost/ws
You can see there are no memory leaks reported by valgrind.
admin@dev:~/collect-v2/clients/cclient$ valgrind --leak-check=full ./example -u ws://localhost/ws
==3970== Memcheck, a memory error detector
==3970== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3970== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==3970== Command: ./example -u ws://localhost/ws
==3970==
2020/01/08 14:40:35 (example.c:141) Libuwsc: 3.3.2
2020/01/08 14:40:36 (example.c:147) Start connect...
2020/01/08 14:40:36 (example.c:91) onerror:2: Invalid header
==3970==
==3970== HEAP SUMMARY:
==3970==     in use at exit: 1,016 bytes in 6 blocks
==3970==   total heap usage: 66 allocs, 60 frees, 43,855 bytes allocated
==3970==
==3970== LEAK SUMMARY:
==3970==    definitely lost: 0 bytes in 0 blocks
==3970==    indirectly lost: 0 bytes in 0 blocks
==3970==      possibly lost: 0 bytes in 0 blocks
==3970==    still reachable: 1,016 bytes in 6 blocks
==3970==         suppressed: 0 bytes in 0 blocks
==3970== Reachable blocks (those to which a pointer was found) are not shown.
==3970== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==3970==
==3970== For counts of detected and suppressed errors, rerun with: -v
==3970== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

I run the program using an SSL URL and valgrind using -u wss://localhost/ws
You can see the program has a memory leak from libuwsc!  Can you fix this please?
admin@dev:~/collect-v2/clients/cclient$ valgrind --leak-check=full ./example -u wss://localhost/ws
==3971== Memcheck, a memory error detector
==3971== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3971== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==3971== Command: ./example -u wss://localhost/ws
==3971==
2020/01/08 14:40:40 (example.c:141) Libuwsc: 3.3.2
2020/01/08 14:40:40 (example.c:147) Start connect...
2020/01/08 14:40:41 (ssl.c:141) (null)
2020/01/08 14:40:41 (example.c:91) onerror:7: ssl handshake failed
==3971==
==3971== HEAP SUMMARY:
==3971==     in use at exit: 162,494 bytes in 2,922 blocks
==3971==   total heap usage: 4,628 allocs, 1,706 frees, 370,000 bytes allocated
==3971==
==3971== 73,990 (824 direct, 73,166 indirect) bytes in 1 blocks are definitely lost in loss record 296 of 296
==3971==    at 0x4C2BBAF: malloc (vg_replace_malloc.c:299)
==3971==    by 0x61FDC87: CRYPTO_malloc (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2)
==3971==    by 0x5F5E2EF: SSL_new (in /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2)
==3971==    by 0x5473783: uwsc_ssl_init (in /usr/local/lib/libuwsc.so.3.3.2)
==3971==    by 0x54715FC: uwsc_init (in /usr/local/lib/libuwsc.so.3.3.2)
==3971==    by 0x54716A3: uwsc_new (in /usr/local/lib/libuwsc.so.3.3.2)
==3971==    by 0x109173: main (in /home/admin/collect-v2/clients/cclient/example)
==3971==
==3971== LEAK SUMMARY:
==3971==    definitely lost: 824 bytes in 1 blocks
==3971==    indirectly lost: 73,166 bytes in 37 blocks
==3971==      possibly lost: 0 bytes in 0 blocks
==3971==    still reachable: 88,504 bytes in 2,884 blocks
==3971==         suppressed: 0 bytes in 0 blocks
==3971== Reachable blocks (those to which a pointer was found) are not shown.
==3971== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==3971==
==3971== For counts of detected and suppressed errors, rerun with: -v
==3971== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

This is with openssl.

You can get around the memory leak being a problem in a reconnect loop by using uwsc_init() instead of uwsc_new:
if (cl->sock == 0) {
    uwsc_init();
}

It will just never reallocate memory for SSL as it doesn't properly free() everything when you ev_break() or ev_timer_stop() or free(cl).

This is with openssl, I'm trying now with mbedtls since the ssl init code in libuwsc is very different.


MPS_search.jl tests

Tests in this file in the current form are done by copying code from functions like _apply_bias!. This should not be the case. There should be a precomputed expected output of the function, which should be compared to the actual output.

Well, functions like the one mentioned act on MPS, whereas the similar code in the test file builds tensor explicitly. This by itself is a good test. That said, some simplifications would not hurt...

I agree with @lpawela that the testing code should not copy the code from the methods under test. Otherwise, if the former is broken, the latter is broken as well and yet the test will pass.
As a side note, those tests are not very descriptive and don't illustrate the usage of the mentioned functions (i.e. if I didn't know what _apply_bias! does I still wouldn't know what it does after reading through tests).

Change it to whatever you want it to be then.

BTW; Which parts of the code are copied exactly from their underlying functions?


only build jdbc bridge when building be

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)


Date & Time format - need setting to change

The A2 server GUI is showing date and time in US format (e.g. 09/25/2018 2.15PM). Where can we find the setting to change it to ISO8601 format (2018-09-25 14:15)?
https://chef.aha.io/epics/A2-E-152?active_tab=related

Duplicate of #4745.


xfce4-13: init

Motivation for this change
Prepare for upcoming Xfce 4.13 release. Most, but not all, components have been switched to GTK+ 3.
This is a clean-room packaging effort and differs from currently packaged Xfce in some ways:

build entirely from source, using xfce4-dev-tools, source from Git
package latest versions rather than Xfce 4.12 branch
mark optional dependencies as such
abstract away common parts via mkXfceDerivation
attribute names match upstream names
overridable scope (created via makeScope)

There are quite a few Autoconf fixes that had to be made, mostly related to their dbus_glib -> gdbus switch. I've talked with Xfce devs and plan to upstream these fixes before the release.
Everything works, except:

xfce4-volumed is missing (but not xfce4-volumed-pulse): release is not tagged
Doesn't include xfce4-panel plugins, yet
Thunar doesn't seem to work, yet (needs to be wrapped)

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Nitpick: when Xfce makes a (stable) release, they will surely call it 4.14, so we might as well start calling it that way.  (In most packages they use the even-odd scheme, e.g. like gnome.)  BTW, I see no indication that the release will come soon, but I don't think that matters at all – people can test now already – perhaps some will finally manage to get rid of gtk2.

Makes sense! However, if we plan to package Xfce 4.15 the same way, we might call it xfceUnstable.
In master, they have ported all of Xfce core and all default apps to gtk3 except xfwm4. That makes me think it will be released soon (probably not in next several months, but given their release cycle even half a year from now is soon), but of course they don't have any public deadline.
I agree. I'll wrap a NixOS module soon: not sure how to call it yet though (see above). It might make sense to make it swappable, i.e. to have services.xserver.desktopManager.xfceUnstable.attrset option where xfceUnstable top-level Nixpkgs namespace is passed as a value.

@GrahamcOfBorg build xfceUnstable.xfce4-panel xfceUnstable.xfdesktop

In recently released xfce4-panel 4.12.2 and 4.13.2, only the latter includes bugfixes.
Just another argument for having them both in nixpkgs

This should get in by 18.03 release at latest. I plan to finish it (wrap Thunar, package xfce4-panel plugins, include NixOS module) by the end of the year.

is it abandoned?

No, it's not. Sorry about the delay.

Let's merge to unstable/18.09 ?

Well, let's merge. Some packages still probably need wrapping, but it's better than nothing.

Some packages still probably need wrapping, but it's better than nothing.

Should be ok for pkgs.xfceUnstable on unstable branch :)

one more reason to merge :)
otherwise we will get 4.13 in place of 4.12 as the result of automated upgrades

OK, merging.

Building...
So far xfce4-session is missing


Set default driver name to pmem-csi.intel.com

As per CSI specification plugin name should include plugin's host company name
and the plugin name. And it must follow domain name notation format.
Hence set default plugin name to 'pmem-csi.intel.com', which can be altered
using -driverName command-line argument.
Signed-off-by: Amarnath Valluri<EMAIL_ADDRESS>

If default name is already set, why do we set it again to same value in activation in deployment file?
Is it for showing example how to change it?
But then, if CSI spec requires it be in certain form, why do we even provide method of overriding it via CLI, as changed value will potentially lead to violating CSI spec?

If default name is already set, why do we set it again to same value in activation in deployment file?
Is it for showing example how to change it?
But then, if CSI spec requires it be in certain form, why do we even provide method of overriding it via CLI, as changed value will potentially lead to violating CSI spec?

Yes, i agree. These questions are valid.
One quick thing in my mind is when we support 'ephemeral' volumes, one might need to deploy the diver with different driver name(pmem-csi-ephemeral.intel.com) , as kubrenetes inline volume design expects driver can implement either "persistent" or "ephemeral" volumes.

Olev Kartau<EMAIL_ADDRESS>writes:

If default name is already set, why do we set it again to same value in activation in deployment file?
Is it for showing example how to change it?

That, and to make it more visible. The same string also occurs in the
storage class .yaml. It's redundant, but I'm in favor of keeping it.

But then, if CSI spec requires it be in certain form, why do we even
provide method of overriding it via CLI, as changed value will
potentially lead to violating CSI spec?

The E2E testing could use this to install the driver multiple times in
parallel. It no longer does that, but perhaps we want it back for some
test.
Having the driver running multiple times with different behavior is a
more realistic use-case. As @avalluri said, ephemeral volumes will have
to do that.

we do not change the drivername in deploy example of unified mode? That's the one we use in e2e test now, I plan to run this PR through e2e

we do not change the drivername in deploy example of unified mode?

Ya, i missed this, shall I change this too.

I fixed the driver name in unified mode deployment.

Is it good enough for merging?

@okartau Ping


doc: doxygen: Remove kernel tests

Remove kernel tests from Doxygen INPUT as they end up unnecessarily included in the generated API documentation, where they can cause confusion as to what is/isn't API and generally make it harder to find information.

FWIW, https://github.com/zephyrproject-rtos/zephyr/commit/7a6f7136bb82316bbfcd6d1f3dd40d1cf32fec12 by @nashif is the commit that added tests/kernel to the input list.

FWIW, 7a6f713 by @nashif is the commit that added tests/kernel to the input list.

Ya thanks, I had tracked it down too this commit too :) Thanks for explicitly flagging @nashif as he may have some input there.


crash - missing camera transitionPeriod

With pymods installed and others, on adding DeadlocksStackingForPyanadon, but loading a vanilla map, although that's likely incidental:
  61.642 Applying migration: Time Lapse Base Edition: tlbe-0.2.1.lua
  61.642 Applying migration: Time Lapse Base Edition: tlbe-1.0.0.lua
  61.642 Applying migration: Time Lapse Base Edition: tlbe.1.1.1.lua
  61.643 Applying migration: Time Lapse Base Edition: tlbe.1.2.0.lua
  61.643 Applying migration: Time Lapse Base Edition: tlbe.1.3.1.lua
  61.643 Applying migration: Time Lapse Base Edition: tlbe.1.4.2.lua
  61.643 Applying migration: Time Lapse Base Edition: tlbe.1.4.3.lua
  61.643 Applying migration: Time Lapse Base Edition: tlbe.1.4.4.lua
  61.643 Applying migration: Time Lapse Base Edition: tlbe.1.4.5.lua
  62.651 Error AppManagerStates.cpp:1662: Error while applying migration: Time Lapse Base Edition: tlbe.1.4.5.lua

__TLBE__/scripts/camera.lua:104: attempt to perform arithmetic on field 'transitionPeriod' (a nil value)
stack traceback:
	__TLBE__/scripts/camera.lua:104: in function 'updateConfig'
	__TLBE__/migrations/tlbe.1.4.5.lua:55: in main chunk

I haven't looked at the code yet -- I'm betting it is some inconsistency in the behaviour of the green box tracking to the white one.

I think it is similar to https://github.com/veger/TLBE/issues/55#issuecomment-1753181233, somehow the Camera is in an incorrect state, and then the updateConfig function has nil values which Lua cannot do maths with...
The Camera property zoomPeriod got renamed to transitionPeriod (see https://github.com/veger/TLBE/blob/master/migrations/tlbe.1.4.5.lua#L52C15-L52C15). This rename seems to be missing in your save file.

Weird. The same issue has not happened again, so I have no idea how to reproduce it. I guess we can leave this until someone else reports it or it happens in a controlled environment where we can fix it properly?

As mentioned it looks similar to #55 (if my deduction is correct, it is due to people running directly from code and thereby missing out on the (changed) migrations in between releases). I cannot see another path that results in the missing properties for the Camera. Within this controlled environment it is reproducible, but it becomes quite unlikely if there are more reports as I doubt lots of people are running 'in between' versions...
We can leave this issue open for a while to see if there are more reports coming in

Fixed in v1.5.1


fix: clone the producer plan and put logicalAnchor generated by Or_Expansion above logicalSink

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Always install ExamplePlugin on build_raven

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes #1489
What are the significant changes in functionality due to this change request?
Adds a line to ./build_raven that will always install ExamplePlugin when the script is run.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test CentOS 7 on 1d25842 : invalidated by @joshua-cogliati-inl
restarted civet

Is the "Refs.  #1489" supposed to close the issue? If so, can you edit the description to close the issue?

@alfoa Pretty much all the tests have passed on this if you want to give it another once over. Thanks!

Test OpenSUSE Leap 15  is currently offline and the IT is working in solving the issue
PR approved. Checklist passed. No email is needed since this is a crash of the installation but not wrong results can be produced


Failing to import night-owl-dark.jsonc?raw

What version of starlight are you using?
latest
What version of astro are you using?
4.3.7
What package manager are you using?
bun
What operating system are you using?
Linux
What browser are you using?
Any
Describe the Bug
When I run the project in dev, I'm getting this error from the image.
It doesn't break anything, just wondering if I should worry about it.

Link to Minimal Reproducible Example

Participation

[ ] I am willing to submit a pull request for this issue.

Worth mentioning I'm using SSR, here is my astro config:
import nodejs from '@astrojs/node'
import react from '@astrojs/react'
import starlight from '@astrojs/starlight'
import tailwind from '@astrojs/tailwind'
import { defineConfig, passthroughImageService } from 'astro/config'

export default defineConfig({
	output: 'server',
	adapter: nodejs({ mode: 'standalone' }),
	image: {
		service: passthroughImageService()
	},
	integrations: [
		react(),
		starlight({
			title: 'Trillian Docs'
		}),
		tailwind({
			applyBaseStyles: false
		})
	]
})

Hi @ronildo! Could you please share a minimal reproduction we can debug?
The best way to do this is to create a new StackBlitz and modify it so it exhibits the error you’re experiencing (e.g. adding SSR etc.)
Here’s a quick link to create a Starlight starter project on StackBlitz: https://astro.new/starlight-basics

I don't think that this actually is an issue we need to worry about. This is just a debug message coming from Astro, and afterwards Astro loads the same config with Vite, which apparently succeeds, otherwise your page wouldn't be working. :)

Ah, thanks @hippotastic! Ok, then closing as not a bug but something specific to how Bun logs warnings from Astro/Vite.

I'm not using Bun and this error is appearing still.
✘ [ERROR] No loader is configured for ".jsonc" files: node_modules/.pnpm/@astrojs+starlight@0.21.5_astro@4.5.17/node_modules/@astrojs/starlight/integrations/expressive-code/themes/night-owl-light.jsonc?raw

    node_modules/.pnpm/@astrojs+starlight@0.21.5_astro@4.5.17/node_modules/@astrojs/starlight/integrations/expressive-code/theming.ts:3:26:
      3 │ import nightOwlLight from './themes/night-owl-light.jsonc?raw';
        ╵                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

✘ [ERROR] No loader is configured for ".jsonc" files: node_modules/.pnpm/@astrojs+starlight@0.21.5_astro@4.5.17/node_modules/@astrojs/starlight/integrations/expressive-code/themes/night-owl-dark.jsonc?raw

    node_modules/.pnpm/@astrojs+starlight@0.21.5_astro@4.5.17/node_modules/@astrojs/starlight/integrations/expressive-code/theming.ts:2:25:
      2 │ import nightOwlDark from './themes/night-owl-dark.jsonc?raw';
        ╵                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

astro v4.5.17
@astrojs/starlight v0.21.5

Does the site still work, so just an error logged to the console? Have you enabled any flags regarding verbose logging?

Hi @hippotastic, the site does not work, since the client-side error page is shown (at least during development, I haven't tested astro build yet).
Here are the verbose logs: https://gist.github.com/aleclarson/9f5f474245720ec9fa452d89d1c5a34b

It seems that you are importing server-side code into a frontend file.
Can you share a link to your repo?

I'm trying to set up the following file structure:
docs/
├─ content/
│  ├─ .git/
│  ├─ reference/
├─ www/
│  ├─ .git/
│  ├─ astro.config.mjs

…with srcDir set to ../.
I assume this setup is not supported, so I'll try having content within www instead. This should be fine, since the main goal is to give the content its own git branch, away from the Astro stuff.

I'm trying to set up the following file structure:
docs/
├─ content/
│  ├─ .git/
│  ├─ reference/
├─ www/
│  ├─ .git/
│  ├─ astro.config.mjs

…with srcDir set to ../.
I assume this setup is not supported, so I'll try having content within www instead. This should be fine, since the main goal is to give the content its own git branch, away from the Astro stuff.

Are you using workspaces? This might be the issue, I have been having lots of issues like this... but I'm still able to build/server the app.

…with srcDir set to ../.

Ahh, I think this is the issue then! If your content is outside of the project root, this might lead to it not being processed by Vite, and therefore the special import suffixes powered by Vite (like ?raw) don't work.


Remove dependency on cross-fetch

Starting node 18 LTS, cross-fetch is no longer required given that global fetch is available by default.
Hence, the goal is to remove dependency on cross-fetch from utils repo and affected algokit repositories.

After recap of the issue report we found out that cross-fetch removal was already addressed in earlier releases. Hence awaiting for more details from @CiottiGiorgio to asses his original issue report

closing for now until further details on steps to replicate are provided. In such case will need to rename the issue title