Calendar UI not displaying correctly

Hello, first of all thank you for your time in creating Qalendar.
I am new to this and I have been unable to get the Calendar UI out correctly.

I have only been testing the Qalendar, following the scripts in the documentation. As such, I am a bit lost as to why the UI would not show up as expected. Here is my code:
  <Qalendar
    :selected-date="new Date(2022, 0, 8)"
    :events="events"
    :config="config"
  />
</template>

<script>
import { Qalendar } from "qalendar";
export default {
  components: {
    Qalendar,
  },
  data() {
    return {
      events: [
        {
          title: "Meeting with Dora",
          with: "Albert Einstein",
          time: { start: "2022-01-01 04:52", end: "2022-01-01 05:37" },
          color: "green",
          isEditable: true,
          id: "de471c78cb5c",
          description:
            "Think of me as Yoda.  Asperiores assumenda corporis doloremque et expedita molestias necessitatibus quam quas temporibus veritatis. Deserunt excepturi illum nobis perferendis praesentium repudiandae saepe sapiente voluptatem!",
        },
        {
          title: "Break",
          with: "Marshall Eriksen",
          time: { start: "2022-01-02 22:10", end: "2022-01-02 22:55" },
          colorScheme: "meetings",
          isEditable: true,
          id: "9f1b209982f1",
          location: "Zoom",
        },
      ],
      config: {
        defaultMode: "month",
        style: {
          colorSchemes: {
            meetings: {
              color: "#fff",
              backgroundColor: "#131313",
            },
            sports: {
              color: "#fff",
              backgroundColor: "#ff4081",
            },
          },
        },
        week: {
          // Takes the value 'sunday' or 'monday'
          // However, if startsOn is set to 'sunday' and nDays to 5, the week displayed will be Monday - Friday
          startsOn: "monday",
          // Takes the values 5 or 7.
          nDays: 7,
          // Scroll to a certain hour on mounting a week. Takes any value from 0 to 23.
          // This option is not compatible with the 'dayBoundaries'-option, and will simply be ignored if custom day boundaries are set.
          scrollToHour: 5,
        },
        month: {
          // Hide leading and trailing dates in the month view (defaults to true when not set)
          showTrailingAndLeadingDates: false,
        },
      },
    };
  },
};
</script>

