A few tweaks for pachctl logs2

This adjusts a couple of quality-of-life issues:

Time flags that are unset are not sent to the server.  This changes the default query from "logs starting a month ago to now" to "logs from the beginning of time", which is something that TimeRangeIterator knows how to handle efficiently.  This means that no matter how old your pipeline is, you'll always see logs with pachctl logs2 --pipeline=edges --user or something like that.
Time flags can be durations instead of absolute times.  To get pachd logs from the last minute, pachctl logs2 --from=1m.
All logs are printed as their object now, so that Loki metadata makes it into the printed output.  An object is now always synthesized when the loki line doesn't parse as JSON.  This lets you always pipe the output into jlog or similar for further filtering / querying.
logs2 always prints a warning about an invalid log level; consider "unset" to be valid and don't warn on the default configuration ;)

3. All logs are printed as their object now, so that Loki metadata makes it into the printed output.  An object is now always synthesized when the loki line doesn't parse as JSON.  This lets you always pipe the output into jlog or similar for further filtering / querying.

It would be nice for this to be a --raw or -o json or a similar thing, with the default being to print only the log message itself.

pachctl logs2 ... | jq .message.

pachctl logs2 ... | jq .message.

Sure, but that requires a separate tool. One doesn’t run ls | jq .name or pachctl list repo | jq .name. It’s not a big deal, and logs maybe are more useful structured than not.

I added --raw.


Overlaps Bottom of Hyperterm

See image:
https://www.evernote.com/l/AFk1AUHEIZ5HBKHWR2vaezbJNOzQdPUFvlA
Here's my current configuration:
module.exports = {
  config: {
    // default font size in pixels for all tabs
    fontSize: 12,

    // font family with optional fallbacks
    fontFamily: '"Source Code Pro", Menlo, "DejaVu Sans Mono", "Lucida Console", monospace',

    // terminal cursor background color (hex)
    cursorColor: '#F81CE5',

    // color of the text
    foregroundColor: '#fff',

    // terminal background color
    backgroundColor: '#000',

    // border color (window, tabs)
    borderColor: '#333',

    // custom css to embed in the main window
    css: '',

    // custom padding (css format, i.e.: `top right bottom left`)
    termCSS: '',

    // custom padding
    padding: '0 5px',

    // some color overrides. see http://bit.ly/29k1iU2 for
    // the full list
    colors: [
      '#000000',
      '#ff0000',
      '#33ff00',
      '#ffff00',
      '#0066ff',
      '#cc00ff',
      '#00ffff',
      '#d0d0d0',
      '#808080',
      '#ff0000',
      '#33ff00',
      '#ffff00',
      '#0066ff',
      '#cc00ff',
      '#00ffff',
      '#ffffff'
    ],

    overlay: {
      animate: true,
      alwaysOnTop: true,
      hasShadow: true,
      hideOnBlur: true,
      hideDock: true,
      hotkeys: ['Ctrl+`'],
      resizable: true,
      position: 'top',
      primaryDisplay: true,
      startup: true,
      size: 0.4,
      tray: true,
      unique: true
    }
  },

  // a list of plugins to fetch and install from npm
  // format: [@org/]project[#version]
  // examples:
  //   `hypersolar`
  //   `@company/project`
  //   `project#1.0.1`
  plugins: ["hyperterm-overlay", "hypercwd", "hyperline"],

  // in development, you can create a directory under
  // `~/.hyperterm_plugins/local/` and include it here
  // to load it and avoid it being `npm install`ed
  localPlugins: []
};

It's possible this is caused by a conflict w/ hyperterm-overlay, but not sure.

Also an issue for me (do not have hyperterm-overlay installed). It's possible to fix by adjusting the padding values in your ~/.hyperterm.js:
padding: '12px 14px 13px'

@NickTikhonov This can be closed now. Fixed in #12

@timneutkens I am currently having this issue.
Hyperterm version 2.1.0 (canary) and latest version of Hyperline.

I no longer maintain Hyperline.


Bump k6 version

Fixes https://github.com/grafana/xk6-output-influxdb/issues/27

This helped compile influx + promrw in the same binary. Would be great to see this land!

@joanlopez @mstoykov it requires to get https://github.com/grafana/xk6-output-influxdb/pull/29 merged before.


fixes a warning from ceph commands when rbdmirrors are not used

Including the 'client' section into ceph.conf when you are not using rbd
mirrors causes a warning to occur when running ceph commands. The
problem seems to be specifically with the 'admin socket' config option.
The warning that is generated:
2016-04-19 15:20:05.128327 7fc0e4033700 -1 asok(0x7fc0dc001680)
AdminSocketConfigObs::init: failed: AdminSocket::bind_and_listen:
failed to bind the UNIX domain socket to
'/var/run/ceph/rbd-clients/ceph-client.admin.20455.140466301441968.asok':
(2) No such file or directory
See: https://bugzilla.redhat.com/show_bug.cgi?id=1328594
Signed-off-by: Andrew Schoen<EMAIL_ADDRESS>

@andrewschoen I don't think this is due to the rbdmirror but more because /var/run/ceph/rbd-clients does not get created automatically.
rbd_client_directories default is false.

@leseb ok, I see if I set rbd_client_directories to true then I do not get this warning. Should we change the default value for rbd_client_directories?

@andrewschoen well probably and we should also stick the default to /var/run/ceph.
Do you want to PR this?

+1 on using the default /var/run/ceph

@leseb yeah, I can do that work

@leseb ok, I went ahead and made those changes in this PR.

@andrewschoen cool let's wait for jenkins :)

test this please

We keep having issues with trusty, not related to this PR though. Maybe this next run will fair better.

test this please


rg is not compiled with pcre2 support on ubuntu and opensuse

Hi, first of all, thx for this great plugin.
However when I try to use tags telekasten.show_tags I'm silently getting the error
PCRE2 is not available in this build of ripgrep

after some googling I found out that my rg is not compiled with that flag enabled.
I tested ubuntu 22.04 and opensuse tumbleweed.
So to use telekasten I'd have to use a local version of rg instead of the distribution maintained version.
Which in my opinion is quite annoying and brings more maintenance to my setup. I guess the rg flag --pcre2 got added due to this color issue
Proposed solutions:

only use --pcre2 when #tag is getting used. not for :tag:
document the need for --pcre2 and why
check if --pcre2 is available and if so, use it, else not.
remove the overall need of --pcre2 :smiley:

Thx for your time,
Cheers!

Indeed, the --pcre2 flag was added to exclude the HTML color codes from tags. I did not known --pcre2was not a standard option.
I  the mean time, regarding what you propose, I think the cleanest way would be trying to completely remove the need of --pcre2 while still being able to exclude the colors tags. However, I have absolutely no idea of how we could do that...
I am not really a pro when it comes to regex (I started using that for for this project basically), so I do not know if there is a better solution here. Any help would be appreciated
In the meantime, the second best solution would be to check if --pcre2 is available or not. If it is, no issue. If it is not, then the users will be bothered by the #color stuff (if they also happen to use #tag notation. We can use a note with that in the readme and config examples. Do you know how we could implement such check?

[..] the second best solution would be to check if --pcre2 is available or not. [...] Do you know how we could implement such check?

You could test for the feature like:
> echo 'hello' | /usr/bin/rg --pcre2 hello
PCRE2 is not available in this build of ripgrep
# command exited with code 2
> echo 'hello' | rg --pcre2 hello
hello
# command exited with code 0

I the mean time, regarding what you propose, I think the cleanest way would be trying to completely remove the need of --pcre2 while still being able to exclude the colors tags. However, I have absolutely no idea of how we could do that...

How about not using regex at all. But instead use treesitter which is available to neovim.
Treesitter parses the markdown syntax and should give you a detailed AST about the markdown document.
However I myself never worked with treesitter, so I've no hands-on experience.
Any thoughts on treesitter?

You could test for the feature like:
> echo 'hello' | /usr/bin/rg --pcre2 hello
PCRE2 is not available in this build of ripgrep
# command exited with code 2
> echo 'hello' | rg --pcre2 hello
hello
# command exited with code 0

Yeah we could definitely do that in the setup of TK and then keep the result in config so we avoid re-testing every time we want to use regex. Good idea.

How about not using regex at all. But instead use treesitter which is available to neovim.

While I like treesitter very much, I am not a fan of forcing people to add yet another dependency (rg is already needed for telescope). Besides that, TK uses rgquite extensively already (as well as telescope). So it would be a pain to rewrite everything to avoid it. Finally, I have never actually worked with treesitter either. This can be rather difficult to do, as we need to parse non-opened buffers (finding tags in all notes), we need to be able to work with non-markdown files (.wiki, .zettel, .whatever), etc.

Yeah we could definitely do that in the setup of TK and then keep the result in config so we avoid re-testing every time we want to use regex. Good idea.

Good thinking. How about a setup setting use_pcre2 with the options no, yes and auto. Default auto which tests rg.

This can be rather difficult to do, as we need to parse non-opened buffers (finding tags in all notes), we need to be able to work with non-markdown files (.wiki, .zettel, .whatever), etc.

Makes sense!

Good thinking. How about a setup setting use_pcre2 with the options no, yes and auto. Default auto which tests rg.

There is already a billion options for TK. I may time the impact of running the test at each startup, but it should be fairly small anyway, so we might as well always do it to limit the number of options. Besides, some people use the same neovim config on different machines (my personal laptop has Arch (btw) and my work computer is a Mac). I'd rather avoid having to maintain two different configs for such small feature.

Finally found some time for this!
Could you checkout this branch and tell me if it works?

works for, everything looks fine. Thx for your time!


fix(goal_planner): use recursive mutex instead of transaction