<style scoped>
@import<EMAIL_ADDRESS></style>```

Hi @bryankwe. Glad to see you want to try out Qalendar. Two things:

you probably need to remove “scoped” from your style tag.
@import "qalendar/dist/style.css"; should be the shortest and preferred way of importing the Stylesheet

please let me know if this helps you

Thanks for your prompt response. It works... rookie mistake


Add filter for homepage flags

Only countries with at least 1 event which date is greater than or equal to 2014
are showed.
Flags for non-european countries still need to be added.

@michelesr Thank you!

We've got a failing test. Are you able to have a look at it?

Yeah, that is related to the fact i changed the list_countries() function to show only certains countries instead of all... i'm working on a hotfix...

Push forced right now, i cross my finger :+1:

Looks better! :) Pushing this live to see how it works.

Nice!

It is live now. We still need to add the missing flags as they show up on other places, too (e.g. http://events.codeweek.eu/scoreboard/) but for now we've patched up things.
@michelesr, thanks a lot for your help!

I'll see if i can patch up a filter in scoreboard.

Maybe we should just add the flags. I'll work on that later. I've found a package of flat flag icons.


Localization: French

We need a file and some french strings to use in the gui.

Implemented with https://github.com/msingr/csvGeom/pull/48


Is it possible to support elasticsearch 6.x?

Hi, is it possible to support elasticsearch 6,x? After 6.x version release, multiple types in the same index had been removed, so we will encounter the following error when we use "elastic" as backend with 6.x version.
Received Exception:
Error: elastic: Error 400 (Bad Request): Rejecting mapping update to [cayley] as the final mapping would have more than 1 type: [nodes, log] [type=illegal_argument_exception]
Many thanks....

Sure, we will support it.

Hi dennwc, thanks for your prompt reply. But i still encountered the same problem when connecting to elasticsearch 6.x.
Received Exception:
Error: elastic: Error 400 (Bad Request): Rejecting mapping update to [cayley_nodes] as the final mapping would have more than 1 type: [nodes, log] [type=illegal_argument_exception]
Many thanks....

@alvinh Sorry, I cannot reproduce. I'm testing it on ElasticSearch v6.2.4 (Docker image) and Cayley version v0.7.3. Make sure you updated to the latest version and in case it still doesn't work, please paste an output of cayley version.

Hi @dennwc, the output and config file are as below, thanks.
Cayley Output:
[root@m01 cayley_0.7.3_linux_amd64]# ./cayley http --host=<IP_ADDRESS>:64211 --config=cayley_elasticsearch_config.yml
I0424 17:25:25.802240  116372 cayley.go:63] Cayley version: 0.7.3 (782194b030b5170bbb0852c5e29f209e8012be37)
I0424 17:25:25.802372  116372 cayley.go:76] using config file: cayley_elasticsearch_config.yml
I0424 17:25:25.802454  116372 database.go:187] using backend "elastic" (http://<IP_ADDRESS>:9201)
Error: elastic: Error 400 (Bad Request): Rejecting mapping update to [cayley_nodes] as the final mapping would have more than 1 type: [nodes, log] [type=illegal_argument_exception]
Config File
store:
backend: elastic
address: "http://<IP_ADDRESS>:9201"
read_only: false
query:
timeout: 30s
load:
ignore_duplicates: false
ignore_missing: false
batch: 10000

Everything looks good, but it still tries to use an old code path. It might happen because of failed ES version detection. Let's try to debug it with your version of ElasticSearch. Please PM me on Slack.

Was a cluster misconfiguration issue


Car Steam Not Working

I installed AA 3.0 and Car Stream 1.8.3. Made the changes shown on Kiran's website and also tried the steps mentioned on the various threads here.  AA is working and shows the Car Stream button when I click the last icon on the right (looks like a small steering wheel), the player screen come on with a message to click the last icon to begin watching YouTube.  There is no YouTube option when selecting the icon. It only shows Car Stream and Google Music Player.
Any ideas how to make this work?

Android Auto 3.0 blocks custom apps.
See issue #116 for a fix.

Any idea what I am doing wrong?  I've tried multiple times.  The path and
apk name is correct.
On Wed, Mar 14, 2018 at 11:49 PM, Gabriele Rizzo<EMAIL_ADDRESS>wrote:

Android Auto 3.0 blocks custom apps.
See issue #116
https://github.com/thekirankumar/carstream-android-auto/issues/116 for
a fix.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thekirankumar/carstream-android-auto/issues/146#issuecomment-373093481,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ajo6EGg86VuDj6Iyu-6WMxXCatRxBEbRks5teUoIgaJpZM4SqVv1
.

--
Best Regards,
Scott E. Stufflebeam

Any idea what I am doing wrong?  I've tried multiple times.  The path and apk name is correct.
Error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell pm install -i "com.android.vending" -r \Phone\Download\youtube_auto_v1.8.3.apk
Error: failed to write; PhoneDownloadyoutube_auto_v1.8.3.apk (No such file or directory)

Use Windows Program instead. Much easier.
Anyway: what you did wrong is put \phone\ which is not a correct directory

Thank you.  I corrected the path but now get another error:
Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>\Minimal ADB and Fastboot>adb shell pm install -i "com.android.vending" -r \Download\youtube_auto_v1.8.3.apk
Access is denied.
C:\Program Files (x86)\Minimal ADB and Fastboot>\Minimal ADB and Fastboot>adb shell pm install -i "com.android.vending" -r \Download\youtube_auto_v1.8.3.apk
Access is denied.

That's still not a correct path.
Try \sdcard\Download\youtube_auto_v1.8.3.apk instead

The apk is on the internal phone storage.  I've confirmed the path through my windows explorer
Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell pm install -i "com.android.vending" -r \sdcard\Download\youtube_auto_v1.8.3.apk
Error: failed to write; sdcardDownloadyoutube_auto_v1.8.3.apk (No such file or directory)

Sorry I didn't even noticed you're using backslash. You should use normal slashes.
Anyway, internal storage in ADB's logic is /sdcard/

Got it.  Working now!  Thank you so much for your help.


Fix test procedure for NCF-187 bug.

To let it match procedure of 6a6e8c0, or it cannot reproduce this bug.
( especially backporting this bugfix patch to legacy version [<= <IP_ADDRESS>] in CentOS 7 )
btw the link of NCF-187 is broken, is there backup/mirror page to see full descriptions of this bug?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Test procedure

environment: CentOS Linux release 7.8.2003 (Core)

Download original source code of version <IP_ADDRESS> (Reason: CentOS 7 EPEL package is currently using it, and this is the last version the bug exists, next version is 4.4.0~)

manually patching nc_test4/tst_fills2.c part in https://github.com/Unidata/netcdf-c/commit/ab18a2e17cf8e6edcc660b410c844d0bbfa906e6

2a. manually patching nc_test4/tst_fillbug_187.c for reference

configure

configuraions
env LDFLAGS="-L/usr/lib64/hdf" ../configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-netcdf-4 --enable-dap --enable-extra-example-tests CPPFLAGS=-I/usr/include/hdf LIBS="-ldf -ljpeg" --enable-hdf4 --disable-dap-remote-tests

make && cd nc_test4 && make check

Before corrections of test procedure of NCF-187 (expected to fail but succeed)
============================================================================
Testsuite summary for netCDF <IP_ADDRESS>
============================================================================
# TOTAL: 58
# PASS:  58
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================

After corrections of test procedure of NCF-187 (expected to fail here)
============================================================================
Testsuite summary for netCDF <IP_ADDRESS>
============================================================================
# TOTAL: 58
# PASS:  57
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
============================================================================
See nc_test4/test-suite.log
Please report to<EMAIL_ADDRESS>============================================================================
make[2]: *** [test-suite.log] Error 1
make[2]: Leaving directory `/build/netcdf-c-<IP_ADDRESS>/build/nc_test4'
make[1]: *** [check-TESTS] Error 2
make[1]: Leaving directory `/build/netcdf-c-<IP_ADDRESS>/build/nc_test4'
make: *** [check-am] Error 2
[user@c5cac934419a nc_test4]$ cat test-suite.log
=============================================
   netCDF <IP_ADDRESS>: nc_test4/test-suite.log
=============================================

# TOTAL: 58
# PASS:  57
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tst_fills2
================

*** Testing fill values.
*** testing read of string record var with no data...ok.
*** testing read of string record var w/fill-value with no data...ok.
*** testing NULL fill values of a string var...ok.
*** testing non-empty fill values of a string var...ok.
*** testing read of string record var with no data...ok.
*** Testing fix for netCDF-4 fill-value bug...Sorry! Unexpected result, ../../nc_test4/tst_fills2.c, line: 378

It seems I need further check


fmt: pp should implement WriteString()

What version of Go are you using (go version)?
1.9beta1
What did you do?
In my code, I'm implementing fmt.Formatter.
In order to write a string to the fmt.State, I'm calling io.WriteString().
I know that this function has an optimization that allows to call WriteString() if w implements it.
Sadly, in my case the "real" type of fmt.State is fmt.pp.
fmt.pp only has Write().
What did you expect to see?
I think we should add:
func (p *pp) WriteString(s string) (ret int, err error) {
	p.buf.WriteString(s)
	return len(s), nil
}

in my case, it greatly improve performance and reduces memory allocation.
We could also implement WriteByte() and WriteRune(), since fmt.buffer has these methods.

Sounds reasonable.

I want to contribute to Go and noticed the Help Wanted label. If no one is working on it, I'd like to take it! :)

io.WriteString() uses a runtime check so it looks like it should work without changing the State Interface definition. For go2 we could then think about wether it makes sense to update the State Interface.
@nikhita go ahead if you want too. Please add<EMAIL_ADDRESS>and<EMAIL_ADDRESS>as reviewers. We can review before go1.10 but we can only submit when the code tree opens for go1.10 start of August.

@martisch will do that, thank you.

@SCKelemen

@nikhita
did you have time to start your first CL for go?
Any blockers encountered that we can help with?

@martisch
sorry, was busy at work - didn't have time to work on it.
But will try working on it on my flight to GopherCon now. :)
Maybe I can even ask any questions I have during the Go contributor workshop at GopherCon? :)

no problem. Asking at the contributor workshop sounds good.

Just checking if this is still active. I see in the CL that it needs tests. I can help with that, if need be.

I mailed another way on how to resolve this by. gopherbot will notice soon.

Adding WriteString makes some sense, but please let's not open up an internal type to the full pressure of external I/O interfaces.

Following up here instead of on the CL discussion.
I would also favor to leave the internal buffer methods unexposed and only implement WriteString on pp as the proposal suggested. As far as i know there has been not yet been data or a request to add more io methods beyond WriteString. Keeping the api footprint low imposes less constraints on internals for future changes and avoids needing to implement them explicitly on pp later if buffer is replaced by something with different interfaces for internal optimization.
If it is decided to expose all the io methods from the buffer it would be good to make sure that there are no regressions due to the compiler not optimizing all the overhead away for the internal use of those methods (e.g. due to inline budget changes).


Implementation of FindMeetingQuery.java

For my second commit, I am trying to create the Arrays.asList() outside the for loop, but keep running into errors. Does anything look off to you guys?

Forgot to hit the approval button.


Improve Team Developer Guide

Refer to the project collaboration notes for more details.
https://docs.google.com/document/d/1Dqr7jzMVZovSkf_vFGNBA7gyR892VFi_DE896cJoqeM/edit

Add the purpose of the guide, the target audience and include clear and complete information about how to use the guide. [JH]
Include clear and complete information on how to get started (e.g. installation instructions, operating systems, parts of the GUI, tutorial on how to use CLI) [Abdul]
Add proper signposting in the features section [Juay Hee]
Add proper signposting in the command summary section [XiaoTeng]
Amend UG to ensure that it is coherent [Pragya]


Flatten insomnia-libcurl package

Attempt to fix #923
On Windows, the installation paths can get long because of node_modules/insomnia-libcurl/node_modules/insomnia-node-libcurl/.... To get around Windows' 260 path length limit, this PR removes the insomnia-libcurl wrapper package and references insomnia-node-libcurl (shortened to inlc in a previous fix) directly.

May have missed on phone but worth updating flowtypes to the new shortened package name?
Nice fix 👍

Yes, we can do that in a separate PR, as the inlc package will have slightly different types than insomnia-libcurl did 😄


Error during docker compose up

Getting the below error during docker-compose up
vulnerability-assessment-tool/docker/rest-backend/conf/restbackend.properties: environment variable name 'vulas.backend.cveCache.refetchAllMs ' may not contain whitespace.
To Reproduce
Steps to reproduce the behavior:
Just go to docker folder and try to run docker-compose up --build as given in https://eclipse.github.io/steady/admin/tutorials/docker/.
Expected behavior
Check if the containers are up and running
Vulas version

Vulas 3.1.9

I was using a Mac. This was giving an issue on Mac but not on Linux. Anyways this needs a fix.


feat(dispatch-service): add retries for posting processing results

added an exponential backoff retry to the simulation run client to rertry failed http post calls.
it might be useful to later add conditions for the retires.
closes #3531

This is not where 502 errors have occurred. Errors have occurred in CompleteProcessor.

:tada: This PR is included in version 6.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Bug] Api version of client is outdated

Bug Type (问题类型)
exception / error (异常报错)
Before submit

[X] I had searched in the issues and found no similar issues.

Environment (环境信息)

Server Version: v1.5.0
Client Version: v1.0.0

Expected & Actual behavior (期望与实际表现)

The api version mismatch between client and server.
The bug is caused by the update of api version in server:
    public static final Version VERSION = Version.of(ApiVersion.class, "0.71");

While the api version is between 0.38-0.70 in client:

Vertex/Edge example (问题点 / 边数据举例)
No response
Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
No response

related pr: https://github.com/apache/incubator-hugegraph-toolchain/pull/542


docs(tile): add a11y tile docs to website

Reference #491
Make sure content matches: https://pages.github.ibm.com/IBMa/Carbon_Integration/Doc/Tile-doc.html

LGTM!


Break up Github::request

Github::request is currently 253 lines long.
But how should it be broken up?  I was thinking by moving it to be a function in a new request.rs file and then breaking it into smaller functions.  Ideally, these could make use of ? and Result to clean things up, but with things being futures perhaps that's not possible.
WDYT?

Triaging gh issues. Im still into this if you'd like to do this

I've moved on from Rust (no hard feelings at all, just shifted interests).
So I'll close it for lack of my own interests, but I understand if you want to reopen it for yourself.


FR-06032022-1 Enhancement to "schedule expire.in.days" filter

Is your feature request related to a problem?
Currently the tool allows to search for rules with schedules which expires in X amount of days ("less than" operand). Which means it is not possible to search for rules with schedules which expire after certain amount of days ("greater than" operand).
Describe the solution you'd like
Is it possible to change
expire.in.days X
into
expire.in.days = > < X
basically allow the user to choose the operand and then define the number of days
Describe alternatives you've considered
currently we have to export the resolved schedule values into excel, change the values into a Date format recognisable by Excel and then we can build a filter in Excel
Additional context
n/a

implemented with CR:
#515


Non-backward compatible definition of external CAD shapes

Reported by beutlich on 2 Jul 2013 07:32 UTC
Where it was in MSL 3.2
Additionally, external shapes are specified as DXF-files
(only 3-dim. Face is supported). External shapes must be
named "1", "2", ... "N". The corresponding definitions
should be in files "1.dxf", "2.dxf" etc.

it is now in MSL 3.2.1
Additionally, external shapes are specified with an URI name:
"modelica://<Modelica-name>/<relative-path-file-name>" or
"file://<absolute-file-name>"

SimulationX uses string to number conversion (atoi) to check if a shapeType string specifies a CAD file or not. This check always fails for MSL 3.2.1.
The new definition is by far cleaner as CAD file location can be specified anywhere and CAD format can be different from dxf. However since MSL 3.2.1 should be backward compatible to MSL 3.2 the old definition of external CAD shapes sould be added again and set to default for fullRobot.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1194

Comment by otter on 2 Jul 2013 15:35 UTC
Fixed in 3074c36dd7210eccc87829d4577f9b5ead71903b by correcting the documentation (re-adding "1", "2" .. as options).
In MSL 3.2.1, all external files, including the animation files, are referenced as URIs. This is still backwards compatible (models built with MSL 3.2 or 3.1 are still working). However, the new feature of URI support is used in MSL 3.2.1. Therefore, without URI support for animation CAD files in a tool, the CAD animation in the examples will no longer work.


Allow for automatic saving each N steps

This allows to launch a training and automatically save a model each N steps performed (to manually pick a specific model progress in time)

Appreciate the commit, but this code is a bit breakable. Thanks.

Appreciate the commit, but this code is a bit breakable. Thanks.

Ok then, It was a quick fix I did on my env to do that, and understand this is absolutely not the best way to do that.
How would you implement that in a cleaner way?

Ok then, It was a quick fix I did on my env to do that, and understand this is absolutely not the best way to do that.
How would you implement that in a cleaner way?

I don't think we need to save the model by steps, that doesn't make sense. we can just do a model.save after the model is fully trained.

I don't think we need to save the model by steps, that doesn't make sense. we can just do a model.save after the model is fully trained.

Ok, that is different.y purpose is to be able to pick a model in time, by choosing the best performance it had in a test run, that might not coincide with the best training run.
I'm still "new" to RL, but as I understand the same train/test logic used in supervised ML applies here, albeit with a much lower and non direct impact.
If instead this is not useful at all, just forget this PR :)

Ok, that is different.y purpose is to be able to pick a model in time, by choosing the best performance it had in a test run, that might not coincide with the best training run.
I'm still "new" to RL, but as I understand the same train/test logic used in supervised ML applies here, albeit with a much lower and non direct impact.
If instead this is not useful at all, just forget this PR :)

Hey @carlogrisetti, been reading through PR's and Issues and i don't think this is a dumb idea and infact a really good idea.
What if you're spending 4 weeks training a huge model on lower end hardware? One power outage or a trip on a cable and poof
What if you want to compare the last 50 generations?
There's lots of reasons to do this, did you find a cleaner way to implement saving training progress?


U-ADS Continuous Integration/Continuous Delivery (CI/CD)

Acceptance Criteria

Creation of an algorithm package from code, configs, etc
run automated tests agains packaged code
publish Algorithm Package to the Algorithm Catalog
Deployment diagram (e.g. what is needed for this to run, is it a per-tenant deployment, or shared across many tenants)
Deployed to Dev environment
Deployed to Test Environment

Zenhub epic, no longer needed


Showing what content is included in each social medium

First off, good job, it is really time saving library.
I noticed that there is mismatch in some social media; For example:
In Telegram, it is URL then description.
While, in Twitter, it is title then URL (and hashtags and twitter-user)
It might be good to show which data are supplied by each social medium, and also show how to customize that.
Thank you for your good work! :+1:

Hello @ibrahimBeladi, thank you for raising this issue, it's indeed an inconsistency issue. I fixed it in the latest version (v3.0.0-beta.4) and updated the README documentation with detailed attributes for each networks.


Fix MobX bug in DashCanvasModel.publishState()

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Closing -- Greg and I were unable to reproduce this, and it seems like the existing code should work fine.  Greg will keep his eyes peeled on this as he is currently working heavily on this dashboard.


C1W2A1-Creating-a-html-document

Hello
I have been trying to have a grade on this assignment for weeks even though i have the same code as yours but it keeps giving me grade error with grader feedback not available .. any suggestions??
This assignment:
https://github.com/greyhatguy007/meta-front-end-developer-professional-certificate/blob/main/C1-introduction-to-front-end-development/week2/C1W2A1-Creating-a-html-document/index.html

I'm sorry I don't understand you, you can realize the question that you are stumbling to solve so I can help you


Update scalafmt-core to 2.7.0

Updates org.scalameta:scalafmt-core from 2.6.4 to 2.7.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-minor

Codecov Report

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

@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   54.41%   54.41%
=======================================
  Files           1        1
  Lines          68       68
=======================================
  Hits           37       37
  Misses         31       31

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 d8c29dc...c1eccad. Read the comment docs.


JSDoc autogeneration not working?

VSCode Version: 1.10.1
OS Version: OSX Sierra

Behaviour of my VSCode doesn't match release notes
No @params are added to the generated block.

I'm unable to repo this with a simple exported function. Can you please share some source code that shows this problem?

Seeing slightly different issue. JSDoc markup is output however it is missing types.
This outputs:
/**
* @param name
*/

But this is expected:
/**
* @param {string} name
*/

@origin1tech That is by-design for TypeScript. See my comment about why this is the case. Basically, the TypeScript types are source of typing truth in TypeScript files, not jsdoc types

Thx @mjbvz yeah I honestly wondered that or gave that thought, but the example shows the types so it was a bit misleading.
wondering now how doc compilers will work with that for building out documentation sites.

Ah, okay. I've worked out what happened. This is not a bug.
I had this keybinding config:
    { "key": "enter", "command": "-acceptSelectedSuggestionOnEnter" },

And I was pressing Enter anyway... (Typically I press Tab while I'm coding, I guess I just didn't think about it here.) Apologies for the false report. I was thrown by the different newline handling for JSDoc:


Fixing default hostname

Coverage remained the same at 100.0% when pulling 0c1d379c445dc6b684b1f168a4bdda5fe9c1b8da on default-host into ee34f09be4b130897451d42169408b167388f664 on master.


How to keep the new created key space or table in Cassandra Docker container

Hi,
I build the new Cassandra Docker container and create a new key space and some tables, but these tables are lost after I restart (shutdown/start)  VM.
How to keep the new created key space or table in Cassandra Docker container?
BRs
Leo

I am having the same problem, I am not sure if volumes help in this case. Volumes can take care of files that are shared between the container and the OS but not with the tables. Do you guys have any other ideas for this issue?


update the chinese translation

Not sure that I can translate all post, lazy is the devil to me :(
Maybe I'll create PR again after finish all posts left.
Afraid to forgot it, so update 4 translated post for newer commit, and add translate for 05, that's all :)

wait ... what's wrong with zola, I need to install it and find why

Thanks a lot! Don't worry about the "zola check" errors, these are just some dead links that are probably unrelated to this PR.
cc @luojia65, @hi-rustin, @TheBegining : Do you have time to review this by any chance?

@liuyuran Thanks a lot for your work! I'll try my best to find someone to review this PR soon.

@liuyuran
Well done!
Just a suggestion about formatting: insert a space between Chinese words and English words.
-讨论了Linux、Windows和macOS中遇到的链接错误
+讨论了 Linux、Windows 和 macOS 中遇到的链接错误

Examples:
-中文English中文
+中文 English 中文

-中文`code`中文
+中文 `code` 中文

-中文English。
+中文 English。

-中文`code`。
+中文 `code`。

-中文[link]中文
+中文 [link] 中文

@liuyuran Thanks a lot for your work! I'll try my best to find someone to review this PR soon.
If someone who speaks Chinese is reading this: It would be great if you could give this PR (or parts of it) a quick review! Thanks!

i would like to do this

@zjp-CN @JiangengDong
thanks for review! I'll try to fix that quickly (a little busy these days, so ... just as possible).
@onion108
Feel free lol, everyone can review it if you want because there is github (:з)∠)

above fixed, and need say something for why some place not changed

problem about white space between chinese char and english char happend in too many place ... please have mercy on me
中断堆栈符表 and ....符表 is a keyword ( not sure how to say by english, by chinese , I call it 约定俗成的组合词汇 ), and has used in too much place, such as 特权堆栈符表
about white space line, you know, these posts maybe changed some days later by someone, so I prefer to use line to line (though have some offset of line code from head part) that can compare between .zh-CN.md and .md easier.

Thanks for the update! Some follow-up discussion:

I am afraid that “符表” is not a phrase. The correspondence between "interrupt descriptor table" and “中断描述符表” is as follows:

interrupt: 中断
descriptor: 描述符
table: 表

For a similar reason, I would doubt whether "interrupt stack table" could be translated into ”中断堆栈表“, since there is no "heap" in the original English word. I completely understand that “堆栈” and “栈” can be used interchangeably most of the time, but for kernel-related documentation, it is better to be careful and avoid ambiguity.
Here https://github.com/phil-opp/blog_os/pull/1131#discussion_r990730067 the "side effect" means “副作用” instead of “边际效应”.

Thanks for the update! Some follow-up discussion:

I am afraid that “符表” is not a phrase. The correspondence between "interrupt descriptor table" and “中断描述符表” is as follows:

interrupt: 中断
descriptor: 描述符
table: 表

For a similar reason, I would doubt whether "interrupt stack table" could be translated into ”中断堆栈表“, since there is no "heap" in the original English word. I completely understand that “堆栈” and “栈” can be used interchangeably most of the time, but for kernel-related documentation, it is better to be careful and avoid ambiguity.

Here update the chinese translation #1131 (comment) the "side effect" means “副作用” instead of “边际效应”.

┭┮﹏┭┮
So that's how it is, I was wrong to think 中断 | 描述 | 符表 is the correct result of word segmentation.
You are right ... I'll fix these mistakes in next commit.

@liuyuran Thanks for all your work on this and thanks everyone for reviewing! Please let me know when you think the PR is ready to be merged.

@liuyuran Thanks for all your work on this and thanks everyone for reviewing! Please let me know when you think the PR is ready to be merged.

@phil-opp Sure, have ready for merge if no more review needed :)

Looks like @JiangengDong did a detailed review up to post-05. So I guess the following files still need a review?

[ ] blog/content/edition-2/posts/06-double-faults/index.zh-CN.md
[ ] blog/content/edition-2/posts/07-hardware-interrupts/index.zh-CN.md
[ ] blog/content/edition-2/posts/08-paging-introduction/index.zh-CN.md

@willser You already left a suggestion for this post, did you proof-read the whole post?

Well, I might be late to the party since I just translated almost half of the blog post 8 and saw this pull request...
Anyways, I'll try to provide my two cents on the translation.
By the way, since I am planning to do post-12, @liuyuran are you doing other blog posts too?

Well, I might be late to the party since I just translated almost half of the blog post 8 and saw this pull request...
Anyways, I'll try to provide my two cents on the translation.
By the way, since I am planning to do post-12, @liuyuran are you doing other blog posts too?

@Byacrya no plan for that, because of I think that I'll very busy next week :(

Thx for ur pr! And I think it can be combined with this repository.https://github.com/rustcc/writing-an-os-in-rust

Thanks @JiangengDong and @Byacrya for your reviews! It looks like this PR is ready to be merged, or do you have any other things that you would like to see improved?
@liuyuran Thank you again for all your work on this! I pushed two commits to this PR to acknowledge all the people that contributed to this. I hope that's ok and that I did not forget anyore.

Ok, looks like there are no further comments. Let's get this merged then! :tada:


Consider using GitHub releases for releases

Many thanks for providing a block module! We just stumbled over it and consider using it in our projects.
However, once we use it in production it would be good to know what changes are done between releases and what we might need to do when upgrading the module.
Please consider doing releases view GitHub releases, so you can add some text describing the changes. This way its also more easy to follow the project.

Hello and thank you for your interest in this module.
Does this correspond to your request?
Best regards
https://github.com/TeamEver/everblock/releases/tag/V4.4.2

Good morning
This issue being open and currently unanswered, it is now closed
Do not hesitate to recreate an issue if your concern is not resolved by detailing the problem encountered
Best regards


Some @Param values can not be converted to target type: "CUCKOO8_4" can not be converted to org.minperf.bloom.Filter.Type

I would like to test the minperf API but when I clone the project and open it, I have an error like Some @Param values cannot be converted to target type: "CUCKOO8_4" cannot be converted to org.minperf.bloom.Filter.Type.
Please, How to solve this problem and compile the API?

Should be resolved now, could you check?

Thank you so much . My problem is solved.


Improved Search Bar

Title : Improve Search Bar
Issue : #211
Currently :

drop down showing correct results.
When the items in the drop down are clicked, the user is redirected to that solver.
When the exit(x) sign is pressed in the search bar, all the solvers are showing.

Video :
screen-capture.webm

Great Job!


Cleanup filesystem code

I made some simplifications to the filesystem initialization code. You may want to double check the Windows portion. In particular, make sure that multiple trailing directory separators really are safely ignored on Windows.
Hopefully this cleanup will make it easier to address upgrading to the newer simpler methods in the more recent versions of Physfs.

Reviewed the commits, they look good to me for the most part though I did note a couple of questions.
I'm reevaluating the init code for the FS and ... it could really use an overhaul especially with PhysicsFS having deprecated a number of functions that FileSystem still uses. Not sure if I should slate for a 1.5.0 release or later.

I'm afraid the review approvals on GitHub don't say which commit(s) you were viewing. I've encountered that limitation myself. As such, I'm a little uncertain what the comments pertain to.
Sometimes while reviewing, I have used a workflow where I examine each commit on it's own in a separate tab, occasionally making annotated code comments. The annotated code comment ties the comment to a commit, and a particular block of code (I aim for the bottom of the block since the preview includes lines above). One annoyance about the GitHub interface, is the first comment for each commit (in a new tab) has the button labelled "Start a review", rather than "Add review comment". It doesn't matter though, you can keep "starting a review", making comments, closing pages, opening new pages, starting new reviews, adding more comments, and then finally collect them all into a single review at the end. GitHub will remember all the comments you were making. For the final review, I like to open a review window that shows all commits. I find if I don't do that, GitHub doesn't accurately track that you've viewed everything, and can list your review as only pertaining to earlier commits. It affects the changes since you last viewed button. It may also impact where the comments appear in the PR timeline. In the final overall review window, I'll add any summary I need to, and either comment or approve all changes together.


Page Layouts: Keyboard Navigation

Summary
Gives users the ability to use keyboard arrows to navigate through page layouts.
Relevant Technical Choices

forwards ref to pageLayout to control focus with arrows in pageLayouts
added prop isFocused in pageLayout tells us if the keyboard is in use and if it is we stop propagation on events that need to not bubble up to pageLayouts (keyUp, focus, blur).
Reference isRTL from useConfig to decide which way arrow nav should go.
PageLayouts gets 2 new refs - pageRefs (object) of refs holding all available pages to focus on and containerRef which is used for the useFocusOut hook to reset keyboard nav state.
This doesn't look as similar to other places hijacking the nav for arrows because we're using a virtualized list.

To-do
I cannot figure out how to get the dialog to focus from keyboard - i can't add a ref anywhere to the dialog that is set up in time for a hook to grab it and focus and the button does not have the ability to forward a ref. Has anyone had to do this with the editor and want to lend a hand?
There's also an issue of if you tab out of the page layouts and you're focused on the actual story page, if you don't first hit 'escape' before 'shift+ tab' focus isn't released from the story page - this feels entirely out of the wheelhouse of this ticket but I wanted to mention it as an edge case just incase there's something I'm unaware of that can prevent this given all of the focus control that occurs in the editor.
User-facing changes
Only visible if page layouts experiment is true.
If it is true, then this gives users the ability to navigate through page layouts with arrow keys. You can tab into the page layouts like media and then use arrows to go through them, hitting tab again will move you out of the page layouts.
Testing Instructions
You can tab into the page layouts like media and then use arrows to go through them, hitting tab again will move you out of the page layouts.  (If you hit 'enter' the focus doesn't shift to the dialog, I've been trying to get that to work for the better part of the afternoon.)

Addresses #5876

@googlebot I consent.

@googlebot I consent.

@zachhale when you get a sec - will you consent for the google bot so that when this is good to go we're not blocked by the bot?

@zachhale when you get a sec - will you consent for the google bot so that when this is good to go we're not blocked by the bot?

@googlebot I consent.
On Tue, Jan 12, 2021 at 6:59 PM Brittany Feenstra<EMAIL_ADDRESS>wrote:

@zachhale https://github.com/zachhale when you get a sec - will you
consent for the google bot so that when this is good to go we're not
blocked by the bot?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/web-stories-wp/pull/5915#issuecomment-759171609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAA6HN4PZMBLPQBXE2PBULSZUEADANCNFSM4WAB6PFA
.

@googlebot I consent.
On Tue, Jan 12, 2021 at 6:59 PM Brittany Feenstra<EMAIL_ADDRESS>wrote:

@zachhale https://github.com/zachhale when you get a sec - will you
consent for the google bot so that when this is good to go we're not
blocked by the bot?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/web-stories-wp/pull/5915#issuecomment-759171609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAA6HN4PZMBLPQBXE2PBULSZUEADANCNFSM4WAB6PFA
.


Where is dead_reckoner ?

Hi!
Where can I find the node dead_reckoner mentioned in the overview?

dead_reckoner mainly uses an IMU sensor to predict the next-frame position of the ego-vehicle and also interpolate the result of lidar_localizer and gnss_localizer.

Many thanks

I am looking for this package too. @jokla, Did you find it? Thanks.

Thanks for using Autoware and for your question. However the issue tracker is for posting confirmed bugs and feature requests.
We ask that you please ask questions on the Autoware Discourse category following our support guidelines: https://github.com/CPFL/Autoware/wiki/Support-guidelines. Please pay particular attention to the information we ask you to provide.


Method to wait for vm status ready

Duplicate vm wait_for_status method in order to give it a more appropriate name. Original method will be removed/refactored in a future PR.

!verify

!verified

!cherry-pick v4.12


Distributed generation eia861

Here's the data for the distributed generation tables with a few small changes to the utility data tables.
This PR also contains changes to the extract module to address the strange -1 column problem.

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

See the complete overview on Codacy


Currency Converter App

Create each of the folders and files from you text/code editor respectively, then, Copy and paste the files into your project respectively.
Note: The exchange rate API key must be generated by you else, it won't work.
All you need to do is to head over to your search bar and search for exchange rate API, Signup for free account and request for an API key. And you would be generated with a unique API key then, head back to your code in your index.js files locate the exchange rate API link,. All you need to update is the API key generated from the exchange rate API website replace it to the one in the code you copied and you are good to go.


FPS testing does not work as described in the documentation

Hello everyone,
Firstly, I apologize for my English.
I have a problem: I trained a custom object detector, and for my use case, the Frames Per Second (FPS) is crucial. I used the following command:
!python -m torch.distributed.launch --nproc_per_node=1 --master_port=29500 tools/analysis_tools/benchmark.py /content/mmdetection/configs/ursa/CustomConfigFasterRcnn50.py /content/mmdetection/work_dirs/faster-rcnn_r50_fpn_2x_coco/epoch_25.pth --launcher pytorch
Unfortunately, the command did not run properly. Instead, an error occurred, and I am unable to fix it. Maybe someone knows where the error is coming from.
/usr/local/lib/python3.10/dist-packages/torch/distributed/launch.py:181: FutureWarning: The module torch.distributed.launch is deprecated
and will be removed in future. Use torchrun.
Note that --use-env is set by default in torchrun.
If your script expects --local-rank argument to be set, please
change it to read from os.environ['LOCAL_RANK'] instead. See
https://pytorch.org/docs/stable/distributed.html#launch-utility for
further instructions
warnings.warn(
usage: benchmark.py [-h] [--checkpoint CHECKPOINT] [--task {inference,dataloader,dataset}]
[--repeat-num REPEAT_NUM] [--max-iter MAX_ITER] [--log-interval LOG_INTERVAL]
[--num-warmup NUM_WARMUP] [--fuse-conv-bn] [--dataset-type {train,val,test}]
[--work-dir WORK_DIR] [--cfg-options CFG_OPTIONS [CFG_OPTIONS ...]]
[--launcher {none,pytorch,slurm,mpi}] [--local_rank LOCAL_RANK]
config
benchmark.py: error: unrecognized arguments: --local-rank=0 /content/mmdetection/work_dirs/faster-rcnn_r50_fpn_2x_coco_Vanilladata_Standcofig/epoch_25.pth
[2024-02-18 10:12:19,373] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: 2) local_rank: 0 (pid: 40420) of binary: /usr/bin/python3
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.10/dist-packages/torch/distributed/launch.py", line 196, in
main()
File "/usr/local/lib/python3.10/dist-packages/torch/distributed/launch.py", line 192, in main
launch(args)
File "/usr/local/lib/python3.10/dist-packages/torch/distributed/launch.py", line 177, in launch
run(args)
File "/usr/local/lib/python3.10/dist-packages/torch/distributed/run.py", line 797, in run
elastic_launch(
File "/usr/local/lib/python3.10/dist-packages/torch/distributed/launcher/api.py", line 134, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/usr/local/lib/python3.10/dist-packages/torch/distributed/launcher/api.py", line 264, in launch_agent
raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
tools/analysis_tools/benchmark.py FAILED
Failures:
<NO_OTHER_FAILURES>
Root Cause (first observed failure):
[0]:
time      : 2024-02-18_10:12:19
host      : 4c4ef013f9fc
rank      : 0 (local_rank: 0)
exitcode  : 2 (pid: 40420)
error_file: <N/A>
traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
Are these issues already known?
I really appreciate any help you can provide.

hello,i met the same problem,but anyone can fix it?

same problem

mmdet3.3 我的改这种形式应该就行了
python  tools/analysis_tools/benchmark.py /content/mmdetection/configs/ursa/CustomConfigFasterRcnn50.py /content/mmdetection/work_dirs/faster-rcnn_r50_fpn_2x_coco/epoch_25.pth


services.plasma5: Make activationscript use absolute path to

kbuildsyscoca5
Motivation for this change
cc: @nand0p
Things done

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

[ ] 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"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Failure on x86_64-linux (full log)
Attempted: tests.plasma5
Partial log (click to expand)
building '/nix/store/ib52bc4n7r4xkpdc92m3r85fsqj0q7xa-xkb-validated.drv'...
building '/nix/store/n1vxqpn3rh80cvppj9id8zwlahp4vqvq-xscreensaver.pam.drv'...
cannot build derivation '/nix/store/fdj35z0pzb9q1g33dkmjygfn05qrc5qp-etc.drv': 15 dependencies couldn't be built
cannot build derivation '/nix/store/ln1d7pwx59p3h7l2jwaavwygrn2qk5mg-nixos-system-machine-18.09.git.86fd9aa.drv': 12 dependencies couldn't be built
cannot build derivation '/nix/store/85v1njp49hx8f9s169ink0fg3zl05r4r-closure-info.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/m0fqskhvl82xhl6r9c899ra5cg80b9v1-run-nixos-vm.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/vqqq70vyzzzp2h6cwzay5xcvc4v3a3av-nixos-vm.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/aik6w7xp29sr2rc9nmkc08m8r6l106dy-nixos-test-driver-plasma5.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/c2i0jpqg15imkqz7kd2kbvcgcj2avbvs-vm-test-run-plasma5.drv': 1 dependencies couldn't be built
error: build of '/nix/store/c2i0jpqg15imkqz7kd2kbvcgcj2avbvs-vm-test-run-plasma5.drv' failed

Failure on aarch64-linux (full log)
Attempted: tests.plasma5
Partial log (click to expand)
cannot build derivation '/nix/store/37sjk73dkj64y52rs5yv3jxwqrc6da6v-system-units.drv': 3 dependencies couldn't be built
Checking that all programs called by absolute paths in udev rules exist... OK
cannot build derivation '/nix/store/lshrzdjh6mr2dhyylhlf91cqqvmkr09p-etc.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/pfgar7xs2s8qy8wx1wyz396bx337saqb-nixos-system-machine-18.09.git.7d79b7d.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/38f54d77v4i9xdsxipv9i9fjym8vx6qb-closure-info.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/ky8djsnh115aykh4wza11917567ryk7l-run-nixos-vm.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/0x8vd2i884dia7jaa08ijwkg148jxzh5-nixos-vm.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/klgpclyfaifcfab12bjd8si350jh8cfx-nixos-test-driver-plasma5.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/m750f9a6r08aj47912lb1xw25n07ss0a-vm-test-run-plasma5.drv': 1 dependencies couldn't be built
error: build of '/nix/store/m750f9a6r08aj47912lb1xw25n07ss0a-vm-test-run-plasma5.drv' failed


Spherical Calculations Bug - Coordinate Transposition

I made a note of some issues with the Spherical Calculations in https://github.com/duckdb/duckdb_spatial/issues/16#issuecomment-2221171749 that were corroborated by several other uses or not, but not sure if they got noticed or not, so figured I would make a separate issue.
In short, ST_AREA_SPHEROID and related functions seem to have a bug with lat/lng coordinate  transposition - any coordinate with a longitude < -90 (so, the western portion of the US) returns NaN when using one of those functions.
See https://github.com/duckdb/duckdb_spatial/issues/16#issuecomment-2226391634 for a visual:

I replied in #16


Support Solaris.

Related: https://github.com/dmlc/xgboost/issues/6542
I ran a test on https://builder.r-hub.io/ mentioned by @hcho3 .  The rabit issue is fixed, but the toolchain itself on the test machine seems a bit weird.
os: Oracle Solaris 10, x86, 32 bit, R-release.  A snippet of log is copied here, complete log is uploaded at the end.
./dmlc-core/include/dmlc/./base.h:207:65: note: #pragma message: Warning: FILE OFFSET BITS defined to be 32 bit
 #pragma message("Warning: FILE OFFSET BITS defined to be 32 bit")
                                                                 ^
In file included from /opt/csw/include/c++/5.5.0/tr1/random:46:0,
                 from /opt/csw/include/c++/5.5.0/parallel/random_number.h:36,
                 from /opt/csw/include/c++/5.5.0/parallel/partition.h:38,
                 from /opt/csw/include/c++/5.5.0/parallel/quicksort.h:36,
                 from /opt/csw/include/c++/5.5.0/parallel/sort.h:48,
                 from /opt/csw/include/c++/5.5.0/parallel/algo.h:45,
                 from /opt/csw/include/c++/5.5.0/parallel/algorithm:37,
                 from ./include/xgboost/base.h:59,
                 from ./include/xgboost/logging.h:14,
                 from xgboost_custom.cc:5:
/opt/csw/include/c++/5.5.0/tr1/cmath: In function ‘float std::tr1::acosh(float)’:
/opt/csw/include/c++/5.5.0/tr1/cmath:424:18: error: ‘float std::tr1::acosh(float)’ conflicts with a previous declaration
   acosh(float __x)
                  ^
In file included from /opt/csw/lib/gcc/i386-pc-solaris2.10/5.5.0/include-fixed/math.h:23:0,
                 from /opt/csw/include/c++/5.5.0/cmath:44,
                 from ./include/xgboost/base.h:11,
                 from ./include/xgboost/logging.h:14,
                 from xgboost_custom.cc:5:
/usr/include/iso/math_c99.h:754:15: note: previous declaration ‘float std::acosh(float)’
  inline float acosh(float __X) { return __acoshf(__X); }
               ^
In file included from /opt/csw/include/c++/5.5.0/tr1/random:46:0,
                 from /opt/csw/include/c++/5.5.0/parallel/random_number.h:36,
                 from /opt/csw/include/c++/5.5.0/parallel/partition.h:38,
                 from /opt/csw/include/c++/5.5.0/parallel/quicksort.h:36,
                 from /opt/csw/include/c++/5.5.0/parallel/sort.h:48,
                 from /opt/csw/include/c++/5.5.0/parallel/algo.h:45,
                 from /opt/csw/include/c++/5.5.0/parallel/algorithm:37,
                 from ./include/xgboost/base.h:59,
                 from ./include/xgboost/logging.h:14,
                 from xgboost_custom.cc:5:
/opt/csw/include/c++/5.5.0/tr1/cmath: In function ‘long double std::tr1::acosh(long double)’:
/opt/csw/include/c++/5.5.0/tr1/cmath:428:24: error: ‘long double std::tr1::acosh(long double)’ conflicts with a previous declaration
   acosh(long double __x)
                        ^
In file included from /opt/csw/lib/gcc/i386-pc-solaris2.10/5.5.0/include-fixed/math.h:23:0,
                 from /opt/csw/include/c++/5.5.0/cmath:44,
                 from ./include/xgboost/base.h:11,
                 from ./include/xgboost/logging.h:14,
                 from xgboost_custom.cc:5:
/usr/include/iso/math_c99.h:796:21: note: previous declaration ‘long double std::acosh(long double)’
  inline long double acosh(long double __X) { return __acoshl(__X); }

log.zip

This line is pulling in TR1, which is likely the culprit of the error:
https://github.com/dmlc/xgboost/blob/b2246ae7eff090bd1431f3854c99a8ca12782a98/include/xgboost/base.h#L57-L59
I will try to patch that line and re-submit to r-hub.

This line is pulling in TR1, which is likely the culprit of the error:
https://github.com/dmlc/xgboost/blob/b2246ae7eff090bd1431f3854c99a8ca12782a98/include/xgboost/base.h#L57-L59
I will try to patch that line and re-submit to r-hub.

Let's backport this patch to the release_1.3.0 branch as well.

Let's backport this patch to the release_1.3.0 branch as well.

After the patch, XGBoost built successfully on R-Hub Solaris:

Awesome!

Let's backport this patch to the release_1.3.0 branch as well.

Will list it.

After the patch, XGBoost built successfully on R-Hub Solaris:

Awesome!

Let's backport this patch to the release_1.3.0 branch as well.

Will list it.

Codecov Report

Merging #6578 (2a20e66) into master (b2246ae) will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6578      +/-   ##
==========================================
+ Coverage   80.10%   80.16%   +0.05%
==========================================
  Files          13       13
  Lines        3604     3604
==========================================
+ Hits         2887     2889       +2
+ Misses        717      715       -2

Impacted Files
Coverage Δ

python-package/xgboost/tracker.py
93.98% <0.00%> (-1.13%)
:arrow_down:

python-package/xgboost/dask.py
81.38% <0.00%> (+0.84%)
: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 b2246ae...5857804. Read the comment docs.

Codecov Report

Merging #6578 (2a20e66) into master (b2246ae) will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6578      +/-   ##
==========================================
+ Coverage   80.10%   80.16%   +0.05%
==========================================
  Files          13       13
  Lines        3604     3604
==========================================
+ Hits         2887     2889       +2
+ Misses        717      715       -2

Impacted Files
Coverage Δ

python-package/xgboost/tracker.py
93.98% <0.00%> (-1.13%)
:arrow_down:

python-package/xgboost/dask.py
81.38% <0.00%> (+0.84%)
: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 b2246ae...5857804. Read the comment docs.


Ignore sigpipe to prevent SIGPIPE in CloudSQLite which crashes the process

A couple of years ago we added Curlopt_nosignal to the requests sent by cloudsqlite (See forum post for more details. Shortly after we had SQLite team ignore SIGPIPE in the daemon because we were experiencing 141 exit codes in the daemon. 141 exit code is SIGPIPE.
Recently the hub team has been experiencing 141 exits in their v2 checkpoint creation job see ticket I created on their behalf.
SQLite team suggests signal(Sigpipe, sig_ign), so I've copied the way he did it in this commit.
No idea why we are suddenly experiencing this. Would appreciate any feedback on the appropriate place to put this line of code.

@mergifyio backport release/4.10.x


change(ci): remove Windows support

Motivation
We can no longer support Windows, see https://github.com/ZcashFoundation/zebra/discussions/3704
Specifications

Designs

Solution
Remove Windows testing from CI
Review
Not super urgent, but this blocks https://github.com/ZcashFoundation/zebra/pull/3799
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work

My only comment would be if we can add a TODO to those comments, as it's visual and easier for follow up for things pending to solve in the future.

@gustavovalverde  Added them in 5a511c8b9

Did you want to update these docs in this PR, or open a ticket or another PR?

https://github.com/ZcashFoundation/zebra/blob/main/book/src/dev/alpha-release-criteria.md

https://github.com/ZcashFoundation/zebra/blob/main/README.md

update supported platforms, add link to Windows issue in known issues

https://github.com/ZcashFoundation/zebra/blob/main/book/src/user/requirements.md

@teor2345 Ah, thanks for the reminder. I changed them in 5a511c8b9. I didn't change the alpha-release-criteria.md since we're in beta now (maybe we should create one for beta?).

I didn't change the alpha-release-criteria.md since we're in beta now (maybe we should create one for beta?).

Sounds like something for a ticket, or something we might do as part of:

#2372
docs for the stable release

@mergifyio refresh

I removed the Windows tests from the list of required jobs in GitHub settings.

This job needs a manual merge, because it changes Mergify rules.


plotjuggler: 3.3.4-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository plotjuggler to 3.3.4-1:

upstream repository: https://github.com/facontidavide/PlotJuggler.git
release repository: https://github.com/facontidavide/plotjuggler-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.7
previous version for package: 3.3.2-1

plotjuggler
* Video plugin (#574 <https://github.com/facontidavide/PlotJuggler/issues/574>)
* gitignore *.swp files (#569 <https://github.com/facontidavide/PlotJuggler/issues/569>)
* Added libprotoc-dev to the apt install targets (#573 <https://github.com/facontidavide/PlotJuggler/issues/573>)
* turn on Sol3 safety flag
* trying to solve reported issue with Lua
* add fields that were not set in Protobuf
* Protobuf update (#568 <https://github.com/facontidavide/PlotJuggler/issues/568>)
* add zoomOut after loadDataFile
* Protobuf options refactored
* changed the protobuf implementation to deal with dependencies
* Protobuf parser and MQTT plugins
* Merge pull request #531 <https://github.com/facontidavide/PlotJuggler/issues/531> from erickisos/fix/517
  Homebrew path added into CMakeLists #517 <https://github.com/facontidavide/PlotJuggler/issues/517>
* LUA version updated
* fix dependency between transformed series
* fix issue #557 <https://github.com/facontidavide/PlotJuggler/issues/557>
* Homebrew path added into CMakeLists
* Contributors: Adeeb Shihadeh, Davide Faconti, Erick G. Islas-Osuna, Miklós Márton

It looks like the source branch for this repository needs to be updated. The CI is failing:
Could not validate source entry for repo plotjuggler with error [[[Could not validate repository with url https://github.com/facontidavide/PlotJuggler.git and version foxy from entry at line 2180. Error reason: No branch found matching foxy]]]

@cottsay the branch is main and the URL is correct. I am not sure what I am supposed to do here, since the URL is correct

I am not sure what I am supposed to do here

You can update this PR with the correct branch.

@facontidavide Lines 2183 and 2174 should be changed to main from foxy.


Minor update of syntax files

Add ‘Enable’ and ‘Download-Upgradeable-Packages-Debdelta’
to file runtime/syntax/aptconf.vim
Add ‘colored-stats’ and ‘show-mode-in-prompt’
to file runtime/syntax/readline.vim

Please first contact the maintainers of the appropriate syntax files. They will send updated files to Bram for inclusion. when they don't react, please contact vim-dev ml

For runtime/syntax/readline.vim
Well, I've been in touch with Nikolai and last I heard, he didn't have enough time to continue maintaining it anymore, so he asked me to send my changes, which is what I just did and whether I would like to take maintainership of it. I’m ok with that, just not sure how to do so.
For runtime/syntax/aptconf.vim
The e-mail has been sent, just waiting for the reply.

Hi rbazaud!
On So, 25 Okt 2015, rbazaud wrote:

For runtime/syntax/readline.vim
Well, I've been in touch with Nikolai and last I heard, he didn't have enough time to continue maintaining it anymore, so he asked me to send my changes, which is what I just did and whether I would like to take maintainership of it. I’m ok with that, just not sure how to do so.

If you want to take maintainership, make your changes, edit the header
and put yourself as the maintainer, moving Nikolai to the Previous
Maintainer and then send the complete file for inclusion with Vim and
refer to this thread.
Best,
Christian
Das sichere Zeichen des beginnenden Alters ist, daß man geschwind
noch einige Jugendtorheiten begeht.
-- Anonym

Hi Christian, thanks for the information. I’ve sent the file readline.vim to Bram, with Nikolai in cc (I’d have put you as well but I don’t have your e-mail address). I’ve committed the change of maintainer name and squashed the commit.

rbazaud wrote:

Add ‘Enable’ and ‘Download-Upgradeable-Packages-Debdelta’
to file runtime/syntax/aptconf.vim
Add ‘colored-stats’ and ‘show-mode-in-prompt’
to file runtime/syntax/readline.vim
You can view, comment on, or merge this pull request online at:
https://github.com/vim/vim/pull/462
-- Commit Summary --

Minor update of syntax files

-- File Changes --
M runtime/syntax/aptconf.vim (8)
M runtime/syntax/readline.vim (4)

Can you please add your full name to the github account?
I have no idea who "rbazaud" is.
I prefer the updated files to be emailed, so that I have a history of
where something is coming from.
--
Q: What is a patch 22?
A: A patch you need to include to make it possible to include patches.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

My profile has been updated as requested, that said my full name is in every one of my commits and it was also accessible one click after the page refered to in a previous message. It is also in the file sent by e-mail.
The proposition has been sent by e-mail as well (same as the pull request which passed successfully every integration test as it's not code stricto sensu). Never got any reply from the supposed aptconf.vim maintainer, which isn't very surprising in itself (I’ve given a possible explanation by e-mail).

Has this file been included yet?

I don't think so.
2016-05-19 17:25 GMT+02:00 Christian Brabandt<EMAIL_ADDRESS>
Has this file been included yet?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/vim/vim/pull/462#issuecomment-220359625

--
Raphaël Bazaud

It seems that they are all included. Closing.


Adding Vault and Secrets to our ansible scripts

WIP
This will likely end up being a major PR, that adds secrets to our ansible scripts, adjusting how our inventory files and playbooks are organized in the process.
At the moment, it introduces an inventories dir, organized around our services or concerns (right now, using the notification service as an example).  Within each concern is an inventory file and the group vars related to it, with the group_vars organized by the same groupings as the inventory file.
For example, we have the dir inventories/notifications_service organized like so:
inventories/notifications_service
├── group_vars
│   ├── all
│   │   ├── vars.yml
│   │   └── vault.yml
│   ├── development
│   │   ├── vars.yml
│   │   └── vault.yml
│   └── production
│       ├── vars.yml
│       └── vault.yml
└── inventory.yml

and the inventory.yml in that dir is structured as:
---
notifications_service:
  hosts:
   notifications.nos.social:
   dev-notifications.nos.social:
  children:
    production:
      hosts:
        notifications.nos.social:
    development:
      hosts:
        dev-notifications.nos.social:

And so every grouping in the inventory corresponds to its own group_vars directory, and each directory contains its own vars.yaml and vault.yml.    The vars.yml contain the public variables specific to that grouping, and vault.yml the same but with the secret values.
The vault password is the same for every file, will be shared outside of this pr, and it is expected that you keep that password somewhere safe via a password manager.   To use it with these playbooks, set the env var  VAULT_PASS to our pass.  I've updated the ansible.cfg so that it reads from a password file called .vault_pass and then added the .vault_pass file, which is a bash script that just echoes the above env var.  The intention is that we don't have to enter the password every time, but also don't accidentally commit it here.
I want to add inventory files and secrets for all the major services we run currently and additional documentation with example playbooks.  The PR does not feel ready until then, but keen for feedback now to make sure this path works with everyone!

@mplorentz :

If I were to run something like ansible-playbook -I inventories/notifications_service/inventory.yml how would it know to load all the vars from the various grou_vars subdirectory?

It is a built-in feature of ansible to look for group_vars in the same dir as the inventory file running, and it maps any children in the inventory to the child dirs in group_vars with a matching name.  I added an example inventory to this PR to show this in better detail (see readme).

It seems like it would be simpler to just define all the vars in the inventory.yml, is there a reason you aren't doing it that way?

Hahaha, ironically I went this way for improved readability when dealing with the secrets.   If we define all the variables in the inventory file, and some of those variables we want to be secret, then we'd need to encrypt the entire inventory file.  You would only be able to read and review it by either decrypting it or running ansible-vault view.  This makes it harder to review and  more easily invites the risk of decrypting the file, changing a secret, and then committing the inventory without remembering to re-encrypt.
The  structure in this pr lets us have most everything unencrypted and readable from github, and the vars themselves are known.  If we want to change a secret, we are only decrypting a specific secrets file, and this feels less risky.
Another option is that we could define an inventory like so:
---
example:
 vars_file:
   - vars/vault.yml
 hosts:
  ansible.fun:
  dev-notifications.nos.social:
 vars:
   port: 1234
   image: docker/busybox
   password: "{{ vault_password }}"
 children:
   lab:
     hosts:
       ansible.fun:
         image_tag: stable
         password: "{{ vault_lab_password }}"
   nostr:
     hosts:
       dev-notifications.nos.social:
         image_tag: latest
         password: "{{ vault_nostr_password }}"

This might be more readable?  My initial sense was that this style would be harder to read/maintain with ilarger inventorie, but I might be wrong!  I can rewrite the notifications inventory in this style and see if it works well.

@cooldracula that all makes sense, thanks. I agree having to manually decrypt/encrypt the inventory file is a no-go.
It does seem like the ansible way is many layers of directories. Personally I would find the single inventory file easier to use. Even if the file gets stupidly large the command line tools I use make it easier to navigate a large file than a hierarchy of folders that need to be kept in sync with the inventory file. Do you prefer the folders? I could go either way, I don't want to spend too much effort swimming upstream.

This accidentally became a large PR as adding in this new inventories and secrets structure required a lot of small changes across our roles and a cleanup/refactor of the root-level inventories and playbooks.
It also now includes the new-do-droplet playbook, as I wanted to make sure this structure would work for creating a wholly new server with the correct service on it.
I have tested the structure with a dev rss service and a dev notifications service.  In both cases, I was able to pass in an inventory file to the playbook new-do-droplet plus some additional variables (like domain and the additional roles to run).  They successfully went from non-existent server to fully deployed service.
I still need to move our metrics inventories over and double check they work, but it is not likely we'll need to deploy them a bunch so it was low priority.
I am not sure the best way to review this,given the size of the pr.  My apologies for this, but maybe a scheduled pair might be good?


Fix tests on Windows platform

2 tests are failing when the library is executed on windows platform:
Test 1
CLI-module
  spawning a child process
    ignore datatype formats
      should show no error when formats have been passed, with newline separated

Issue
the default shell used to spawn child processes in windows is cmd.exe that does not support new line in the commands.
Proposed solution
In case of platform Windows, set the default shell to PowerShell.exe
Test 2
Main-module, for v3 should
with additional properties
with flag set
`validateExamplesByMap` should throw an error

Issue
The function glob.sync() at src\index.js:153 returns a different path format compared to path.json().
In Windows platform, paths should use forward slashes, but glob.sync() returns paths with backslashes.
This discrepancy creates a difference between the expected path and the path in the error message.
Proposed solution
Use the function path.normalize() to convert the path generated by glob.sync() to a valid Windows path.

Pull request updated


[FEAT] Support Terms & Conditions on Hyva Checkout

:bulb: Feature request
Feature Name

Terms & Conditions
The Desired Behavior

The payment form should not load until the customer has accepted any terms and conditions, to ensure the customer can't place the order until the terms are accepted.

Added in 49a53e340cd220a32c4c3cb1d21ecc4838d14c20 for next release


Build failure: Bottles

Steps To Reproduce
Steps to reproduce the behavior:

build Bottles

Build log
sudo nixos-rebuild switch --flake /etc/nixos [sudo] password for pantelis:  building the system configuration... error: builder for '/nix/store/bqfg2ljj6cmv8cppfhhn08c5zzmakzli-python3.12-patool-2.4.0.drv' failed with exit code 1;        last 25 log lines:        > =================================== FAILURES ===================================        > __________________________ TestMime.test_nested_gzip ___________________________        >        > args = (<tests.test_mime.TestMime testMethod=test_nested_gzip>,), kwargs = {}        >        >     def newfunc(*args, **kwargs):        >         if not testfunc(name):        >             pytest.skip(f"{description} {name!r} is not available")        > >       return func(*args, **kwargs)        >        > tests/__init__.py:44:        > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _        > tests/test_mime.py:198: in test_nested_gzip        >     self.mime_test_file("t.rar.gz", "application/x-rar", "gzip")        > tests/test_mime.py:56: in mime_test_file        >     self.mime_test(patoolib.mime.guess_mime_file, archive, mime, encoding, info)        > tests/test_mime.py:38: in mime_test        >     self.assertEqual(        > E   AssertionError: 'application/gzip' != 'application/x-rar'        > E   - application/gzip        > E   + application/x-rar        > E    : MIME type for archive /build/source/tests/data/t.rar.gz' should be application/x-rar, but was application/gzip. Info: application/x-gzip
> =========================== short test summary info ============================
> FAILED tests/test_mime.py::TestMime::test_nested_gzip - AssertionError: 'application/gzip' != 'application/x-rar'
> =========== 1 failed, 87 passed, 124 skipped, 6 deselected in 20.50s ===========
For full logs, run 'nix log /nix/store/bqfg2ljj6cmv8cppfhhn08c5zzmakzli-python3.12-patool-2.4.0.drv'.
error: 1 dependencies of derivation '/nix/store/d1bhadx9561cqg0fgwhk745j6w4f4d9b-bottles-unwrapped-51.17.drv' failed to build
error: 1 dependencies of derivation '/nix/store/blw4pwy4j0acasw1i72ar9x39i6i2x7w-bottles.drv' failed to build
error: 1 dependencies of derivation '/nix/store/dlrmfwy9w5fxmkgd1im86iajhbmsgvf6-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/ibl3zjikjlfn83aq8fiy6ha5nkp7rfg2-nixos-system-nixos-25.05.20241227.634fd46.drv' failed to build`
Metadata

It outputs nothing
Notify maintainers @psydvl @SCOTT-HAMILTON @Gliczy

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

This is an issue with patool, it is fixed on master with https://github.com/NixOS/nixpkgs/pull/368882.


Function in if

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add example jupyter notebook

It would be nice to have a jupyter notebook that showcases polarify in action. I also suggest adding a link to open it with google colab at the top of the notebook.

Or use marimo in combination with GitHub Pages


Error TypeScript

VSCode Version: Code 1.19.1 (0759f77bb8d86658bc935a10a64f6182c5a1eeba, 2017-12-19T09:41:01.414Z)
OS Version: Linux x64 4.14.8-1-ARCH
Extensions:

Extension
Author (truncated)
Version

beautify
Hoo
1.1.1

Angular-BeastCode
Mik
5.1.15

php-debug
fel
1.12.1

docthis
joe
0.6.0

Angular2
joh
2.11.2

vscode-phpfmt
kok
1.0.17

vscode-scss
mrm
0.6.2

mssql
ms-
1.3.0

node-debug2
ms-
1.20.0

sass-indented
rob
1.4.6

autoimport
ste
1.5.3

react-beautify
tai
0.3.0

vscode-react-native
vsm
0.5.7

(1 theme extensions excluded)

Steps to Reproduce:

Reproduces without extensions: Yes/No

@alexnfsc175 How can this bug be reproduced? What were you doing when you encountered this error?


When is selected the plan , the race date, and the training. if is changed the raceDate, is unselected the training.

preserve the item selected, despite the date changes, and preserve the training detail

Ignore.


Supporting shifting by business days in DateOffset's constructor

Now it is not possible to create a DateOffset which would incorporate shifting by a certain number of business days in addition to any other offset rules. In my view, it would be useful to include a bdays argument which would act similarly to days parameter.
NOTE: It is also impossible to create such a DateOffset indirectly via summation DateOffset(hour=2) + BDay() since DateOffsets are currently not summable as discussed in #10902.

So this works
In [2]: Timestamp('20130101') + pd.offsets.DateOffset(hours=2) + pd.offsets.BDay(1)
Out[2]: Timestamp('2013-01-02 02:00:00')

This doesn't handle business days but is much simpler.
In [4]: Timestamp('20130101') + pd.Timedelta('1 day 2 hours')
Out[4]: Timestamp('2013-01-02 02:00:00')


New version: LOOT.LOOT version 0.20.0

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115111&drop=dogfoodAlpha

@wingetbot run

x86 Automatic Validation ended with:

/AzurePipelines run


Network has been temporary banned - BAD REQUEST