This reverts commit 654fa8cd0dbf036cf693abbd137acae9936c327c in https://github.com/autowarefoundation/autoware.universe/pull/5202
Description

transaction cannot lock in the following cases

thread1: use transaction
thread2: use just setter/getter

Related links

https://github.com/autowarefoundation/autoware.universe/pull/5202
Tests performed

psim
evaluator_description: fix/goal_planner_recursive_mutex
2023/10/23 https://evaluation.tier4.jp/evaluation/reports/fee28b13-55cd-5606-882e-b5c476037840/?project_id=prd_jt
Notes for reviewers

Interface changes

none
Effects on system behavior

none
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

compare
https://evaluation.tier4.jp/evaluation/reports/tables/new?catalog_id=cb497016-2e2f-4ce0-9ac8-68d77a27a55d&filter=&job_id=fee28b13-55cd-5606-882e-b5c476037840&project_id=prd_jt&table_config=date%2Ctotal%2Csrc%2Chide&target_ids=8cdcf567-81a6-59db-81f7-f533153b3e57


Doc improvements for 1.0

Some proposed updates to the docs. @bmcfee - I just want your opinions on these before I proceed on them.

[ ] I don't think the "Simple Example" is a real example, since it doesn't actually use Pescador. I propose to merge the "Simple Example" and "Advanced Example", or at least move the Streamer component into the Simple example.
[ ] Fix / fill out the API Reference (This could just be a bug on my machine in generating them.)
[ ] Buffered streamers example
[ ] ZMQ Example

[ ] Basic example
[ ] More realistic example

[ ] Examples plugging pescador in with common ML/DL frameworks

[ ] sklearn-style APIs
[ ] Keras
[ ] (Lasagne/Theano, Tensorflow, ...)

Absolutely!  This would actually be a great thing to do for docathon.  (Or independently, cause why not.)

Oh! There's even one at Berkeley! I don't think I can take that much time
off work, though. I think at least some of these are pretty important for
V1.0, though, so I'll try to work on them this weekend.
On Thu, Mar 2, 2017 at 5:44 PM Brian McFee<EMAIL_ADDRESS>wrote:

Assigned #58 https://github.com/pescadores/pescador/issues/58 to
@cjacoby https://github.com/cjacoby.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pescadores/pescador/issues/58#event-984718710, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA4t8-7Ue5I7w3clsaq0md9r3G7fy6myks5rh3BmgaJpZM4MRwwf
.

.. and point-by-point, I like all of that.
I suppose since TF is moving toward keras for its high-level interface, maybe we can skip that one.
Possibly a good way to present the examples, rather than directly in sphinx docs, is as a sphinx-gallery.  That way, the scripts are directly downloadable.

Ah neat! :+1:
On Thu, Mar 2, 2017, 17:49 Brian McFee<EMAIL_ADDRESS>wrote:

.. and point-by-point, I like all of that.
I suppose since TF is moving toward keras for its high-level interface,
maybe we can skip that one.
Possibly a good way to present the examples, rather than directly in
sphinx docs, is as a sphinx-gallery http://sphinx-gallery.readthedocs.io.
That way, the scripts are directly downloadable.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pescadores/pescador/issues/58#issuecomment-283841162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4t8yM6U6lwxIDfCggQcp80b6Gj7amNks5rh3GbgaJpZM4MRwwf
.

I'm still having this problem. I spent a while messing with configuration to try and fix it, but no luck.
I'm going to try to spin up a VM later today and see if I get the same problem in Linux / a different environment.


Update FlowListView.cs

I'm trying to emulate the behaviour of ListView's ItemTapped.

Thanks for a help. Merged :) 👍


File format for P4ML models

We either need to adopt the ACEbase.FIO  JSON  interface, or decide on an alternative.

This is maybe a question for @tjjarvinen and @CheukHinHoJerry  and needs some context:
When we started solidifying ACE, JSON3 did not yet exist, and JLD and JLD2 were both incredibly unreliable. So we decided to basically create our own JSON wrappers and enforce that all model components must implement that wrapper, basically converting manually between struct and Dict. The interface is in ACEbase.FIO and requires overloading read_dict and write_dict. This has worked very well.
But it's now many years later, and maybe the rewrite of the kernels is a chance to revisit this decision. Any thoughts?