Hello !
Is a problem :
InstagramFeed: It looks like YOUR network has been temporary banned because of too many requests.
See https://github.com/jsanahuja/jquery.instagramFeed/issues/25 4

and
Uncaught TypeError: Cannot set property 'innerHTML' of null
    at Object.display (InstagramFeed.min.js:1)
    at InstagramFeed.min.js:1
    at XMLHttpRequest.c.onload (InstagramFeed.min.js:1)

It means exactly what it says. You are temporarily banned by IG. Wait at least for 24 hours since the last script activation and try again.

J'ai trouvé une meilleure alternative :
https://github.com/stevenschobert/instafeed.js/

It is not an alternative because of
 Instagram Basic Display API

Exactly, but the solution is less limited for my ecommerce use ;)

But you should take into account that only you are banned, and your visitors can see IG images.

Closing as the new client-side caching (cache_time) feature implemented in #97 (2.0.0 release) should deal with this.

Great Jog. I will test the update tomorrow


Line numbers far from the text

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
1.4.14
Describe the bug
Bug
Line numbers display before the gutter, at the far edge of the screen, instead of near the text.
This makes it very hard to make usage of the line numbers.
Line number setting
Options > Editor > Show line number
Obsidian without Minimal theme
Line numbers near the text.

Obsidian with Minimal theme
Line numbers at the far edge of the viewport.

Debug info
SYSTEM INFO:
Obsidian version: v1.4.14
Installer version: v1.3.5
Operating system: Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 22.6.0
Login status: logged in
Catalyst license: insider
Insider build toggle: on
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: Minimal v7.3.2
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.

this is a feature not a bug
https://minimal.guide/features/active-line


x/crypto/acme/autocert: Enable custom port / IP binding

It is mandatory to be reachable on port 443 from the public internet for autocert to work but it is completely fine to run a service on a different port internally and use e. g. NAT on a router to fulfill this requirement.
Additionally there are setups where I don't want to listen on all my local IP addresses.
This can be implemented through a new function ListenerCustomAddress(address) that works like Listener() but accepts a custom address.
PR: https://github.com/golang/crypto/pull/69
Gerrit: https://go-review.googlesource.com/c/crypto/+/155744

Am I missing something or is it already possible to do what you want by calling tls.Listen/http.(*Server).ListenAndServeTLS directly instead of using the autocert manager's convenience function?

Copy of @bradfitz comment in Gerrit:

I'm not a huge fan of this name. Plus Go APIs typically say "Addr" instead of "Address", but even that's kinda weird.
The adjectives should probably go before the noun, too, even though we don't do that everywhere (Dial, DialContext, etc).
Maybe "Indirect443Listener"? To make it super explicit that this is really for port 443 but not directly?
In any case, file a bug and we can bikeshed the name there with others. We don't typically make these sorts of decisions on Gerrit