The issue with JLD2 is that, if you change something in the type definition, it will break the files. So, if you use JLD2 (don't even consider JDL1) you need to formulate the save, so that it only saves general Julia structures like arrays, dictionaries, strings etc.
The good part with JLD2 is that it binary format with an option to compress, which will save space. The issue with JLD2 is that it is mainly Julia only, if you want the option to move to some other language then JSON3 is probably better.

I think JSON3 is better too. Given that we don't usually have huge model sizes I think JSON3 works well. It is even more friendly to some users who wants to run ASE in python with ACE.

So let’s look into that. Two questions I have

are we throwing out all our read_dict / write_dict interface or just migrate it to JSOn3?
How do we control loading models saved in different package versions?


After recovery the secondary device is not visible in the F&F list.

-Before the recovery, I confirmed the Level 2 secondary device.That was also seen in the F&F list.
-After that I restored the wallet, now I do not see that in "My Keepers" F&F list.
-After that I was going to add "Add keeper" at Level 2, then I got the error "First Complete Primary Keeper Setup".

-Verified this issue on dev app v1.5.0(249)


"No id found for..." error log message

Thank you for this packge. I've been trying to link org-roam and logseq for a while using the file path method, but it didn't work. As you noted, it is buggy. So I was glad to come across this library.
When I execute logseq-org-roam, I am getting some errors that say: "No id found for..." I'm trying to understand what this error means and how I can remediate. Can you explain?

Hi Ethan,
I just saw your email, my apologies for the late reply. Thanks for trying
the package. I'm still using it daily.
I will double check the code before I answer. From memory, "no id found"
occurs when org-elements fail to parse the org-id in the file. I think it
occurs only after the package already attempted to convert the file to
org-roam.
Usually, the fix consists in looking up the org-roam files already opened,
closing them, then retrying. The issue seems to be with org-elements, but I
have not dived deeply into it.
I'll double check the code later to make sure the above is accurate.
Sylvain
On Sun, 20 Oct 2024, 22:09 Ethan Miller, @.***> wrote:

Thank you for this packge. I've been trying to link org-roam and logseq
for a while using the file path method, but it didn't work. As you noted,
it is buggy. So I was glad to come across this library.
When I execute logseq-org-roam, I am getting some errors that say: "No id
found for..." I'm trying to understand what this error means and how I can
remediate. Can you explain?
—
Reply to this email directly, view it on GitHub
https://github.com/sbougerel/logseq-org-roam/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLKAXNWHPVW5XJRUWTLRDDZ4O2RBAVCNFSM6AAAAABQIRVAROVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYDANJQGIYDANQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi Ethan,
Background
So my memory was correct. The package raises this issue when it looks at its internal report of all updates performed. The report is constructed by re-scanning all files after they have been updated. Updates are performed in 3 stages:

Add all identifiers and titles, then reparse updated files only
Use identifiers and titles to update all links, reparse updated files only
(optionally) create additional files

I decided early that I needed to reparse all files after the updates because I (and other) may have save file hook that alters the file structure. Since during parsing, I create an index of all the positions in the files that require updates (e.g. links, titles, etc) I need to ensure these positions are accurate post update by external packages.
Issue encountered
The parsing is done by org-element-parse-buffer which returns an AST-like structure of the file. In some circumstances, org-element fails to parse the buffer correctly.
Things to test
I do remember facing this issue quite regularly in the past (I would say around 6 months ago) but I have not seen it in a long time. Note that I am using straight package manager and I'm always getting the latest from the repository. org-element has received a lot of improvement last year, and if you were on an older version, your experience might be impacted.
Let me know if you face these issues always on the same files or its different files every time.


ESMValBot tests for v2.2

DO NOT MERGE!
This is here so we can run the tests with @esmvalbot

@esmvalbot Please run examples/recipe_correlation.yml

@esmvalbot Please run examples/recipe_julia.yml

@esmvalbot Please run examples/recipe_my_personal_diagnostic.yml

@esmvalbot Please run  examples/recipe_ncl.yml

@esmvalbot Please run examples/recipe_ncl.yml

I just manually killed the process running the recipe mentioned above by the bot.

@esmvalbot Please run examples/recipe_ncl.yml

v2.2.0 has been released, closing this.


Allow multiple meetings

(Probably should wait to review this until #47 is merged to develop because otherwise the changes from that branch will appear in this branch's Files changed tab)
To Test:

npm install and npm start.
First try importing and exporting the math-schedule.csv, and notice that the exported meetings for classes with multiple meetings are on multiple lines as expected (includes days, startTimes, locations, roomCapacities, durations).
Also note that the bug with commas in the name of a course is fixed (should only appear in one field), but this could still be a problem with other fields...
Now try using the add a course/section popup to add a new meeting on an existing section, so for example, try Math 100 A with new days, duration, location, roomCapacity, startTime, and notice that it is added to the same section when exporting.
Try to break it with edge cases?

Might be useful to log the schedule after parsing/adding courses/sections/meetings for testing purposes.

I suggest you resolve the conficts so it's easier to view the changes. Thanks! @Syobnaf

I suggest you resolve the conflicts by merging in develop branch to this branch so it's easier to view the changes. Thanks! @Syobnaf

Thanks for the heads up, should be good now.

@Jonri2, I could not get the app to crash. It could handle (after some time) the Course Section Enrollment.csv.

The crash was fixed after the first review iteration. I'm not sure what was causing it, but it seems good now :)


Update _config.yml

Hey @MiftahurRidho . I guess you are new to github and don't know how things work here.
No problem! We all started somewhere ;)
If you want to use this theme for your website the easiest way to do this is to fork the 'front-cover' repository and rename it to MiftahurRidho.github.io . That way you have a copy of the repository on your account which you can edit and customize. You can reach the website under http://miftahurridho.github.io
What you just did was a so-called pull request. This allows you to fix bugs or just generally improve the code which you can submit back to me so I can push it to the main 'front-cover' repository.
But that was probably not your intention since you only customized it for your needs...
I hope this helped.
Best regards


[CARBONDATA-1618] Fix issue of not support table comment

Background: Current carbon do not support table comment when create table.
This PR will support table comment.

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/681/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1318/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/682/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1319/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/689/

@sounakr  please review it.

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1324/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/701/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1337/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/752/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1389/

@chenerlu how the tablecomment added through ddl is persisted? I don't see anywhere the logic to persist the tablecommnet.

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/789/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1422/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/790/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1423/

LGTM, comments of this PR will be handled in another PR


code --wait should return when window of opening file loads something else

Steps to Reproduce:

use code --wait <path> to open a file and wait for the window to close
in the window that opens, load another folder so that a reload is triggered
=> the --wait process does not terminate even tough the file is no longer opened

Fixed via https://github.com/Microsoft/vscode/commit/fa269dfaaf55c0803697ca480b223bd128da755e


Add testing module

It seems like every release breaks something here and there. It would be very useful if the ETL had a CI that ran tests. Customers (like myself) could then add tests with the following files:

setup.sql - set up the schema for the ETL
CLASS.json - config files for every class
CLASS.data - mock JSON data files for every class
At a very basic level, the test could just ensure that the ETL completed without error. At a more useful level, the test could also run queries and compare the results to what is expected.

@laa I think this is done. If so, we can close this.

mvn clean install is not running  the tests, so is it jenkins but we are not really running tests in jenkins, i'll reopen this.

As I see orientdb-etl in Jenkins tests are runing now.


emptyOutDir seems to be hardcoded to false

Is that on purpose, can we allow it to be controllable on the client build seeing as it runs first, and hardcode false for the server build as we can't clear it at that point?

I don't really remember what was the reason to have false as the default 🤔
In any case, you can override that. I think by just passing it to Vite as a normal option should affect both front and backends. Otherwise, you can pass options only for the frontend build in Vite SSR plugin:
viteSSR({
      build: {
        clientOptions: {
          build: {
            emptyOutDir: true
          }
        }
      }
    })

Hmpf, you're right. I had tested with server only, however, after drilling into the source code, I just realized that the output directory when building with this library isn't ~/dist, but ~/dist/client and ~/dist/server
So what I'll do is clear both.
However, as part of my build process, what I'm trying to achieve is to have the client as static files uploaded somewhere on a server, and for SSR - a single-file binary via pkg. So I'm building the server with pkg successfully and then moving it into the ~/dist directory. And somewhat naively thought I'd have the option to clear the whole directory via a single option.
Do you think it's worthwhile investing into an option to clear ~/dist, or rather to leave it to user code to achieve that?


non-branch commitish doesn't work

The following advertised example doesn't work:

(:70c2952): not on any branch; parent commit has sha1 70c2952

Observe:
(master|✔)~/.zsh-git-prompt> git checkout HEAD\^
Note: checking out 'HEAD^'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at d8cc0aa... more readable presentation of the output
~/.zsh-git-prompt>

I'm using this repo at c6032a64aaaa4dd45216eda8102fea61b0a5933a with zsh 4.3.12 (x86_64-unknown-linux-gnu) and Python 2.7.2.  Thanks.

What's your version of git? I can't reproduce your error with git v <IP_ADDRESS>.

git version 1.7.7


Create Project Structure

Hi Team,
I have created the project structure, please verify and let's proceed with the next steps

Looks great! Thank you Affrin


[Bug]

### Actual behavior
[chrome  mac os x #0-0] Spec: /Users/sf-unified/utam-js-recipes/force-app/test/record-create.spec.js
[chrome  mac os x #0-0] Running: chrome (v) on mac os x
[chrome  mac os x #0-0] Session ID: ec32bc66889e3e30dce609b1d166132c
[chrome  mac os x #0-0]
[chrome  mac os x #0-0] Record creation tests
[chrome  mac os x #0-0]    ✖ "before all" hook
[chrome  mac os x #0-0]    ✖ Create a new Account Record
[chrome  mac os x #0-0]    ✖ Create a new Opportunity Record
[chrome  mac os x #0-0]
[chrome  mac os x #0-0] 3 failing (1.4s)
[chrome  mac os x #0-0]
[chrome  mac os x #0-0] 1) Record creation tests "before all" hook
[chrome  mac os x #0-0] An element on the interface of UTAM Element or a Locator must be provided in order to load a PageObject
[chrome  mac os x #0-0] Error: An element on the interface of UTAM Element or a Locator must be provided in order to load a PageObject
[chrome  mac os x #0-0]     at UtamLoader.load (/Users//sf-unified/utam-js-recipes/node_modules/@utam/loader/build/index.js:42:19)
[chrome  mac os x #0-0]     at login (/Users//sf-unified/utam-js-recipes/force-app/test/utilities/salesforce-test.js:23:30)
[chrome  mac os x #0-0]     at processTicksAndRejections (internal/process/task_queues.js:93:5)
[chrome  mac os x #0-0]     at UserContext. (/Users//sf-unified/utam-js-recipes/force-app/test/record-create.spec.js:64:9)
[chrome  mac os x #0-0]     at UserContext.executeAsync (/Users//sf-unified/utam-js-recipes/node_modules/@wdio/utils/build/shim.js:101:16)
[chrome  mac os x #0-0]     at UserContext.exports.testFrameworkFnWrapper (/Users//sf-unified/utam-js-recipes/node_modules/@wdio/utils/build/test-framework/testFnWrapper.js:25:18)
### Steps to reproduce
Followed the steps as described in the readme file
### Environment
Sanbox
### Additional context
the Login script seems not working and I think the consequent steps are failing.

Thanks, Martin
listing steps below

I replaced .env file (with my login and credentials)
renamed existing pageObject folder to pageObject2
ran yarn build, this generated new pageObject folder (just to ensure I have the newly compiled files)
Than ran only - yarn test --spec force-app/test/record-create.spec.js
got an error with saying (Error: An element on the interface of UTAM Element or a Locator must be provided in order to load a PageObject)

I added try/catch and below is the modified code and error stack. and I also verified the code gets my credentials
added modified utilites/salesforce-test.js
try{
const login = await utam.load(Login);
console.log('after UTAM load');
await sleep(2000);
    await login.login(username, password);

    await sleep(2000);
}catch(e){
    console.log('after UTAM load error');
    console.log(e);
}

=== error stack
[0-0] Error: An element on the interface of UTAM Element or a Locator must be provided in order to load a PageObject
at UtamLoader.load (/Users/chandrasekar.pathipa/sf-unified/utam-js-recipes/node_modules/@utam/loader/build/index.js:42:19)
at login (/Users/chandrasekar.pathipa/sf-unified/utam-js-recipes/force-app/test/utilities/salesforce-test.js:23:34)
at UserContext. (/Users/chandrasekar.pathipa/sf-unified/utam-js-recipes/force-app/test/record-create.spec.js:67:9)
at UserContext.executeAsync (/Users/chandrasekar.pathipa/sf-unified/utam-js-recipes/node_modules/@wdio/utils/build/shim.js:101:16)
at UserContext.exports.testFrameworkFnWrapper (/Users/chandrasekar.pathipa/sf-unified/utam-js-recipes/node_modules/@wdio/utils/build/test-framework/testFnWrapper.js:25:18)
[0-0] 2022-02-07T19:14:40.981Z DEBUG @wdio/utils:shim: Finished to run "afterHook" hook in 0ms

I just sent you an invite to join our external support channel where we'll be able to jump in a video call and troubleshoot this. This should help troubleshoot your issue quicker! Hope this works for you.

After some analysis, the issue was caused by different versions of the UTAM dependencies being present in the workspace's packages:

<EMAIL_ADDRESS>in the utam-preview package
<EMAIL_ADDRESS>at the workspace root

After resetting versions of the dependencies to be in async (to 1.0.1) and running yarn clean && yarn build && yarn install we were able to have the test running.
@cpathipati feel free to close the issue to confirm the problem has been solved!

Thanks, @olivier-martin-sf. This issue is resolved now!
I will continue testing and will let know if any issues.
Thanks again

Thanks a lot, @olivier-martin-sf


[Enhancement] Swap these 2 arguments so they are in the correct order: expected value, actual value.[PravegaStorageConfigTest]

Search before asking

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

Enhancement Request

located at:
eventmesh-storage/eventmesh-storage-pravega/src/test/java/org/apache/eventmesh/storage/pravega/config/PravegaStorageConfigTest.java line 50,51,53,54,56-58
analysis and explanation:
The standard assertions library methods such as org.junit.Assert.assertEquals, and org.junit.Assert.assertSame expect the first argument to be the expected value and the second argument to be the actual value. For AssertJ, it’s the other way around, the argument of org.assertj.core.api.Assertions.assertThat is the actual value, and the subsequent calls contain the expected values. Swap them, and your test will still have the same outcome (succeed/fail when it should) but the error messages will be confusing.
Describe the solution you'd like
Swap actual and expected values.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

I would like to work on this.
/assign

@akashsawan1 Welcome, you can submit a pr first.

I have already submitted a PR 2 days back.
Please check and let me know if any change is required.
https://github.com/apache/eventmesh/pull/3658


InfluxDB 2.0 - Write failed - storage-engine - unexpected end of JSON input

Hi,
I have a problem with my influxdb (latest version)
I´m running the influx inside of a docker container (azure container instance)
Data is inserted by telegraf.
Everything is fine.
Now I implemented a second telegraf instance which sending the data to a second bucket, same org.
After a few seconds the following log messages appear.
I have no idea where this is coming from.
First of all, who is sending the message "unexpected end of JSON input", and when does this happen?
Is it related to the input data?
Or how can I enhance the debug message?
ts=2021-09-03T16:35:22.019827Z lvl=info msg="Series partition compaction (start)" log_id=0WN81wYG000 service=storage-engine partition=0 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/00 op_event=start
ts=2021-09-03T16:35:26.197561Z lvl=info msg="Series partition compaction (end)" log_id=0WN81wYG000 service=storage-engine partition=0 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/00 op_event=end op_elapsed=4177.741ms
ts=2021-09-03T16:35:26.477786Z lvl=info msg="Series partition compaction (end)" log_id=0WN81wYG000 service=storage-engine partition=2 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/02 op_event=end op_elapsed=5379.702ms
ts=2021-09-03T16:35:26.506912Z lvl=info msg="Series partition compaction (end)" log_id=0WN81wYG000 service=storage-engine partition=4 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/04 op_event=end op_elapsed=4661.029ms
ts=2021-09-03T16:35:46.184542Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
ts=2021-09-03T16:35:56.344869Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
ts=2021-09-03T16:36:05.670810Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
ts=2021-09-03T16:36:18.987579Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"

Thx in advance
Martin

Can you try running with debug logging? See: https://docs.influxdata.com/influxdb/v2.0/reference/config-options/#log-level
It looks like the error message only comes from a shard needing to be created and not being able to, or (more likely I think in this case) a write not being able to be made successfully, see: https://github.com/influxdata/influxdb/blob/279c23a0c62f7fbdf65499e8345b3258c969d4c7/v1/coordinator/points_writer.go#L439-L451

Ok, I changed the log-lvel to debug. but t
still msg is
ts=2021-09-03T21:24:08.450871Z lvl=info msg="Write failed" log_id=0WNOIrdW000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
ts=2021-09-03T21:24:08.466571Z lvl=debug msg="Compaction progress" log_id=0WNOIrdW000 service=storage-engine engine=tsm1 tsm1_strategy=full tsm1_optimize=false op_name=tsm1_compact_group output_file=/var/lib/influxdb2/engine/data/45fad86a9d732ab5/autogen/2/000000185-000000002.tsm.tmp size=524292393

and a lot of this one, internal error but only debug
ts=2021-09-03T21:24:12.064044Z lvl=debug msg=Request log_id=0WNOIrdW000 service=http method=POST host=localhost:8086 path=/api/v2/write query="bucket=second-bucket&org=myorg" proto=HTTP/1.1 status_code=499 response_size=90 content_length=-1 referrer= remote=[::1]:44352 user_agent=Telegraf took=20561.129ms error="internal error" error_code="internal error"
And telegraf log a lot of ..
2021-09-03T21:29:21Z E! [agent] Error writing to outputs.influxdb_v2: Post "http://localhost:8086/api/v2/write?bucket=second-bucket&org=myorg": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Hi @Prybe, we faced the same problem a few days ago and found a workaround.
I explained the full problem and the workaround on the community website : https://community.influxdata.com/t/error-when-writing-data-unexpected-error-writing-points-to-database-shard-2613-unexpected-end-of-json-input/22883/2
Hope it helps !

I'm facing the same problem. It seems that there's no .tsm file for this shard. The solution proposed by @bvasunr does not apply, there's no backup database where this .tsm is available to copy from.
Is there a way to either restore this shard or remove it all together, so that there's at least no write error?

Hello,
i'm having the same problem and I cannot push data on my bucket.
{"code":"internal error","message":"unexpected error writing points to database: [shard 378] unexpected end of JSON input"}
is there a way to deactivate this shared or open it to  its fix the structure ?

@sidwise I also faced this issue. The issue probably started when the server running the influx instance ran out of space.
The dirty "solution" I came up with was to remove the shard in its entirety. Just removing the index file for the shard was not enough, so I also removed the data itself. This is less than ideal, but nothing else worked for me.


Improve support for production of frozen tables with locked metatables

The locked-metatable state and frozen state of a table are (mostly) mutually exclusive, because setmetatable and table.freeze error when the other state is present.
Setting metatable first:
local mt = {__metatable="locked"}
print(pcall(function()
	local v = {foo="bar"}
	setmetatable(v, mt)
	table.freeze(v)
	print(v.foo)
end))
--> invalid argument #1 to 'freeze' (table has a protected metatable)

Freezing the table first:
local mt = {__metatable="locked"}
print(pcall(function()
	local v = {foo="bar"}
	table.freeze(v)
	setmetatable(v, mt)
	print(v.foo)
end))
--> Attempt to modify a readonly table

This can be worked around by temporarily unsetting __metatable before freezing:
local mt = {__metatable="locked"}
print(pcall(function()
	local v = {foo="bar"}
	setmetatable(v, mt)
	local locked = mt.__metatable
	mt.__metatable = nil
	table.freeze(v)
	mt.__metatable = locked
	print(v.foo)
end))

This seems rather clunky, though. Especially since it involves temporarily unlocking the metatable of all related objects just to construct a new one.

Yeah that's correct. This is to some extent intentional - out of abundance of caution, when introducing table.freeze we prohibited it to work on tables with locked metatables because the fact that the metatable is locked may have indicated that some sandboxing mechanism is in effect, and being able to freeze the table would potentially break the system that exposes this table.
That said I don't know that this is inspired by specific problems - it's more correct to say that we were trying to be careful. The logic is that if you didn't protect the metatable your table can be tampered with anyway, so table.freeze doesn't introduce new ways to tamper with existing code.
So one way of resolving this would be to lift the restriction on freezing. Out of curiosity, what use cases for locked metatables do you have in mind? My current understanding of the state of sandboxing is that once you have freezing, you actually don't really have to protect the metatable; eg in Roblox, string metatable is protected but in Luau CLI, it's not - it's simply frozen. So it's not 100% obvious to me that locking metatables is very worthwhile.

My particular case was in an "error" object, where the contents were never meant to be modified, and it uses a metatable to implement a standard error interface. For example,
-- Standard interface.
type Error = {
	Error: (self: Error) -> string,
}

local FormattedError = {
	__index = {},
	__metatable = "The metatable is locked",
}
local function newFormattedError(format, ...)
	local self = {RawMessage = format, ...}
	table.freeze(self)
	setmetatable(self, FormattedError)
	return self
end
function FormattedError.__index:Error(): string
	return string.format(self.RawMessage, table.unpack(self))
end

In this case, it was never really necessary to lock the metatable, but it's how I found the issue.
It hadn't occurred to me that freezing the table would also prevent the metatable from being set. A neat side-effect of this is that getmetatable still works, which is often useful for checking the "type" of an object. It also just occurred to me that the metatable itself can be frozen to prevent further tampering.
Even so, I identify several uses for locking a metatable:

Blocking getmetatable, to prevent reuse of the metatable where it isn't meant to be, or inspection of its contents.
Blocking setmetatable for unfrozen objects.
Preventing users from freezing an object unexpectedly. If a method needs to modify a field, then it should be able to without the user interfering.

I think these depend on how interested one is in preventing accidents. The first and second cases only seem to block deliberate actions, so they aren't actually useful. The third case seems somewhat more legitimate; a user might accidentally freeze an object, and is later greeted by an apparently nonsensical error after calling a method that modifies the object. In fact, it makes me wonder if tables with any kind of metatable should be freezable, locked or not.
Anyway, I think that the current restrictions with both setmetatable and table.freeze are useful and correct (in isolation), and shouldn't be changed.
The issue could be resolved by setting the metatable and freezing at the same time. In one solution, table.freeze could receive an optional metatable as a second argument. Or setmetatable could receive an extra flag that freezes the table. Another option would be to add a new function that does the work, which would of course bloat the API. A final option would be to do nothing at all; the problem is so rare in practice that any solution wouldn't be worth it. My overall opinion is that this is a design problem more than a practical problem, which makes it worth solving.

I'm going to close this for now - in general we're not considering locked metatables a critically important use case at the moment, and building a special feature for this is a little awkward. Locked metatables were fairly critical before table freezing, but after table freezing they are typically not critical for sandboxing. This makes it difficult to select the correct route here, as the resulting use case is fairly niche.


can this be run directly from Isilon ?

Hi, i am having issues running the script directly on the Isilon? trying to run there to get the capacity details for the allocated shares.
its failing in the first step itself, datetime - Isilon has python 2.7 installed

Hi, i am having issues running the script directly on the Isilon? trying to run there to get the capacity details for the allocated shares.
its failing in the first step itself, datetime - Isilon has python 2.7 installed

I designed the script as a pre migration tool.  The idea is to calculate "if I were to migrate this data on a host to an Isilon/Powerscale system, how much space will it take up?".
The answer to this is pretty complex as you'd have to know how large each file is, the protection scheme to be used and how many nodes there are (and you'd have to calculate this for each file!).
If the data is already on the array this should be easier to simply measure (df or Isi-get for example), but you are welcome to adapt the script to run directly on a node (as noted Python is already installed on the nodes).


Consider alternative, annotation-based syntax

class BgColor(TypeEnum):
    transparent: tuple[()]
    name: tuple[str]
    rgb: tuple[int, int, int]
    hsv: tuple[int, int, int]

This is of course more verbose, and there is no corresponding syntax for named fields, but this would make working with generics easier in the mypy plugin.

If I want pyright to show fewer errors, I could do something like this:
from typing import Tuple, Type
from typing_extensions import TypeAlias, TypeVarTuple, Unpack

Ts = TypeVarTuple("Ts")

t: TypeAlias = Type[Tuple[Unpack[Ts]]]

and then define fields with A: t[int, str].


Bug in loss recording for LAMA

The loss variable recorded for the LAMA task isn't the average over the dataset.
Since loss is always reset in the if-else block, the recorded loss on this line is always the double of the last batch.
Pasting the relevant block here for reference
for x_hs, x_ts in loader:
    if False and self.args.extend_data:
        loss, _hit1 = self.model.test_extend_data(x_hs, x_ts)
    elif evaluate_type == 'Test':
        loss, _hit1, top10 = self.model(x_hs, x_ts, return_candidates=True)
    else:
        loss, _hit1 = self.model(x_hs, x_ts)
    hit1 += _hit1
    loss += loss.item()

Thanks for your reminding. We will fix it in our next major update.


Close warning message dialog when resetting context in browser tests

Description
Staging probers are failing (sample link) due to an axe accessibility test failing on the "Do not enter actual or personal data in this demo site" pop up dialog. This dialog is never show in prod, so is not a real issue.
We don't show the warning pop up message when running the browser tests in non-staging environments (code link), so this was failing on staging but passing everywhere else.
This PR should hopefully fix the staging failures.
Release notes:
N/A
Checklist

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)

Codecov Report

Merging #3350 (2ba0cf1) into main (e36385b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #3350   +/-   ##
=========================================
  Coverage     80.21%   80.21%
  Complexity     2348     2348
=========================================
  Files           287      287
  Lines          9259     9259
  Branches        619      619
=========================================
  Hits           7427     7427
  Misses         1592     1592
  Partials        240      240

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Multipage

Having one template for each page, all extended from base.html
Use cookie to store the dataset Id
Use Babel and Babel-minify to transpile and minify the code in /src, the code in /dist gets generated automatically from /src
Fixed the styling issue when the dataset name and the username overlap when either or both become very long

Codecov Report

Merging #82 into develop will decrease coverage by 0.01%.
The diff coverage is 69.23%.

@@            Coverage Diff             @@
##           develop     #82      +/-   ##
==========================================
- Coverage    80.61%   80.6%   -0.02%
==========================================
  Files           37      37
  Lines        14573   14585      +12
  Branches      1441    1441
==========================================
+ Hits         11748   11756       +8
- Misses        2348    2352       +4
  Partials       477     477

Impacted Files
Coverage Δ

ga4gh/server/frontend.py
66.45% <69.23%> (ø)
: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 6387c87...1e84d5b. Read the comment docs.


Update icon

Hello
Do you think to do a new icon for "update".
Thank you!

There's already bx-refresh


Implement IManagerPackageActions and related work.

Some of the logic pertaining to project managers can be extracted into libraries.  So the IManagerPackageActions interface was created which defines methods to download a package version, get all versions of a package, get the latest version of a package, and get a package's metadata. Currently, the only implementation is for NuGet which now uses the NuGet.Protocol library, I created a NuGetPackageActions class to implement the interface and use NuGet.Protocol to implement the methods defined in IManagerPackageActions

The download tests are failing for NuGet. I'm OOF until wednesday, just wanted to get this out for review so hopefully I have some comments to address on wednesday.

@gfs If we mark the BaseProjectManager async methods as async they'll warn us unless we suppress the warnings, or have an await in this implementation.

@gfs If we mark the BaseProjectManager async methods as async they'll warn us unless we suppress the warnings, or have an await in this implementation.

@jpinz I expected as much. I think its fine to leave as is.

@gfs can't respond inline to this comment for some reason: https://github.com/microsoft/OSSGadget/pull/327#discussion_r849887287
But it doesn't appear to return null strings, it can however return an empty list of strings.

@gfs can't respond inline to this comment for some reason: https://github.com/microsoft/OSSGadget/pull/327#discussion_r849887287
But it doesn't appear to return null strings, it can however return an empty list of strings.

In that case ignore the suggestion for changing the await position but you should remove the ? On the  string declaration inside the forecast, the enumeration shouldn't be returning nulls. If it's empty it should skip execution of the for each body entirely.
Unless, is this another edge case with tasks instead of AsyncEbumerable?


Feature Request:  Add option to always pad conversions to hex and binary as full bytes

The existing options to either prompt or always pad to a certain length is nice for smaller conversions, but it is not practical for converting longer strings of Hex to Binary where the needed padding length is not easily determined.
For instance:  Converting 01ffff0007f101 from Hex -> Binary.  You would need to set the padding 56 to get full byte boundaries, which is not readily obvious.  This also becomes impossible to use with the current tool when converting multiple selections to binary, each of different lengths.
I suggest adding the following option:

Converter: Always Use Full Bytes
:ballot_box_with_check:  Use full bytes when converting to Hex and Binary.  This also changes the padding feature for conversions to Hex and Binary to apply to the total number of bytes instead of binary bits or hex characters.

I would also recommend turning that option on by default.  I suspect most of your users probably expect this functionality.
You may also want to change the default "Pad to Length" to have separate options for each output type.
BTW, I love the tool!  I'm surprised there are not other tools similar to this.

Thanks for the feedback! That's a solid idea and makes sense. I probably won't have time to implement it in the near term, but will put it on the back burner. Feel free to submit a PR and I'll get it merged if you want it done sooner.


fix(6509): improve the test case coverage of [saga] module to 70%

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
fix https://github.com/apache/incubator-seata/issues/6509
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@xjlgod You can submit your PR in stages.

@xjlgod You can submit your PR in stages.

I am trying to invoke codecov action to see my test case coverage by add new commit.  But I find the error is
'Rate limit reached. Please upload with the Codecov repository upload token to resolve issue. Expected time to availability: 2244s.

It seems that the quota limit has been reached.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 52.39%. Comparing base (8b58f85) to head (6ccff41).
Report is 14 commits behind head on 2.x.

Additional details and impacted files

@@             Coverage Diff              @@
##                2.x    #6519      +/-   ##
============================================
+ Coverage     50.02%   52.39%   +2.37%
- Complexity     5224     5449     +225
============================================
  Files           950      950
  Lines         33447    33448       +1
  Branches       4047     4048       +1
============================================
+ Hits          16732    17526     +794
+ Misses        15104    14155     -949
- Partials       1611     1767     +156

see 70 files with indirect coverage changes


bug: fix environment variables escaping (#288)

Added a function to escape environment variables (see normalize_escape_sequences). It is mainly based on ansi-c escape sequences plus some extra chars ('`', '$'), these  were escaped by bash in my current environment.
I also rewrote the bash script output parsing to escape the values after parsing (mainly  for multiline variables).
Unit tests
The unit test were failing in my environment due to the original escaping method. They all now succeed.
I have modified one value in 'test_from_bash_script' which looks that it was incorrectly escaped.

@issmo it wasn't clear to me what the changes to from_bash_script were intended to do. The tests didn't behave any differently with those changes. If I'm missing something from that let me know what test case I could add.

it works fine with the initial parsing then looping through the variables and clean the additions hashmap. I just tried to do everything in one pass.
I have tested the update and so far everything works fine for me.
Thanks a lot.


Upgrade to use 6.0.0 typings + remove all hard references to PIXI

For some reason, the animation in the example isn't working right after this change. @ivanpopelyshev can you take a look.

The problem is that import * as utils from '@pixi/utils;gets compiled intoPIXInotPIXI.utils`.

Fixed the problem. @pixi-build-tools/globals had @pixi/utils's namespace listed as PIXI, but it should've been PIXI.utils; republished.

@bigtimebuddy Removed the dependency on the canvas tilemap plugin & removed registration. That should fix the PIXI reference.


App Store Connect Operation Error  /  The app references non-public selectors in Payload

An error occurred when I archived an app containing TwitterKit5 with Xcode14.0 and performed validation.
App Store Connect Operation Error
The app references non-public selectors in Payload ****** /TwitterKit.framework/TwitterKit: placeID

Anyone know a solution for this issue?

Even with this warning message, I was able to upload the binary to App Store Connect.
And it passed the review by Apple and was able to be distributed on the App Store. The delivered app is working fine.
However, I have submitted feedback to Apple as this appears to be a bug in Apple's validations handled in the backend.


Named volume is deleted after a first containter using it is run with "autoremove" option.

Steps to reproduce:

Create a named volume.
$ docker volume create --name <named_volume>

1.1. It is listed in volumes
$ docker volume ls
DRIVER              VOLUME NAME
...
local               <named_volume>
...
1.2. So far in /var/lib/docker/volumes:
$ ls -l /var/lib/docker/volumes/
...
drwxr-xr-x 3 root root   4096 Jan 19 13:50 <named_volume>
...

Then I "put" a file "into it"
$ echo file content > /var/lib/docker/volumes/<file>

run a container with --rm option
$ docker run -v <named_volume>:/volume --rm busybox sh -c 'ls -l /volume; cat /volume/<file>'
total 4
-rw-r--r--    1 root     root            13 Jan 19 11:34 file
file content

run step 3 again. It fails to find /volume/file file:
$ docker run -v <named_volume>:/volume --rm busybox sh -c 'ls -l /volume; cat /volume/<file>'
total 0
cat: can't open '/volume/file': No such file or directory

Listing docker volumes gives no <named_volume> volume, so far no /var/lib/docker/volumes/<named_volume> directory.
As for me, this goes against Docker Data Volume docs

Data volumes are designed to persist data, independent of the container’s life cycle. Docker therefore never automatically delete volumes when you remove a container, nor will it “garbage collect” volumes that are no longer referenced by a container.

$ docker version
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:08:59 UTC 2015
OS/Arch:      linux/amd64
Server:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:08:59 UTC 2015
OS/Arch:      linux/amd64
$ docker info
Containers: 8
Images: 38
Server Version: 1.9.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 54
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu precise (12.04.5 LTS)
CPUs: 2
Total Memory: 1.737 GiB
Name: drcis
ID: 7V5F:V5ON:S6MS:7UGI:3NBZ:G76R:CIIJ:N5PS:P7HD:RYAC:5H2M:VTOH
WARNING: No swap limit support

@ashumkin  The volume was deleted because you use --rm option. With --rm option, the volume will be deleted if there is no other container referenced to this volume.

@coolljt0725, thanks
here goes Docker run docs reference
But this doc (I consider it important) is missing in man docker-run which only contains

 --rm=true|false
     Automatically remove the container when it exits (incompatible with -d). The default is false.

See also #17907
The behavior you are experiencing is not the desired behavior. It was just an oversight when volume management was implemented.


py3: logs are displayed in one line

$ head /usr/bin/osbs -n
#!/bin/python3
$ osbs <..> build-logs <build-id>
2016-10-03 10:55:14,894 - osbs - DEBUG - Logging level set to debug
2016-10-03 10:55:14,895 - osbs.core - DEBUG - using kerberos authentication
/usr/lib/python3.5/site-packages/requests/packages/urllib3/connectionpool.py:838: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/security.html
  InsecureRequestWarning)
/usr/lib/python3.5/site-packages/requests/packages/urllib3/connectionpool.py:838: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/security.html
  InsecureRequestWarning)
2016-10-03 10:55:16,413 - osbs.http - DEBUG - cleaning up
2016-10-03 10:55:16,413 - osbs.core - DEBUG - fragment is 'access_token=1Ps8ugUf9zSa4k6ezhZccjMRwRwyOdxnlKVpeQD6fLE&expires_in=86400&token_type=Bearer'
/usr/lib/python3.5/site-packages/requests/packages/urllib3/connectionpool.py:838: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/security.html
  InsecureRequestWarning)
2016-10-03 10:55:17,482 - osbs.http - DEBUG - cleaning up
/usr/lib/python3.5/site-packages/requests/packages/urllib3/connectionpool.py:838: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/security.html
  InsecureRequestWarning)
2016-10-03 10:55:18,861 - osbs.http - DEBUG - cleaning up
b'2016-09-30 12:32:13,554 - atomic_reactor.inner - DEBUG - getting build json from input osv3\n2016-09-30 12:32:13,554 - atomic_reactor.plugin - DEBUG - loading plugins from dir \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins\'\n2016-09-30 12:32:13,554 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/__init__.py\'\n2016-09-30 12:32:13,554 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/exit_delete_from_registry.py\'\n2016-09-30 12:32:13,555 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/exit_koji_promote.py\'\n2016-09-30 12:32:14,570 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/exit_remove_built_image.py\'\n2016-09-30 12:32:14,571 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/exit_store_logs_to_file.py\'\n2016-09-30 12:32:14,578 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/exit_store_metadata_in_osv3.py\'\n2016-09-30 12:32:14,587 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/input_env.py\'\n2016-09-30 12:32:14,588 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/input_osv3.py\'\n2016-09-30 12:32:14,588 - atomic_reactor.plugin - DEBUG - load file \'/usr/lib/python2.7/site-packages/atomic_reactor/plugins/input_path.py\'\n

Probably related: I get
2016-10-03 10:59:37,034 - osbs.http - DEBUG - cleaning up
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/osbs/api.py", line 36, in catch_exceptions
    return func(*args, **kwargs)
  File "/usr/lib/python3.5/site-packages/osbs/api.py", line 485, in wait_for_build_to_get_scheduled
    response = self.os.wait_for_build_to_get_scheduled(build_id)
  File "/usr/lib/python3.5/site-packages/osbs/core.py", line 631, in wait_for_build_to_get_scheduled
    build_response = self.wait(build_id, BUILD_FINISHED_STATES + BUILD_RUNNING_STATES)
  File "/usr/lib/python3.5/site-packages/osbs/core.py", line 585, in wait
    for changetype, obj in self.watch_resource("builds", build_id):
  File "/usr/lib/python3.5/site-packages/osbs/core.py", line 560, in watch_resource
    j = json.loads(line)
  File "/usr/lib64/python3.5/json/__init__.py", line 312, in loads
    s.__class__.__name__))
TypeError: the JSON object must be str, not 'bytes'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/osbs", line 11, in <module>
    load_entry_point('osbs-client==0.31', 'console_scripts', 'osbs')()
  File "/usr/lib/python3.5/site-packages/osbs/cli/main.py", line 697, in main
    args.func(args, osbs)
  File "/usr/lib/python3.5/site-packages/osbs/cli/main.py", line 289, in cmd_build
    build = osbs.wait_for_build_to_get_scheduled(build_id)
  File "/usr/lib/python3.5/site-packages/osbs/api.py", line 47, in catch_exceptions
    raise OsbsException(cause=ex, traceback=sys.exc_info()[2])
osbs.exceptions.OsbsException: TypeError("the JSON object must be str, not 'bytes'",)

when a build is started

Does this only happen with Python 3?

Yes, works fine in py2

Same with me

My fault - I had a version with PR #458 installed, this is the only version I can reproduce the issue.


[Observability] Add http base url tag to observability information

Purpose

Add base URL tag to observability information for HTTP client

 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.

Codecov Report

:exclamation: No coverage uploaded for pull request base (observability-improvements@76daa19). Click here to learn what that means.
The diff coverage is n/a.

@@                      Coverage Diff                      @@
##             observability-improvements   #21910   +/-   ##
=============================================================
  Coverage                              ?   19.11%
=============================================================
  Files                                 ?       56
  Lines                                 ?     1533
  Branches                              ?      235
=============================================================
  Hits                                  ?      293
  Misses                                ?     1224
  Partials                              ?       16

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 76daa19...6adb5dc. Read the comment docs.


lang: discussion on #[account] macro renaming

one is for usage with Account<'a, T>, one is for constraints. a bit confusing for new users. not only that but even if we just had the macro inside deriveAccounts, we could maybe find a more descriptive name for it. how about #[constraints(..)] which would match what we use internally in the parser and generator too

Can confirm as a new user that this was confusing 👍


Prevent infinite read loop in tweepy Stream

I have noticed that my twitter streaming programs using tweepy (3.2.0 with requests 2.4.3) have been going into an infinite loop after a couple of days running. They seem to get stuck in the ReadBuffer.read_line() method. From breaking into it with a debugger, it looks like the underlying raw stream (in the ReadBuffer this is self._stream) is closed (self._stream.closed is True).
I am not certain how the stream gets closed, but probably there is a network glitch or Twitter just booted me randomly. I am surprised that no exception gets thrown from requests when you try to read from a closed response, but I don't know the library that well, so maybe this is intentional.
In the stream read loops in stream.py, there is currently only one check if the underlying stream has been "closed" (line 337), and it is actually outside the read loop. I looked back at the history of the file and found in #400 that before switching to the requests library, there were checks for isclosed() all over the place, and after there was only the one.
Anyway, to try and prevent this from happening, I added checks to make sure the response stream is still open in the read loops within the ReadBuffer class, as well as in Stream._read_loop() method. I also updated line 337 at the bottom of the _read_loop() to use resp.raw.closed instead of resp.raw._fp.closed() since this seems like it is supposed to be private API.
I added a test in the TweepyStreamReadBuffer class that mocks a closed stream with no content available and then tries to call read_line() on it. Before I modified stream.py this test failed because read_line() looped infinitely. Now read_line() returns None, which hopefully is the desired result in this situation. Note that I had to do some extra work to block a true infinite loop inside the test, hence all the extra complexity there.
I don't know if I fixed this the best way, but the problem is pretty serious so I hope this can be fixed and released quickly. Thank you!

Looks good to me. :+1:  Thanks!


Cannot delete project_roles resource

DELETE on e.g. /api/project_roles/168 returns a 404.
This isn't in the API docs. Should project roles be deleted some other way?

This resource can be changed to support real deletes now. The original implementation asked you to update the resources to have an empty roles array, but, with the way roles are implemented now, there's no reason not to make it work right.


feat(types): add return type for withNamespaces function

Type checking does not work bacause of return type any of a withNamespaces function.

Type casting helped, but it's not the correct behaviour:

Thanks @prokopsimek!

@prokopsimek, I'm not able to use withNamespaces as a decorator with those types :\

@felixmosh I'm sorry, my mistake - fix is waiting to merge - https://github.com/isaachinman/next-i18next/pull/239
@felixmosh Please try the pull request branch and let me know.

@prokopsimek @felixmosh Hey guys - apologies. I think part of the problem here is that I am not yet a TypeScript user of this package.
@prokopsimek Can you please help review #239?

@prokopsimek, the extend is not the issue when you are using withNamespace as a decorator.
The issue is the type of the component

@felixmosh I'm going to fix it.

Maybe we need just another interface (as interface overload)

@felixmosh I'm going to fix it.

export class CustomerCard extends React.Component<ICustomerCardProps> {
}


Add an optional custom delimiter for arrayToString()

This should allow more flexible version of the functions

Thank you for PR!


KDE doesn’t render many of the nerd-font glyphs

Describe the bug
I’m on NixOS 23.05 and found a strange issue where KDE (QT?) based apps don’t display many nerd-font glyphs properly, e.g. those suggested in the starship manual. It’s only in KDE/QT apps, and only on NixOS (KDE Neon / Kubuntu work fine)
The font I use is “MesloLGSDS Newd Front Mono”
Chrome displays them just fine as you can see below (at least I do)
💨🕙💦🦬🍞✨🦕🐋🔮🇬🌱

GTK-based app have no issues as well. Here is tilix terminal for example:

But KDE/QT based stuff struggles. Here is how I see it in the konsole (Note the rectangles instead of glyphs)

I looks like NixOS-specific issue because it all works just fine in KDE-neon running in Virtualbox (KDE 5.27 on Wayland):

Same issue happens with kate as well as any QT app (Dolphin, klipper, etc.)

All I do in confugration.nix is
services.xserver.displayManager.defaultSession = "plasmawayland";
services.xserver.desktopManager.plasma5.enable = true;

Notify maintainers
CC @ttuegel  @nyanloutre
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.37, NixOS, 23.05 (Stoat), 23.05.1622.c99004f75fd`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `"home-manager-23.05.tar.gz, nixos-23.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/kde-doesnt-render-nerd-font-glyphs/30153/2

Fixed by applying font configuration as mentioned here: https://github.com/NixOS/nixpkgs/issues/86601#issuecomment-757959059.
Though I understand the concerns why it's not the default, that was a hard one to dig out.


Make bash scripts more reusable

Scripts to create and destroy clusters reuse code often. A single scripts/ folder should be created and hold multiple short bash scripts that can be reused to create multiple versions of the cluster (e.g. Docker Desktop vs EKS, Helm vs Kubectl, different app installations like ArgoCD, Prometheus + Grafana, Ingress NGINX, AWS Load Balancer Controller, etc.)
scripts
├── aws
│   ├── delete
│   └── deploy
├── helm
│   ├── install
│   └── uninstall
└── kubectl
    ├── apply
    └── delete

https://github.com/CheriseCodes/ai-flash-cards/pull/114


Version 1.9.8: unfixed numpy from 1.22

I removed the explicit dependency on numpy 1.22 and successfully tested the new version on Windows and Linux.
At the time of writing Google Colab uses numpy 1.23 and numpy 1.26 is common, both have been tested with.
I fixed some bugs and inconsistencies in distance and window. Rigorous testing would require major changes in the examples.

@jeremitu Thanks for this. I am currently working on something else so it will take me some time before I can merge this PR and regenerate the wrapper binary to support latest colab NumPy. But I'll do it as soon as I can.


Angular 6 support

Angular 6 is about to have the stable version.
There are some changes that need to be done in order to this package support it.
I'm going to list the changes that I see:

[ ] Change peer dependencies of angular packages to ^6.0.0
[ ] Change RxJS dependency to ^6.0.0 (or use rxjs-compat it still want to support rxjs5)

Angular 6.0.0 is live today.

Already work started. Track patch-1 branch for updates.

Hey @Sibiraj-S, do you need help with update to v6?

Thanks @ssuperczynski . Just waiting for ng-packager to release its final version. The rest is done.

Hey @Sibiraj-S looks like ng-packager has released 3.0.0

Thanks @headly48. I will look at it

@Sibiraj-S Why does it take so long?

@Sibiraj-S We are waiting for this release.

I added the package rxjs-compat and now everything works without errors.
Angular CLI: 6.0.3
Node: 8.11.2
OS: linux x64
Angular: 6.0.3
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.3
@angular-devkit/build-angular     0.6.3
@angular-devkit/build-optimizer   0.6.3
@angular-devkit/core              0.6.3
@angular-devkit/schematics        0.6.3
@ngtools/webpack                  6.0.3
@schematics/angular               0.6.3
@schematics/update                0.6.3
rxjs                              6.2.0
typescript                        2.7.2
webpack                           4.8.3

If anyone interested, I just published fork of this library to the npm as ngx-editor2 with angular6 support.
See https://github.com/ssuperczynski/ngx-editor

@Sibiraj-S Can you please announce when will you merge this branch with master?.
Please update the status and let us know if help is needed.

@ssuperczynski fork is not stable, popup hovers for font, image, link insert, etc. are not working at all.

@kolkov Nice! The only thing i miss in your README is how to configure toolbar. Is this possible?

Sorry everyone for the delayed response. I was too occupied in setting up a product release. I will start working on it once it is completed. You can expect a release by end of this month or by mid of next month. But for now, I can't touch this.
Thanks for understanding.

Checkout V4


[FLINK-23242][docs-zh] Translate the page of "Handling Application Parameters" into Chinese

What is the purpose of the change
Translate the page of "Handling Application Parameters " into Chinese
The page url of "Handling Application Parameters" is https://ci.apache.org/projects/flink/flink-docs-release-1.13/zh/docs/dev/datastream/application_parameters/.
The markdown file can be found in flink/docs/content.zh/docs/dev/datastream/application_parameters.md in English.
Brief change log
Translate 'flink/docs/content.zh/docs/dev/datastream/application_parameters.md'.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no
Documentation
Does this pull request introduce a new feature? no
If yes, how is the feature documented? not documented

@PatrickRen   hello,Could you help me review my PR in your spare time? thank you !

@PatrickRen  Thank you for your valuable comments. I have made some modifications according to your comments.

@wuchong   hello,Could you help me review my PR in your spare time？if there is some problem,please tell me!Thank you!

@wuchong  hello,Jark,if you have some time,could you help me view my translation for the page of "Handling Application Parameters " . Thank you a lot !

@PatrickRen , do you have other concerns about this PR?

According to the translation specifications, it would be better to use free translation instead of literal (意译优于直译) if the literal translation is hard to understand or against the habit of Chinese.
I think the order of words is acceptable, just a suggestion 😄

According to the translation specifications, it would be better to use free translation instead of literal (意译优于直译) if the literal translation is hard to understand or against the habit of Chinese.
I think the order of words is acceptable, just a suggestion 😄

@PatrickRen  Thank you very much for your comments and review.  @wuchong  Where else do you think can be modified?


Added an example made with TemPy

Added a template in examples/templates   bootstrap_example2.py
In response to issue ALWAYS OPEN: add examples. #17

Written in Tempy
CSS , JS and background added to static folder and linked in bootstrap_example2.py so that user just have to run the file and that's it.
Passed all the test cases

Preview of the web page

Error Report

Thanks for merging the pull request :)  , I am loving TemPy and I was thinking about optimizing code in my example and also other examples , make it more pythonic , like decreasing redundant code, so it can highlight the beauty of TemPy with the power of Python ,like why it's so convenient than using HTML .


Refactor examples to include better migration logic

Something like
export class UserAccount extends Account {
    profile = co.ref(Profile)
    root = co.ref(UserRoot)

    migrate(this: UserAccount, creationProps?: { name: string; avatarUrl?: string }) {
        if (!this._refs.root && creationProps) {
            this.initialMigration(creationProps);
        }

        // Check the current version and run subsequent migrations
        if (this._refs.root) {
            const currentVersion = this.root.version || 0;
            if (currentVersion < 1) {
                this.migrationV1();
            }
            // Uncomment this to run another migration in the future
            // if (currentVersion < 2) {
            //    this.migrationV2();
            //}
            // Add more version checks and migrations as needed
        }
    }

    private initialMigration(creationProps: { name: string; avatarUrl?: string }) {
        super.migrate(creationProps);

        this.root = UserRoot.create(
            {
                // ...
                version: 0  // Set initial version
            },
            { owner: this }
        );
    }

    private migrationV1() {
        // Implement your first schema change here
        // Then increment the version
        this.root!.version = 1;
    }

    private migrationV2() {
        // Implement your second schema change here
        // Then increment the version
        this.root!.version = 2;
    }
}

trying to parse how this works (I haven't used jazz, just skimming the code):
is the idea that UserRoot holds all covalues in my app, and when displayings things, and I guard any rendering/read of  covalues on version != my version?

trying to parse how this works (I haven't used jazz, just skimming the code):
is the idea that UserRoot holds all covalues in my app, and when displayings things, and I guard any rendering/read of covalues on version != my version?

yes UserRoot typically holds all CoValues that belong to a user. The way migrations work is that they are run every time you sign up / log in / create a context - so this is your chance to arbitrarily modify the CoValues to support new features, before the app gets a hold of them.
The versioning @pax-k is using here is a manual pattern to keep track of which migrations you have run, you could also have simpler checks for presence/absence of certain fields.

Interesting! How does this resolve the issues people normally talk about with CRDT migrations (e.g. in the automerge docs?
A classic issue is a client on an older version (V1) doing an edit to a migrated (by another client) document (V2). How would that be resolved in this case?
Maybe the hope/idea is that user accounts can only be edited by a single client?


Remove ID from SubPostV2

Description

removed ID from SubPostV2 structure. The ID for each post will be looked up by MarriageIndex field. It's the index of this ID in the equivocation set (equal to the index in Marriages slice of a marriage ATX).
removed Commitment ATX from v2 nipost challenge structure.

Test Plan
n/a
TODO

[x] Explain motivation or link existing issue(s)
[ ] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

bors merge


fix(deps): update pnpm-lock file to appease installs

For some reason the changes in #53809 are breaking all CI jobs.

Ran pnpm install locally to update the lockfile.

So, this happened because another change to the lockfile came in between https://github.com/freeCodeCamp/freeCodeCamp/pull/53809 being updated and it being merged. Without requiring the PR to be up-to-date with main I'm not sure how to avoid this.
However, I think we should be okay, since pnpm defaults to --frozen-lockfile in CI (hence the errors we're seeing on main).


Suppress warnings about depending on non-stable versions of packages

The NU5104 warning in this project is a constant source of failures in stable builds of this branch. We should figure out if we're doing something wrong with this reference, but for now we can just suppress the warning. Example of a failing build: https://dev.azure.com/dnceng/internal/_build/results?buildId=522096
CC @dougbu @JunTaoLuo
@Pilchie is this alright for 3.1.3 tell mode?

F:\workspace_work\1\s.dotnet\sdk\3.1.100\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets(198,5): error NU5104: A stable release of a package should not have a prerelease dependency. Either modify the version spec of dependency "Microsoft.AspNetCore.Mvc.Razor.Extensions.Version1_X [3.1.3-servicing.20114.2, )" or update the version field in the nuspec. [F:\workspace_work\1\s\src\Razor\src\Microsoft.AspNetCore.Razor.LanguageServer.Common\Microsoft.AspNetCore.Razor.LanguageServer.Common.csproj]

https://github.com/dotnet/aspnetcore/issues/19072

Another example - https://github.com/dotnet/aspnetcore-tooling/pull/1587

Failure was a test failure

Yes, tell-mode is sufficient for this.

@dougbu are you ok with merging this change?

are you ok with merging this change?

Yes


Running this under apache?

How would I run windwalker under Apache instead of the built-in web server in php?

If you put your project at /var/htdocs/windwalker
Just enter http://localhost/windwalker/www to open windwalker.


Feature/mobile menu

The following are the points to note about this Pull Request  :

The hamburger button becomes an X for closing the menu
The menu display on clicking the hamburger menu
Once a menu item is clicked it scrolls to the appropriate section

Invalid pull request


UAT | E-filing | Navigating Across Case sections during filing

Issue:

User removes respondent
Navigates to Complainant details
The respondent details reappear

Expected behaviour:

All changes made are reflected irrespective of navigation across sections

This issue is fixed and working fine in UAT Env.


Add shim for Spark 3.1.2

Apache Spark has started publishing Spark 3.1.2 snapshots, so this adds a shim to support that version.

build

build

build


fix: schema-org regression since 1.8.0-beta.5

Environment

@nuxtseo/module v2.0.0-beta.39
unhead v1.8.0-beta.5

Reproduction
https://github.com/dargmuesli/vio/actions/runs/6699750370/job/18204497093?pr=112#step:7:1273
Describe the bug
Raising this issue quickly, can work on a full reproduction if necessary.
Updating to anything since v1.8.0-beta.5 (could be .4 or .3 instead, they're not on npm.com) makes my regression test fail with this diff:

Additional context
I'm defining schema-org like this:
const siteConfig = useSiteConfig()

useSchemaOrg([
  defineWebSite({
    description: siteConfig.description,
  }),
])

Notice that in the diff the WebSite part stays the same while the WebPage part changes.
Logs
No response

Hmm, there might be something else going on here. On static build, no og.pngs are generated as well even when pinning unhead to 1.8.0-beta.2. I'm a bit confused, but I guess my dependency pinning doesn't make incompatibilities less likely...

Thanks, investigating this

@dargmuesli is this fixed in latest? :thinking:

I think so. I'll be able to tell for sure once https://github.com/harlan-zw/nuxt-seo-kit/issues/112 is resolved.

Indeed it is! Thank you very much @harlan-zw :heart:


Multiple objective

Hi, is there a way for me to have multiple objectives. For example, maximize a set of scores and minimize volatility? Thank you!

Hi @amos-peter,
You have two options here:

define a new objective function like "scores - c × volatility" then maximise this objective. The constant c will need to be chosen depending on how you want to tradeoff the scores and volatility
maximise scores subject to a vol constraint, or minimise vol subject to a scores constraint.

Best,
Robert

Hi Robert. Thank you for your suggestion. I agree that I might need to define a function to set the percentage trade-off for multiple objectives.

Cool. Let me know if you get stuck!


Move Scheduler.usesFileSystem to SchedulerAdaptorDescription

The usesFileSystem() is adaptor specific not Scheduler instance. It should be moved to the adaptor description. This will make the Scheduler api less cluttered.

Agreed. Will fix.


Refactoring termination criterion

This PR extracts the codes on refactoring termination criteria abstraction from #214.
There changes are needed for unifying static and dynamic trajectories.
Changes are

Introduced AbstractTerminationCriterion, StaticTerminationCriterion <: AbstractTerminationCriterion and DynamicTerminationCriterion <: AbstractTerminationCriterion
Introduced FixedNSteps and FixedIntegrationTime
Refactored GeneralisedNoUTurn and StrictGeneralisedNoUTurn so that they only contains algorithm parameters but not turn statistics
Introduced TurnStatistics as suggested in https://github.com/TuringLang/AdvancedHMC.jl/pull/214/files#r467505568

Along with necessary updates in test cases and docs (+some clean-ups).

@sethaxen Can you please take a look at this PR?
I guess the TurnStatistic  is also what you wanted to introduce while doing the vec-NUTS PR IRCC.
Does what I doing here suit your usage?

@sethaxen Can you please take a look at this PR?
I guess the TurnStatistic  is also what you wanted to introduce while doing the vec-NUTS PR IRCC.
Does what I doing here suit your usage?

I'll take a look at this PR soon.

I'll take a look at this PR soon.

@torfjelde Any chance you have reviewed this PR?

@yebai I guess this PR is good to go once the CI passes.

It seems that CI is broken due to mismatched function signatures.
https://github.com/TuringLang/AdvancedHMC.jl/pull/240/checks?check_run_id=1866519262#step:5:385

Opps. I by mistake committed some temporary changes and pushed them along with the commit to adapt Tor's suggestion.
I've reverted these changes and hopefully the CI shall pass now.

@xukai92 so sorry for the late reply! I'll review this in a few hours.

@sethaxen Can you please take a look at this PR?
I guess the TurnStatistic  is also what you wanted to introduce while doing the vec-NUTS PR IRCC.
Does what I doing here suit your usage?

I don't recall adding a TurnStatistic, and I don't see anything to that effect in #228. Haven't had a chance to go through this PR in detail, but nothing looks off.


Added specific font-size for .btn-cta in the 500px breakpoint

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #37165

Thank you for the PR @Raibaz


Big Endian support

I realized that the function from_chars with the exponential notion (e.g. 1e30) with float always returns 0.
This is because this line always copies the first four bytes of uint64_t when we handle float. However, on big-endian platform, the value is stored in the last four bytes of word when we handle float.
This issue comes from https://github.com/apache/arrow/pull/8674

@kiszk Thanks for the report. We will gladly take a pull request. This being said, I do not have access to a big-endian system and I do not know how to do continuous integration tests for big-endian systems. Without proper testing in place, we cannot support big endian platforms reasonably. I believe travis added POWER support recently, but again, only little endian.

@kiszk  To be clear, you report one issue, but there might be other issues related to big-endian system. To be able to say that things work under big endian systems, we'd want to run our tests. I'll gladly take the patch you contributed to Arrow and make no fuss about it, but how do you know that it fixes all issues related to endianness?

@lemire Thank you for your comment.
Regarding testing on BE, Travis CI s390x (BE) is available as written in https://blog.travis-ci.com/2019-11-12-multi-cpu-architecture-ibm-power-ibm-z in addition to ppc64le.

In addition, if you need System z Linux environment, you may want to see https://developer.ibm.com/components/ibm-linuxone/gettingstarted/ to get a free instance for (probably) 90 days.

I will see if I can run tests under x390x.

to get a free instance for (probably) 90 days.

We really do want continuous integration support. It is not practical to claim to support a platform while only testing it sporadically using temporary access.

@kiszk  Thankfully, your pointers proved useful. It works.
I'll merge a fix soon.

Ok. I am preparing a release. It takes some time because I need to run exhaustive tests.

Thank you for taking care of both endians.


[v4-beta.19] Tabs stop working when moving from a page with tabs to another page with tabs

Bug Report
Ionic version:
[x] 4.x
Current behavior:
Navigating from a page with tabs to another one with tabs breaks the tabs. You can still click on the tabs (url also changes) but the page does nothing. It is still stuck at the default tab. I have to navigate to a page without tabs first and then navigate to my desired tab page for it to work.
Expected behavior:
Tabs should not break
Steps to reproduce:
Just have a page with tabs and navigate to another one with tabs. I use the split pane menu in my case.
EDIT:
It seems to be something related to the router outlet.

Thanks for your issue! We are aware of this problem and the good news is: We have a fix for it :) But I cannot say when the next beta will be online.
It's a duplicate of #16411 so I close this here

@paulstelzer I think it's a pretty major issue. Glad you fixed it. I think it's worth pushing a small release for it :-)

I did not fixed it, it was @manucorporat  ;) I think there will be a new beta soon


Support of prerelease 10.276

Hi, there is already a 10.276 prerelease version out, could you please integrate that?
https://foundryvtt.com/releases/10.276
Thanks

I'll try to get this out today.  There is a new configuration to support in options.json so this is a bit more than a normal version bump.
As a work-around, if you need to test before the new image is published you can manually set the FOUNDRY_VERSION environment variable to 10.276.

New protocol option in options.json
See:

https://github.com/foundryvtt/foundryvtt/issues/6506

See:

https://github.com/felddy/foundryvtt-docker/releases/tag/v10.276.0


Typo error in the definition file for DataPicker is making the prop "disabled" a required one

There is a typo that causes the "disabled" prop to be required, this in the DatePicker interface. What is written is:
disabled:? boolean;
where it should be:
disabled?:boolean;
Interrogation sign before two points.

#2132


New client doesn't appear to use $HOME environment variable

GHA (GitHub Actions) sets HOME to /github/home
In a GHA script I do
cat << EOF > ~/.transifexrc
[https://www.transifex.com]
rest_hostname = https://rest.api.transifex.com
token         = $TRANSIFEX_API_TOKEN
EOF

Meanwhile the current tx client (1.4.0) is actually looking at /etc/passwd to find home directory.
(from an strace)
openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/root/.transifexrc", O_RDONLY|O_CLOEXEC) = 3

End result is that I write a config but the client doesn't see.

Hey @Docteh,
Our latest release v1.4.1 fixes this issue.
Thank you for bringing this to our attention.


PEX stopped loading in when I had added new permissions(pastebin updated)

Can anyone please tell me what the problem is. Here is what I have in my .json
https://pastebin.com/rnVndm5Y

don't open a new issue update the one you already had