I'm not really happy with the name, too. Here are my thoughts why I ended up with ListenerCustomAddress and my proposal to solve it.
My first thougt was to make ' Listenermore flexible and move the current Listener functionality to something likeListener443Any` but this will break backwards compatibility and is easy to be used wrong so people will face not working Letsencrypt challenges.
My 2nd idea was to call the function NATListener but this name does not include binding the listener to a selected IP on port 443 without NAT and generally I don't like to refer to names of "external" techniques that might be used but maybe there are other situations without NAT where you want to (and can) use different ports.
So I went with the 3rd option ListenerCustomAddress to stay close to the underlying net package. At the end we are setting net.Listener.Addr.
I thought about a 4th option that maybe work well with @bradfitz proposal Indirect443Listener We can create two new functions

Indirect443Listener(port int) net.Listener or NATListener(port int) net.Listener
ListenerBindIP(IP string) net.Listener.

If somebody really wants to bind to a specific address on a port different from 443 he needs to build this on his own outside of autocert. I'm not sure if it is a good idea to sacrifice flexibility for better function naming but the described case will be rarely needed so I'm fine with it.

@FiloSottile I support your proposal. I think it's more straightforward to use and returning errors is a huge improvement.
The changes should be fairly easy to do but I have two questions regarding the workflow:

Can I mess around with the branch (rebase / force push) without breaking Gerrit integration or something else?

Should I change the PR now and hope it will be approved or wait until a decision is made?

I am no idea , give best way
On Sat 2 Feb, 2019, 9:04 PM Axel Gluth<EMAIL_ADDRESS>wrote:

@FiloSottile https://github.com/FiloSottile I support your proposal. I
think it's more straightforward to use and returning errors is a huge
improvement.
The changes should be fairly easy to do but I have two questions regarding
the workflow:

Can I mess around with the branch (rebase / force push) without
breaking Gerrit integration or something else?
2.
Should I change the PR now and hope it will be approved or wait until
a decision is made?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/29540#issuecomment-459974157, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AgJkYz9_LLpWaHwoc-zQ4aRt0sWV5n39ks5vJa_9gaJpZM4Zo6BI
.

@x1ddos, does https://github.com/golang/go/issues/29540#issuecomment-458711482 look good to you?

This issue requires no code changes imho:

It is mandatory to be reachable on port 443 from the public internet for autocert to work but it is completely fine to run a service on a different port internally and use e. g. NAT on a router to fulfill this requirement.
Additionally there are setups where I don't want to listen on all my local IP addresses.

The above sounds like a non-issue to me:
m := &autocert.Manager{
    Cache:      autocert.DirCache("secret-dir"),
    Prompt:     autocert.AcceptTOS,
    HostPolicy: autocert.HostWhitelist("example.org", "www.example.org"),
}
s := &http.Server{
    Addr:      "<IP_ADDRESS>:8443",
    TLSConfig: m.TLSConfig(),
}
s.ListenAndServeTLS("", "")

Listener has a different purpose:

It enables one-line HTTPS servers

It even says so later:

NewListener is a convenience function for a common configuration. More complex or custom configurations can use the autocert.Manager type instead.

(from https://godoc.org/golang.org/x/crypto/acme/autocert#NewListener)

Talked to @bradfitz about this (we designed this package).
It seems odd to have both Listen and Listener (maybe Listener should have been named Listen from the start but oh well). For >99% of use cases Listener is doing the right thing.
We could imagine adding a field Addr string to Manager, defaulting to ":443", but then what if you want to change the keepalives that listener does?
As it is, listener (the unexported type) is a very small wrapper around Manager itself. It probably makes sense to just copy it out. All you really need access to is m.TLSConf(), which you have.

Based on the discussion above, this seems like a likely decline.

No change in consensus, so declined.


This PR is for  cortx-motr-apps to support multiplatform( x86_64 / aarch64)  build

@Nalini-Seagate,
1.)Why this PR uses selfie.out? Where did you get that? that is not at all part of sample apps.
2.) Why this include the binary fgen file?
Please clean up these first. The update the readme as well and resubmit.

updated the necessary  to resolve the review comments


Cannot ignore ref struct properties

CompareNETObjects fails when it encounters an object which contains a ref struct property, which is expected since you can't access those through reflection.
Unfortunately, you can't ignore such a property either, as the library tries to read the property before it filters out ignored members. Filtering out properties before trying to read them should fix this issue.
Sample repro:
internal class Program
{
    public RefStruct Item => default;

    public static void Main()
    {
        var compareLogic = new CompareLogic(new ComparisonConfig
        {
            MembersToIgnore =
            {
                nameof(Item)
            }
        });

        compareLogic.Compare(new Program(), new Program());
    }
}

public ref struct RefStruct
{
}

Output:
Unhandled Exception: System.NotSupportedException: Specified method is not supported.
   at System.Reflection.RuntimeMethodInfo.ThrowNoInvokeException()
   at System.Reflection.RuntimeMethodInfo.InvokeArgumentsCheck(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, Object[] index)
   at KellermanSoftware.CompareNetObjects.TypeComparers.PropertyComparer.AddPropertyInfos(Object objectValue, Type objectType, IEnumerable`1 properties)
   at KellermanSoftware.CompareNetObjects.TypeComparers.PropertyComparer.PerformCompareProperties(CompareParms parms, Boolean ignoreBaseList)
   at KellermanSoftware.CompareNetObjects.TypeComparers.ClassComparer.CompareType(CompareParms parms)
   at KellermanSoftware.CompareNetObjects.RootComparer.Compare(CompareParms parms)
   at KellermanSoftware.CompareNetObjects.CompareLogic.Compare(Object expectedObject, Object actualObject)
   at ConsoleApp.Program.Main() in C:\Dev\TempProjects\ConsoleApp\ConsoleApp\Program.cs:line 19

Thank you for reporting this issue.

@ltrzesniewski  what version are you running with? I got no issue running your code.

I tested it with the latest version: 1.49.0.
Note that this code will probably not crash if you test it with an old runtime which doesn't understand IsByRefLikeAttribute.
Here's the full project which reproduces the issue, I just added some console output:
ConsoleApp.zip

@ltrzesniewski I have created a fix, ignoring the issue.

Thanks!


Environment variables override cargo --config  in precedence

Problem
If both an environment variable and cargo --config <filename> are specified at the same time, the environment variable overrides the file passed in over the CLI. This is counter-intuitive and also the documentation at https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides is unclear about this:

Configuration values specified this way take precedence over environment variables, which take precedence over configuration files.

Steps
Create .cargo/foo.toml:
[build]
target-dir = "from-foo-toml"

Then, run:
CARGO_BUILD_TARGET_DIR=from-env cargo build --config .cargo/foo.toml

Notice that the build happens in "from-env" rather than the expected "from-too-toml".
Possible Solution(s)
I think the behavior should be changed so that config files passed in over --config come first and environment variables come later.
(Unlike #10991, this I think is straight-up incorrect and should be fixed.)
Notes
I'm guessing this is a regression from #10755 and specifically this change, though I could be wrong. cc @jonhoo, @ehuss
Version
cargo 1.63.0 (fd9c4297c 2022-07-01)
release: 1.63.0
commit-hash: fd9c4297ccbee36d39e9a79067edab0b614edb5a
commit-date: 2022-07-01
host: x86_64-unknown-linux-gnu
libgit2: 1.4.2 (sys:0.14.2 vendored)
libcurl: 7.83.1-DEV (sys:0.4.55+curl-7.83.1 vendored ssl:OpenSSL/1.1.1n)
os: Pop!_OS 22.04 (jammy) [64-bit]

Hm, yea, that's a strange intersection. I'm not sure how hard that would be to fix, but would be good to investigate.

I also realized that there's a related issue. If --config is passed in in this fashion:
--config 'k=v' --config foo.toml --config 'k2=v2' --config bar.toml

Then the behavior I expect is that config would be merged in this order:

k=v
foo.toml
k2=v2
bar.toml
environment
.cargo/config.toml, with discovery as before

However, in reality, config is merged in this order:

k=v
k2=v2
environment
foo.toml
bar.toml
.cargo/config.toml, with discovery as before

From my understanding, the change you referred to might not be the root cause. Either config-include or Config::_load_file will eventually create a ConfigValue with Definition::Path. As Definition::Path is the lowest priority of the three, and the comparison with env var occurs here, so env vars always win over configs from --config <path> and config-include.

-config is passed in in this fashion:
--config 'k=v' --config foo.toml --config 'k2=v2' --config bar.toml

Then the behavior I expect is that configs would have precedence in this order:
...

You are correct that the behaviour is wrong. The precedence you describe could be more precise. AFAIK the flow looks like,

CLI args get merged first. The latter arg takes precedence over former (force merge).
A request of a ConfigValue triggers a deserialization
During the deserialization, get_cv_with_env get called.

For instance, when one runs cargo check with args and env vars below,
k=env0
--config k='cli0'
--config k='cli1'
--config .cargo/file0.toml # k='file0'
--config k='cli2'
--config .cargo/file1.toml # k='file1'

It would look like the followings after cli-args merge before env merge:
k='file1' [from path]
k=env0 [from env]

I feel like the fix would be tricky. We may want to construct a ConfigValue with Definition:Cli here when _load_file is triggered by config-cli, though doing that loses the path information of Definition::Path, regressing the error message. The other way is attaching the requested-from-cli information right on Definition::Path enum, which is more intrusive IMO but the good error message remains.

Click to expand this cargo test case exercising the behaviour aforementioned.
#[cargo_test]
fn merge_primitives_for_multiple_cli_occurences() {
    let config_path0 = ".cargo/file0.toml";
    write_config_at(config_path0, "k = 'file0'");
    let config_path1 = ".cargo/file1.toml";
    write_config_at(config_path1, "k = 'file1'");

    // k=env0
    let config = ConfigBuilder::new().env("CARGO_K", "env0").build();
    assert_eq!(config.get::<String>("k").unwrap(), "env0");

    // k=env0
    // --config k='cli0'
    // --config k='cli1'
    let config = ConfigBuilder::new()
        .env("CARGO_K", "env0")
        .config_arg("k='cli0'")
        .config_arg("k='cli1'")
        .build();
    assert_eq!(config.get::<String>("k").unwrap(), "cli1");

    // Env has a lower priority when comparing with file from CLI arg.
    //
    // k=env0
    // --config k='cli0'
    // --config k='cli1'
    // --config .cargo/file0.toml
    let config = ConfigBuilder::new()
        .env("CARGO_K", "env0")
        .config_arg("k='cli0'")
        .config_arg("k='cli1'")
        .config_arg(config_path0)
        .build();
    assert_eq!(config.get::<String>("k").unwrap(), "file0");

    // k=env0
    // --config k='cli0'
    // --config k='cli1'
    // --config .cargo/file0.toml
    // --config k='cli2'
    let config = ConfigBuilder::new()
        .env("CARGO_K", "env0")
        .config_arg("k='cli0'")
        .config_arg("k='cli1'")
        .config_arg(config_path0)
        .config_arg("k='cli2'")
        .build();
    assert_eq!(config.get::<String>("k").unwrap(), "cli2");

    // k=env0
    // --config k='cli0'
    // --config k='cli1'
    // --config .cargo/file0.toml
    // --config k='cli2'
    // --config .cargo/file1.toml
    let config = ConfigBuilder::new()
        .env("CARGO_K", "env0")
        .config_arg("k='cli0'")
        .config_arg("k='cli1'")
        .config_arg(config_path0)
        .config_arg("k='cli2'")
        .config_arg(config_path1)
        .build();
    assert_eq!(config.get::<String>("k").unwrap(), "file1");
}


Measure validation

Adds a management command (./manage.py import_measures --check) which checks that measure SQL is valid.
Includes a step during fabric build which validates changed measures before building them, with the result that someone deploying a branch to staging will get an exception reported to #technoise.
Validation happens using BigQuery's dryRun option, which will raise exceptions on malformed SQL without incurring execution costs.
Note that this PR contains accidentally-merged commits from Rich which were then reverted, so commit-by-commit review will be hard; just check Files changed, which is not too big.

You can make errors go to the originating channel (I think), but I wondered if that would be too noisy.... will give it a go.


RayCast debug visualization scans 180deg repeatedly, instead of 360

The draw_shapecast call in the debug render on the main branch (as linked here) seems to have strange behavior when the max_distance scalar is greater than about 10,000. (the current min value calculated when not setting a max distance on the raycast displays the issue).
 The black line is being limited to a toi of 10,000 and behaves correctly, while the red line seems to only scan in 180 degrees repeatedly. The scalar max value seems to be<PHONE_NUMBER>00000000000000000000000000000 when the min is calculated.
https://github.com/user-attachments/assets/1ba71b89-9c16-4568-ab27-628b8b5cd707

also notable in the video is that the errant red line display corrects itself if the raycast is actively hitting an object, like it does when it hits the cube.