Added some more interractions with API

Hey @MongkonEiadon
Here are some of the improvments I have made during the past few days.
I was getting excited to directly offer a pull request to the master branch, sadly, a lot got broken by your recent changes.
Anyway, you can still benefit from these changes if you feel like to.
I may have change some of your logic regarding subscribe request/sendmessage. I have seen  also that some that some of the improvements I thought of, were already implemented (like the microservice tag in requests)
This PR should normally be pullable from commit c42f2521e956b52e78c57d4dc578d9c7e7e7bbb7.
Regards

Thanks I'll have a look

I'll investigate one by one and pick some from your, Thanks for your help


Add Rhyolite.Frontend.Modal.*

Add Rhyolite.Frontend.Modal.* modules for conveniently creating modals that do not require the use of z-index to position correctly.

We've been using this code almost verbatim for a long time without any issues. Getting your constraints right for ModalM can be slightly tricky, but for good reason.

Examples:

runModalT
tellModal Notice the constraints on that function have MonadRhyoliteFrontendWidget Bake t (ModalM m), HasModal t m.
Some modal builders that apply different styles

Now with a nice Prerender instance! Thanks @cgibbard for helping me sort that out...it was gnarly!


specify git workflow

@jrawbits requested we use an agreed upon git workflow. He suggested reviewing this tutorial as well.

This is now specified here Development-Guidelines


Ionic2 ion-slides didChange event not triggering if animation interrupted with mouse/touch

Platform: browser
version: ionic-angular 2.0.0-beta.7
Short description of the problem:
When using the component ion-slides, adding a handler for the didChange event, the event didChange triggers when the user swipes to change of slide and waits until the end of the animation, but if stopping the animation with tap/press/start swiping, but still releasing on the new slide, the event didChange does not trigger.
Example use-case: I change of slides quickly and don't wait until the animation is finished before trying to go to the next slide. (In my case, slides are used to make a calendar, sliding to go to the next day).
What behavior are you expecting?
didChange always triggers when a slide changed, even if the animation was paused by the user in the middle of the change.
EDIT: when slides are quickly swiped without waiting the end of the animation, it would still trigger for each slide. Maybe not be obvious, but it would make events consistent regardless of how fast the user is swiping.
Steps to reproduce:

Create a new Ionic 2 app
in a page, insert a slider like <ion-slides (didChange)="logMe($event)"> with a few slides
swipe and pause the animation by tapping the screen. When releasing and finishing the animation, the event is not triggered.

Which Ionic Version? 2.0.0-beta.7
Plunker that shows an example of your issue
http://plnkr.co/edit/c7N6KXP8vAkYgh5cZNo4?p=preview
Click the Thanks! button, open the browser console and slide as described before. Logs are missing if the animation is paused.
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.2.0
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.7
Ionic CLI Version: 2.0.0-beta.25
Ionic App Lib Version: 2.0.0-beta.15
OS: Windows 7 SP1
Node Version: v6.2.0
Thanks for the great work around Ionic btw!

Hi! Any update about this issue? Will it be considered in a future release? Thanks a lot.


Responsive Page

Responsive Page
To do:
Add Bootstrap to website to enable Bootstrap components and CSS.
Notes:

High Priority
Bootstrap will provide an easy way to address multiple issues regarding responsiveness.
Included in initial sprint in order to set up website for custom styling (responsive images) and components (cards, columns, etc).

Size:
Small
User Story: Responsive Page

Branch name: responsive-page
Bootstrap was already imported into the project via CDN. I added img-fluid to the placeholder images preemptively for when the images are swapped out for the poem related images.
Columns will stay at the default until content is added. We can discuss how we want the layout to be e.g. how many poems will be aligned for different view ports before they start to stack on top of each other.


Train content misaligned in inventory tab

Describe the Bug
Train contents in inventory tab seem to be aligned to the right, causes misalignment on long station names, see image.

Tell me if a savegame is really needed.

Geez, that's a long station name, I would recommend shortening it.
I'll fix this in v0.3, which will have some other GUI improvements.

At long last, this is fixed for the next release.


Convert to Actions

Changed

Convert to actions
Change file permissions from 644 to 664

At this point in time, I'm not certain what else to do and if the mode test is worthwhile.


Storage+BigQuery.import notFound errors

I am uploading files to Google Cloud Storage and then importing them to Big Query and am seeing an intermittent notFound error during the import job.
Here is a simplified version of how I am streaming files to GCS:
rs.pipe(bucket.file('[filename]').createWriteStream({
  metadata: {
    contentType: 'text/csv',
    metadata: {
      custom: 'metadata'
    }
}).on('finish', function () {});

After file streaming has finished, the next step is importing to Big Query:
bigQuery
  .dataset([datasetId])
  .table([tableId])
  .import([bucket.file('[filename]'], {
    createDisposition: 'CREATE_IF_NEEDED',
    writeDisposition: 'WRITE_TRUNCATE',
    sourceFormat: 'CSV',
    schema: {
      fields: [fields array]
    }
  }, function (err, bqJob) {
    // Executes successfully
  });

I am seeing the error in the response I get from job.getMetadata():
bigQuery.job(bqJob.id).getMetadata(function (err, response) {});

response.status.errorResult.message: Not found: URI gs://[bucket]/[filename]
response.status.errorResult.reason: notFound
response.status.errorResult.errors: [{"reason":"notFound","message":"Not found: URI gs://[bucket]/[filename]"}]
After receiving this error, I have confirmed that the file in question does exist in GCS. Can there be some lag between when a stream has finished and when the file is actually available? If so is there a better way to know when the file(s) are ready for import into big query?
To be clear, this flow of events usually completes successfully, but I am intermittently seeing the notFound error. I would like to track it down or at least find a way to avoid it. Is this a known issue? (I haven't been able to find mention of it yet). Is it possible that rate limiting it occurring and causing this error to be generated?

Thanks for the detailed report. I'm putting together a sample script to try to reproduce.
As a quick thing that likely doesn't relate, I believe you can make the following change to your code:
.import([bucket.file('[filename]'], {
-   metadata: {
-     createDisposition: 'CREATE_IF_NEEDED',
      writeDisposition: 'WRITE_TRUNCATE',
-     sourceFormat: 'CSV',
      schema: {
        fields: [fields array]
      }
-   }
  }

The metadata property can be removed, and the other values I removed are also the default values.
I'll report back after I have a chance to try to reproduce.

Ah yeah, my mistake on including the metadata: {} wrapper. I have not been using it that way, just a copy paste+simplification mistake. I will update my comment. Thanks for the suggestions.

According to this doc, once a file upload is complete, it is immediately available. That would mean the only way BigQuery would get a 404 is if you received a "false finish" from file.createWriteStream, or somewhere else in the stack jumped the gun.
I put together a sample repo I've been using to try to reproduce. So far, no errors. Can you check this out to see where it might differ from your usage? Feel free to PR to make it more likely to fail.

Thanks for your efforts on this, Stephen. I just solved a bug in my code that was causing the import to happen before all files were finished streaming. From what I was seeing it's possible that the notFound error was happening from something unrelated, but I haven't been able to reproduce it. I will reopen if I run into the issue again. Thanks again!

Phew! No problem, glad you found the :bug:


[build] [could-not-resolve-reference] - Could not resolve reference to element-mixin when using Polymer.mixinBehaviors()

Description
Receive warning when building with polymer-cli v1.8.0 on polymer 2.0 project with the following class declaration:
/**
 * CustomValidator
 *
 * @polymer
 * @customElement
 * @extends Polymer.Element
 * @appliesMixin Polymer.IronValidatorBehavior
 */
class CustomValidator extends Polymer.mixinBehaviors([Polymer.IronValidatorBehavior], Polymer.Element) {
  // ...
}

Steps to reproduce
N/A
Expected result
No warning
Actual result
Warning as follow:
warning [could-not-resolve-reference] - Could not resolve reference to element-mixin

Any updates on this?

Currently I am reverting to Polymer CLI v1.6 until the problem is resolved.

It's quite a no go if you have a big app and your pipeline fails (as it should) if there are linter errors. I'd really appreciate a fix...

Still nothing?

Polymer 3 with cli 1.9.*....I am hitting this also


Add tests for taproot descriptors having deep scripts trees.

As we know that there is a limit to the depth of the script tree in taproot specification.
These tests try to create script trees with depths 127 and 128. The limit is 128 (i.e a script tree of depth 129 is invalid) for valid trees.
Another test with a complete tree having 128 leaves has also been added.
A simple python script was used to generate these test cases, here it is.

Can you make sure there is only commit here? @kanishk779. It might require you to read online about git squash and fixup.


Strange lint warnings about missing C:/github/angular.in-memory-web-api/src//src/index.ts

If I switch to this new in-memory-web-api library, I get a strange lint warning when running "ng test" on my mac:
WARNING in ./~/angular-in-memory-web-api/index.js
Cannot find source file 'C:/github/angular.in-memory-web-api/src//src/index.ts': Error: Can't resolve './C:/github/angular.in-memory-web-api/src//src/index.ts' in '/Users/xxx/mytestproject/node_modules/angular-in-memory-web-api'
 @ ./src/app/shared/services/test.service.spec.ts 6:34-70
 @ ./src \.spec\.ts
 @ ./src/test.ts

The source file that it can not find is "C:/github/angular.in-memory-web-api/src//src/index.ts" and is unrelated to my project and even my platform (I am using Mac - not windows).

Works on our machines. Please provide a repro. Make sure you've deleted the only package and installed the new in node_modules

Here is a reproducible hello-world sized example. Unzip, "npm install" and "ng test" on a Mac to reproduce. You might also be able to reproduce on a PC (not sure) but in this case you need to make sure you have folder on it called "C:/github/angular.in-memory-web-api" !!
bugdemoproject.zip

You have some kind of loader problem that I can't see. I'm not using the CLI so I personally don't know how to configure it properly. Something is clearly wrong if your app is looking for ../src//src/....
This looks like a compile problem not a lint problem. But what do I know?

Are you sure, it is not because there is something wrong with your npm package as this is the only package that the angular cli tools complain about. The bug demo project is produced by "ng new" with just a few additions. If you are sure, I can report a bug with the "ng tools instead" ?

Just to emphasise, I am using a standard out-of-the-box configuration produced by the angular cli tools. If it is reproducible on your machine (i.e. not something about nodejs local to my machine) than it is strange that the problem only happens with your npm package I think.

Looks like the . typo is in all the map files in the node_modules/angular-in-memory-web-api folder. I think it should be a - and there is also that C:/, I am not sure it should be there (since i'm on a mac), but i'm new to npm so I don't want to say something wrong.

@wardbell I can also reproduce this problem using the new version 0.1.9. I have no idea how to fix it myself so I would highly appreciate a fix.... Where you able to reproduce the problem in bugdemoproject.zip on your machine or do you need more info from me here ?

I'm sorry but this project has not been vetted with the CLI and the tiny team on this repo doesn't have resources at the moment to square with the CLI.  Maybe you can cross-reference this with an issue on the CLI repo so that someone on that much larger team can help.

I think @igalil is on to the problem. I am running into the same thing when using webpack because the sourcemaps have hard coded values. Look, for example, at http-status-codes.js.map and you'll see a hardcoded value of 'C:/github/...'. I believe sourceRoot in tsconfig.json needs to be updated to not be ./src. For now to work around the problem, I'm just excluding the project for webpack so it avoids the errors.

I have this problem with webpack. Please help.

I have fixed it by adding to exclude session of 'webpack.test.js':
exclude: [
// these packages have problems with their sourcemaps
helpers.root('node_modules/angular-in-memory-web-api'),
....


Inconsistent behaviour with google.protobuf.Struct

Serializing and deserializing google.protobuf.Value of kind Struct will flatten the struct's inner fields field.
However, serializing and deserializing google.protobuf.Struct directly will not flatten the fields field.
This difference can be worked around most of the time, but it makes the usage not very ergonomic when trying to work with a collection of Struct.
This can be easily resolved by adding .field_attribute("google.protobuf.Struct.fields", "#[serde(flatten)]") to the prost build config
(This is for prost-wkt-types)

Thanks for raising this issue @tcohen01! It's definitely important that behaviour is consistent. So you recommend adding the above field_attribute to the wkt-types/build.rs, correct?

Yes, thanks! That should make the struct serde behaviour identical to how it's manually implemented for google.protobuf.Value;
https://github.com/fdeantoni/prost-wkt/blob/0e5a8d7811a1ca0104bed5b48b3e16a3964ffd17/wkt-types/src/pbstruct.rs#L201-L207
https://github.com/fdeantoni/prost-wkt/blob/0e5a8d7811a1ca0104bed5b48b3e16a3964ffd17/wkt-types/src/pbstruct.rs#L294-L304
https://github.com/fdeantoni/prost-wkt/blob/0e5a8d7811a1ca0104bed5b48b3e16a3964ffd17/wkt-types/src/pbstruct.rs#L136-L142
As it already logically flattens the fields field as seen here.

Oh, I actually wonder if the same needs to be done with ListValue and its values field?
I've not really used this myself, mainly seen a bunch of repeated usage questions regarding Json::Value to google.protobuf.Struct deserialization in Rust and Tokio's discord servers and figured this is common enough to raise it as an issue.

Oh, I actually wonder if the same needs to be done with ListValue and its values field?
.field_attribute("google.protobuf.ListValue.values", "#[serde(flatten)]")

That unfortunately won't work as serde(flatten) only works on structs or maps. In any case, I decided to implement the Serialize and Deserialize traits manually instead, and share it with the Value serde implementation. This way there should be no inconsistencies between Struct/ValueList and Value. I already merged the changes into master branch. Hopefully this addresses the problem correctly, but if not do let me know!

Checked both Struct and ListValue, all seems to be working fine now!
Also still had a little test snippet on this function I had written to help a rust user on discord:
fn serialize_rows_to_protobuf(
    rows: Vec<serde_json::Map<String, serde_json::Value>>,
) -> Result<Vec<prost_wkt_types::Struct>, serde_json::Error> {
    rows.into_iter()
        .map(|row| {
            serde_json::from_value(serde_json::Value::Object(row))
                //.map(|fields| prost_wkt_types::Struct { fields })
        })
        .collect()
}

Before it only worked as intended when uncommenting the commented line, now it works both commented and uncommented.
Thanks for the fixes!


VirtualMachineInstance.status.guestOSInfo switch between having a value and empty value

What happened:
VirtualMachineInstance.status.guestOSInfo always empty,but somtimes which have a value, the vm's status is running.
status:
  activePods:
    42a8a6d4-bbe1-4ad1-9746-fc7ee4c69ae3: xxxxx
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2023-11-01T09:07:51Z"
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: null
    status: "True"
    type: LiveMigratable
  - lastProbeTime: "2023-11-01T09:08:24Z"
    lastTransitionTime: null
    status: "True"
    type: AgentConnected
  - lastProbeTime: null
    lastTransitionTime: "2023-11-01T09:08:37Z"
    status: "True"
    type: AccessCredentialsSynchronized
  guestOSInfo:     #**this filed always empty**
    id: centos
    kernelRelease: 3.10.0-1160.88.1.el7.x86_64
    kernelVersion: '#1 SMP Tue Mar 7 15:41:52 UTC 2023'
    name: CentOS Linux
    prettyName: CentOS Linux 7 (Core)
    version: "7"
    versionId: "7"
  interfaces:
  - infoSource: domain, guest-agent
    interfaceName: eth0
    ipAddress: xxxxx
    ipAddresses:
    - xxxx
    - xxx
    mac: xxxx
    name: xxx
    queueCount: 1

What you expected to happen:
the running vm has a correct VirtualMachineInstance.status.guestOSInfo  field
How to reproduce it (as minimally and precisely as possible):
Steps to reproduce the behavior.
Additional context:
Environment:

KubeVirt version (use virtctl version): v0.59.0
Kubernetes version (use kubectl version): v1.23.4
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): CentOS Linux 7 (Core)
Kernel (e.g. uname -a): 5.14.0-1.0.38.x86_64
Install tools: N/A
Others: N/A

Hi, do you mean that while running it has a value but otherwise this is empty?

Hi, do you mean that while running it has a value but otherwise this is empty?

the vm's is always running, but when i run kubectl get vmi xxx -o yaml,sometimes the guestOSInfo is emtpy

you can use the command of virtctl guestosinfo <vm>  to check it.

you can use the command of virtctl guestosinfo <vm> to check it.

emm,virtctl guestosinfo <vm> always the correct os info,but at sametime i use kubectl get vmi xxx -o yaml got a empty os info.

https://github.com/kubevirt/kubevirt/blob/v0.59.0/pkg/virt-launcher/notify-client/client.go#L430-L435

yes , that would be ok.

This has been fixed by https://github.com/kubevirt/kubevirt/pull/10419 , please recheck this on a latest version.


⚠ Bofrost.be has degraded performance

In eab8b91, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2552 ms

Resolved: Bofrost.be performance has improved in 454d0a4.


⚠ Bofrost.fr has degraded performance

In 94036f2, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 908 ms

Resolved: Bofrost.fr performance has improved in f69589c.


fmSetupAssistant: UX: Duplicate entry

A function to duplicate an entry would be useful, which

sets the sort value correctly
adds " Copy" to the path name

Done.

Duplicate Config button on the popup menu
Duplicate Setting button in the settings definition panel


Bump version to 0.11.2

Bumping to a new version so the web interface could start using the latest functionalities.
Requires #483 to be merged first.

@OscarWang114
Feel free to go ahead since https://github.com/neulab/ExplainaBoard/pull/483 has been merged.
Also, one very important thing is that there are usually some potential incompatible issues in the ExplainaBoard web due to the upgrade of Explainaboard SDK. So it would be nice if you can perform some lightweight usability tests on some tasks after you upgrade the SDK version number in explainaboard_web repo.
Here is one example of the usability test: https://github.com/neulab/explainaboard_web/issues/311
You don't need to test all, maybe select some typical tasks first.

@pfliu-nlp : FYI, we have a checklist here https://github.com/neulab/explainaboard_web/wiki/Pre-release-Checklist
You can add things to it if you'd like. It might be nice to also automate some of these things if possible.

Aha interesting and thanks for the pointer, I will refine it later.

Just finished class, thanks for merging the PR!
The checklist is definitely helpful. I'll use it to check the next release and see if there's anything I'd like to add as well.


1909 support

I'm having an issue with a Xamarin UWP app on a device running 1909 which works fine on 1903. I can't rollback to 1903 because "updated more than 10 days ago". When is 1909 support being added? Still only goes up to 1903. Note: this may or may not be the reason for the issue, but hasn't been ruled out yet (it's the only lead I have at the moment though).

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

ID: fd1ff7f3-d77d-b7bd-8dfa-7f25cb0b5239
Version Independent ID: 71e57b3b-b25f-0299-2cbc-f895a98c685d
Content: Choose a UWP version - UWP applications
Content Source: windows-apps-src/updates-and-versions/choose-a-uwp-version.md
Product: uwp
Technology: deployment
GitHub Login: @hickeys
Microsoft Alias: hickeys

We are having similar issues with two of our LoB applications, runs fine on 1803, 1909 seems to be a hot mess where they don't ever start correctly.  Windows Event log shows the apps are being killed by Windows for various reads such as Hung Thread or Navigation (Hang Type).
To be fair to developers and businesses, this whole UWP thing is a good example of something extremely pointless - MS aren't willing to admit they made a huge mistake on - however are more than happy to recommend it strongly to their customers with statements like "we're all in on this [insert tech]".

@SmartmanApps So this is a Xamarin.Forms app? What's the problem you're seeing?

@SmartmanApps @bmwilson1978
We'd like to follow up on this issue, but it seems like it's a little too complex to do via GitHub. Can one or both of you email me at<EMAIL_ADDRESS>

Based on some investigations, I can confirm 1909 support. The engineering team did not see anything that would cause the issues you're describing. Since there has been no reply on this issue, I'm going to close it. Please reopen if you continue to encounter this issue.


Evaluation results on MT Bench and BBH

Hello,
Thanks for the great work! It seems that SPIN is effective in improving model performance on reasoning, math tasks (TruthfulQA, GSM8K, BB-Causal) but less so on knowledge task (MMLU).
I have a couple of questions to the authors:

on which tasks in MT Bench do you observe contributing the most to the performance gain? I guess Math, reasoning, and extraction?
1.1. Do you plan to release the responses of your MT Bench results?
have you tested on the full suite of BBH? Did you observe performance gain across all tasks or only the subsets that you reported in the paper?
The results in figure 5 is intriguing: do you have results for other HF open leader board benchmarks, i.e., mmlu, gsm8k? Do you also observe the same phenomena in these benchmarks?

I would really appreciate if the authors could kindly respond to some of my questions.
Kind thanks,
FengTing

Hi, thanks for your interest! Regarding the questions,

The detailed performance of MT-Bench is illustrated in Figure 6 of our paper. We observed notable improvements in writing, STEM, and roleplay tasks. It's important to note that these performance gains vary depending on the specific SFT dataset that SPIN started with. Our use of the ultrachat dataset, which contains user-gpt dialogues and may be limited in certain fields, may explain the lesser improvement in other tasks.
1.1. Yes, we would release the MT Bench responses in the near future.
Our study primarily concentrated on the Open LLM Leaderboard and we extended our analysis to additional tasks like MT Bench and selected BBH tasks. The choice of BBH tasks was random. Given the specific focus of our SFT dataset, it's possible that our model may not show improvements in certain tasks that are in fields not related to or covered by the SFT dataset.
Yes, we observed the same for the other tasks, but did not included all of them at the time. These additional figures were not included in the current paper but will be incorporated in our next revision.

We appreciate your interest and hope this clarifies the questions :)


vim will not correctly processs  or

vim 8.1.204 on win10 amd64.
Start vim, even vim -N -u NONE
Enter insert mode, and hit  or  and strange characters appear on screen

Reproduced on Win32 CUI, not on Win32 GUI and Cygwin.
Typing F9 inputs literal text <F9>, but typing F11 inputs 0xCE 0x85.

I also encountered this problem.

What are 'term' 'ttybuiltin' and <F11> set to in the problematic console terminal?

        :verbose set term? ttybuiltin? <F11>?

(with the question marks)

Does it change anything if you toggle ttybuiltin as follows:

        :set invtbi

then retry using the F11 key?
Best regards,
Tony.

:set invtbi doesn't work.

Well, apparently your terminal sends something else for <F11> than what Vim thinks it ought to.
Try adding to your vimrc the following snippet:
if &term == 'win32'
    set t_F1=<Char-0xCE><Char-0x85>
endif

or, if it doesn't work, then replace it (after the place where you set 'encoding' to UTF-8) by
if &term == 'win32'
    let &t_F1 = "\u0385"
endif

(it is important to use double quotes around the \u0385). If it still doesn't work, then we'll have to find out exactly what your terminal sends for <F11>. For that, open an empty buffer by :new, go to Insert mode, and then hit Ctrl-Q followed by F11 (I'm saying Ctrl-Q rather than Ctrl-V because if you source mswin.vim your Ctrl-V will have been remapped to the paste operation while Ctrl-Q, a synonym, will usually have been left untouched). Then, after going back to Normal mode, place the cursor over each of the characters which (hopefully) will have been inserted in the buffer and do ga over each of them.
Best regards,
Tony.

Two snippets don't work.

if &term == 'win32'
set t_F1=<Char-0xCE><Char-0x85>
endif

Does not work.

if &term == 'win32'
let &t_F1 = "\u0385"
endif

works kind of, but only with the default locale of latin1 (not with utf-8). With Latin 1, pressing F11 results in (starting with vim.exe --clean in a cmd with codepage 850):

with encoding=utf-8 started with (vim.exe --clean --cmd ":set enc=utf-8"), does not change anything:

I have no clue, what terminal key code the win32 console expects.

I posted some more information here: https://groups.google.com/d/msg/vim_use/LS3_-hzkQjA/pBKlVa2mBgAJ

Can you please check, if this is fixed by https://github.com/vim/vim/commit/2bc152ab53c4b01072edf6ec2ff61e504cb03cbe (e.g. patch 8.1.0451)?

fixed by 2bc152ab53c4b01072edf6ec2ff61e504cb03cbe


pe-addlicense

@Macuyiko I will go ahead and merge this, but since this is about the license, please make sure you review it.


linuxPackages.r8168: 8.052.01 -> 8.053.00, remove broken

Description of changes
Bumping to latest r8168 module from mirror. Removed maintainer per their request and updated broken to match module's current compatibility with kernels up to 6.8.
Successfully built this module (without my changes) and applied it to an install (using allow broken) and it worked well. I'm not confident in the syntax I used for the broken setting, nor was I able to build this change locally (almost certainly because I don't know clearly what I'm doing - I tried nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD -p r8168" for example and it hung my terminal for a while then subsequently crashed)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@timokau would you mind reviewing? not sure if I'm missing something or if there's more I can do to help move this along.

thanks timokau. after following the download link(s) through realtek I diff'd with the mtorromeo repo:
> diff -r r8168/ r8168-8.053.00
Only in r8168/: .git


Release SQL JDBC driver

Is your feature request related to a problem? Please describe
JDBC driver was never released on Maven. The one published on artifacts page is a bit old already and should be updated.
Describe the solution you'd like
Publish most recent JDBC driver on Maven and on artifacts page.
Driver build is available as GHA artifact: https://github.com/opensearch-project/sql/actions/workflows/sql-jdbc-test-and-build-workflow.yml?query=branch%3A2.x
Describe alternatives you've considered
N/A
Additional context
https://github.com/opensearch-project/opensearch-build/issues/794
https://github.com/opensearch-project/sql/issues/401
CC: @anirudha

Hey @Yury-Fridlyand we have some publish scripts handy, could use them, but quick question, do you have a proper project or gradle task when executed publishes SQL JDBC driver jar to local maven repo (~/.m2) with proper maven group Id like org.opensearch.driver? may be if we have that task or job we can use it part of the CI to publish it to actual maven repo with right creds.
Example for opensearch-job-scheduler plugin zip
<groupId>org.opensearch.plugin</groupId>
<artifactId>opensearch-job-scheduler</artifactId>
<version><IP_ADDRESS></version>

Thank you

Thanks, I will have a look and make all preparations. We need to do few minor fix in the driver prior to release.
I'll ping you once everything will be ready.

@prudhvigodithi yes there's a publishToMavenLocal task in jdbc driver.
One quirk with JDBC driver is that it can build two jars -- normal one, and one with all dependencies shadow copied. The second one is what can be used right now by just dropping the jar in the classpath. We want to publish the first one.

Notes from our discussion.
Examples to follow:

opensearch-java publishes with Jenkins like this.
opensearch-testcontainers publishes with Jenkins like this.
JDBC driver will be set up similarly.

Someone with   admin permissions on sql repo will need to setup a webhook used by Jenkins to publish releases when a release tag is made.

@peterzhuamazon since JDBC driver is in the sql repo, what git tag pattern should its releases have? The Jenkins pipelines currently assume refs/tags/v

Also @peterzhuamazon do you know if JDBC driver will be kept in the plugin repo or split out? The discussion happened here but it's not clear what will happen to drivers.
If JDBC driver stays in a monorepo with something else, will there be one Jenkinsfile for each product in the repo or one Jenkinsfile for all of repo?

Hi @MaxKsyunz I added several comments to @Yury-Fridlyand PR there.
Would love to discussion more later on the strategies of the repo.
Thanks.

@MaxKsyunz Is there an issue on extracting the JDBC driver into its own repo with pros/cons already? Care to open one so we can discuss that there?
My uneducated opinion is that it looks like the JDBC driver should follow its own semver, and have its own CI/CD that publishes it to maven similar to how we do this now in opensearch-java and other repos. Sounds to me like it should live in its own repo, but I don't know what its dependencies are.

My uneducated opinion is that it looks like the JDBC driver should follow its own semver, and have its own CI/CD that publishes it to maven similar to how we do this now in opensearch-java and other repos. Sounds to me like it should live in its own repo, but I don't know what its dependencies are.0

Raised:

https://github.com/opensearch-project/opensearch-build/issues/2799
https://github.com/opensearch-project/opensearch-build/issues/2800
https://github.com/opensearch-project/opensearch-build/issues/2801
for specific discussion and execution @dblock - thanks!

is repo split a blocker for maven release now on this issue or is it a separate issue ?

is repo split a blocker for maven release now on this issue or is it a separate issue ?

Separate issue.  At least until I'm informed otherwise.

AFAIK if we were able to release the driver before I don't see why splitting should be a blocker, however to setup automation you'll need to queue off a tag, and that becomes more difficult in a monorepo (you'd have to queue of a tag format, unclear which branch to tag, etc.).

Hi,
Have new discussion with @MaxKsyunz @Yury-Fridlyand @penghuo here is the method we are going to use:

Tag creation trigger a github action to clone the code, build maven artifacts, and push to an s3 bucket.
Github action will trigger jenkins workflow with the webhook.
Jenkins workflow will download the maven artifacts from s3 bucket, sign them, stage to sonatype.
Build repo members login to sonatype to release artifacts to maven central.

Thanks.

thanks peter, can you provide n estimate on this.

Release automation is tracked in #2505. This ticket is to track the current JDBC release.
The deadline is ~ Nov 9, 2022.

I created a JDBC driver pre-release on SQL repo: https://github.com/opensearch-project/sql/releases/tag/JDBC-<IP_ADDRESS>
Please proceed with manual publish on the Maven (no-shadow-copy-jar.zip).

We recently separated SQL into multiple repositories - this issue is now moving to the appropriate repo
https://github.com/opensearch-project/sql-jdbc

Hi,
I am looking into integrating the workflows for releasing SQL-JDBC. Publishing snapshots integration is depending on #1182
For releasing artifacts to maven central, I'll create PR with above repo.
Thanks!

Hi,
@MaxKsyunz @YANG-DB @anirudha,
Looks like ./gradlew build test shadowJar is just generating a single jar. Can you follow the instructions posted here: https://github.com/opensearch-project/opensearch-build/issues/2692#issuecomment-1278043132 and it get it in so that we can publish to maven?
Example: https://aws.oss.sonatype.org/content/repositories/releases/org/opensearch/opensearch-job-scheduler/<IP_ADDRESS>/
This has source java doc and application jar under same folder. Ideally it should be this way so that a user can download all 3 of them with same groupID. Also the gradle command should generate it all in a folder org/opensearch/driver. Can someone look into that?
Thanks!

can we remove jdbc-stage-maven-release.jenkinsfile

The jenkins file will be replaced similar by the ones similar to https://github.com/opensearch-project/spring-data-opensearch/blob/main/jenkins/release.jenkinsFile
For generating release artifacts we need some gradle command similar to this line https://github.com/opensearch-project/spring-data-opensearch/blob/main/.github/workflows/release-drafter.yml#L24 for jbdc that will take care of everything stated here https://github.com/opensearch-project/opensearch-build/issues/2692#issuecomment-1371566132

OK
I will replace the jenkins file with a similar to the one you suggested -
can u plz take care for the creation of the appropriate
tokenIdCredential:
*'jenkins-sql-jdbc-opensearch-generic-webhook-token'
*?
Thanks
בתאריך יום ד׳, 4 בינו׳ 2023 ב-19:48 מאת Sayali Gaikawad <
@.***>:

The jenkins file will be replaced similar by the ones similar to
https://github.com/opensearch-project/spring-data-opensearch/blob/main/jenkins/release.jenkinsFile
For generating release artifacts we need some gradle command similar to
this line
https://github.com/opensearch-project/spring-data-opensearch/blob/main/.github/workflows/release-drafter.yml#L24
for jbdc that will take care of everything stated here #2692 (comment)
https://github.com/opensearch-project/opensearch-build/issues/2692#issuecomment-1371566132
—
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/opensearch-build/issues/2692#issuecomment-1371751319,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALVNB5ICCYTS62S4ZXOUGTLWQZABVANCNFSM6AAAAAAQ47OH4A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey! Looks like there is some confusion. Sorry for not being clear. I'll take care of adding release workflows (GHA workflow as well as jenkins), also will set up other things like webhook and stuff. However, before we proceed with any of that, jdbc team needs to fix what I mentioned here in above comment.
Please update this issue once its done.
Thanks!

Thanks @Yury-Fridlyand , that would be great! So as far I understand this is what we want to publish on maven right?
Got confused because of the shadow jar conversation.

@gaiksaya, please, see https://github.com/opensearch-project/sql-jdbc/pull/45

@gaiksaya - plz add the 'release_drafter.yml' workflow to the following branches

main
2.x
Thanks

Hey @YANG-DB ,
Github actions only triggers workflows on default branch (which I assume is main). The triggers are at repo level. So it you want to publish something on 2.x branch, just checkout the branch, create a tag and push it. It will trigger the workflow and checkout the git ref accordingly.
Will work on adding the release workflows. Thanks!

Few questions:

What should be the trigger for the release? The ones followed by various other repos in this org is using a tag. However, I had offline discussion with @YANG-DB that they want to control publishing snapshots (in future) via tag too.
Please confirm the below artifacts needs to be published to maven:

build/repository
└── org
    └── opensearch
        └── driver
            └── opensearch-sql-jdbc
                ├── <IP_ADDRESS>
                │   ├── opensearch-sql-jdbc-<IP_ADDRESS>.jar
                │   ├── opensearch-sql-jdbc-<IP_ADDRESS>.jar.md5
                │   ├── opensearch-sql-jdbc-<IP_ADDRESS>.jar.sha1
                │   ├── opensearch-sql-jdbc-<IP_ADDRESS>.pom
                │   ├── opensearch-sql-jdbc-<IP_ADDRESS>.pom.md5
                │   └── opensearch-sql-jdbc-<IP_ADDRESS>.pom.sha1
                ├── maven-metadata.xml
                ├── maven-metadata.xml.md5
                └── maven-metadata.xml.sha1

hi

tag is fine
yes @Yury-Fridlyand can you approve ?

Thanks,
Please make sure you do not use tag for snapshots as well then as it will draft a release, triggering the release workflows. For  publishing snapshots I believe push is a good way to go. Your call.
One more question:
What should be the java version? Need it to specify here https://github.com/opensearch-project/spring-data-opensearch/blob/main/.github/workflows/release-drafter.yml#L19

lets go with java 11
@Yury-Fridlyand - sound correct ?

lets go with java 11
@Yury-Fridlyand - sound correct ?

Yes. Small note - version should be <IP_ADDRESS> or higher.
Please, check that you are on the right repo (sql-jdbc, not sql) and right branch.

Hi @YANG-DB , @joshuali925 , @anirudha
Was the security review completed for this version? Since the release template was not used, asking this question here.
Please confirm. Thanks!
cc: @bbarani

Got confirmation from @dblock @bbarani that security review is not required since its not a new product just code shifted to new repo. All the set up is done. We are good for the release. Will sync up with @YANG-DB offline to cut a tag.
Thanks!

sql-jdbc <IP_ADDRESS> is out https://aws.oss.sonatype.org/content/repositories/releases/org/opensearch/driver/opensearch-sql-jdbc/<IP_ADDRESS>/
Thanks everyone involved in this release. The process is end to end automated. You can check more details about universal release mechanism in this issue https://github.com/opensearch-project/opensearch-build/issues/1234.
Regarding releases see the documentation in the repo https://github.com/opensearch-project/sql-jdbc/blob/main/RELEASING.md

The SQL 2.5 release,  2.x and main branches are now depended on this (maven artifact )[https://repo1.maven.org/maven2/org/opensearch/driver/opensearch-sql-jdbc/<IP_ADDRESS>/]

Hi @YANG-DB, @joshuali925
You can now publish snaphots to maven using GHA directly. See the PR[1] as an example on what all needs to be added to make that happen. You can add me as a reviewer once PR is ready so that I can make changes at the backend and add the required role to retrieve the credentials.
Thanks!
[1] https://github.com/opensearch-project/opensearch-java/pull/325


Misspelled

Minor correction to spelling.

This change is

Hi @lboening, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


How to customize a form that contains fields from ChargeLogic Payments extension in Business Central 14 On Premise

Hi,
I am trying to modify the sales invoice form in a Business Central 14 On Premise system that has ChargeLogic Payments installed as an extension. My sales invoice modification needs to use a field from the ChargeLogics extension. I have added the .app files in the dependency's section of the app.json file and added the two .app packages into the .alpackages folder. The field is visible for me to reference. However when I try to download symbols (or debug) I receive an error that the app is not installed. I am using a DOCKER Image which does not have the ChargeLogic apps installed. Because it is a Sandbox I cannot upload the extension. I cannot debug or test because the ChargeLogic apps are not installed in my sandbox and I am not aware of how to install them.
Error:
[2020-05-29 08:46:20.24] Sending request to http://iss14:7049/NAV/dev/packages?publisher=ChargeLogic%2C LLC&appName=ChargeLogic Base&versionText=<IP_ADDRESS>
[2020-05-29 08:46:20.24] Sending request to http://iss14:7049/NAV/dev/packages?publisher=ChargeLogic%2C LLC&appName=ChargeLogic Payments&versionText=<IP_ADDRESS>
[2020-05-29 08:46:20.35] The request for path /NAV/dev/packages?publisher=ChargeLogic%2C%20LLC&appName=ChargeLogic%20Base&versionText=<IP_ADDRESS> failed with code NotFound. Reason: No published package matches the provided arguments.
[2020-05-29 08:46:20.39] The request for path /NAV/dev/packages?publisher=ChargeLogic%2C%20LLC&appName=ChargeLogic%20Payments&versionText=<IP_ADDRESS> failed with code NotFound. Reason: No published package matches the provided arguments.
If I try to publish any app to the sandbox image I receive an error that the package contains corrupted data.
app.json file:
"dependencies": [
{
"appId": "4714e6b7-6fde-4a8b-9c39-c2da3f239396",
"publisher": "ChargeLogic, LLC",
"name": "ChargeLogic Base",
"version": "<IP_ADDRESS>"
},
{
"appId": "0f30fcab-5ea0-4345-ba83-a32015759fbe",
"publisher": "ChargeLogic, LLC",
"name": "ChargeLogic Payments",
"version": "<IP_ADDRESS>"
}
],
"screenshots": [],
"platform": "<IP_ADDRESS>",
"application": "<IP_ADDRESS>",

This GitHub repository is dedicated to handling issues and feedback for the latest Developer Preview releases of the AL development tools for Dynamics 365 Business Central.
If you can reproduce the problem on the latest Business Central Developer preview version we will be happy to look further into it. Otherwise please contact the regular support channel.
You can open Support Request to CSS through PartnerSource portal or contact your Service Account Manager (SAM) in the local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also step by step direct you how to open a support request or how to get credentials if this is the first time for you / your company.
For more details please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions#i-found-an-issue-on-nav-2018-what-do-i-do


mini_racer_extension.so: undefined symbol: _ZNKSt8__detail20_Prime_rehash_policy11_M_next_bktEm

When running MiniRacer::Context.new I get the following error:
ruby: symbol lookup error: /usr/local/lib/ruby/gems/2.3.0/gems/mini_racer-0.1.6/lib/mini_racer_extension.so: undefined symbol: _ZNKSt8__detail20_Prime_rehash_policy11_M_next_bktEm

I'm using ruby 2.3.1 and bundler within a Docker container running debian:wheezy on an Ubuntu 16.04 Docker host and an Arch Linux Docker host. Natively on Arch it works.
uname -a
Linux lfm-docker-8 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
ruby -v
ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]

It happens with mini_racer 0.1.6 and 0.1.7.

Maybe I just found the answer. I have gcc version 4.7.2 (Debian 4.7.2-5). Trying to upgrade to 4.8.

Yup. That's it. Updated to Debian 8.3 with gcc 4.9. Now it works. Closing.

I have same issue but I am on Debian 7 so I can't upgrade gcc to 4.8.
Do you know if there  is an alternative?
Thanks.

Not sure what's the situation with clang on Debian, but theoretically one could export CXX=clang and try to install the gem this way.

I tried that. But it did not work.
mini_racer requires gcc 4.7+ (4.8+ it seems) or clang 3.2+. On Debian 7, clang package is 3.0.


Remove loop variable copies

This change removes loop variable copies which is no longer an issue with Go1.22+ semantics.

do we need to limit go version in makefile ?

do we need to limit go version in makefile ?

the go.mod already specifies go1.22.0 as minimum, so we should probably be good https://github.com/containerd/containerd/blob/c3efa0cb339ffc2d6c9f03d7fb4e5e6577d0194b/go.mod#L3


Can not process data in Custom Tools

Hi all,
I faced a problem that I can not receive or find any upload images or upload files in the custom tool. My purpose is that create a tool can process a specific job like detect object or OCR image and then return the result as a output of agent. What must I do for this task. Beside that, what about the custom tool can return another data types like image and return this image for user response.

Hey, I suggest using a file system for this purpose. Your agents can exchange file paths, or you can store the file in the shared_state within one tool and access it from another. For more tips, visit https://vrsen.github.io/agency-swarm/advanced-usage/tools/#pro-tips


Editor view gets corrupted on rx vega 56

Godot version:
v3.1.stable.official
OS/device including version:
Windows 10 x64
Radeon RX Vega 56 Driver version: 19.3.3
Issue description:
2d and 3d views get corrupted after a while. Same issue as described here: https://www.reddit.com/r/godot/comments/afekg2/new_to_godot_having_a_bug_happens_after_having/ Restarting the editor temporarily fixes the problem. Happens after moving something inside the editor, editing properties or simply switching between nodes.
Steps to reproduce:
follow the tutorial https://docs.godotengine.org/en/3.1/getting_started/step_by_step/ui_game_user_interface.html
usually happens after ~10-15 minutes
Minimal reproduction project:
ui_gui_design.zip

Windows 10 x64
AMD RX 460 Driver Version 19.3.2
Can't reproduce using the steps you listed in 20+ mins of trying.
I know it's not the same hardware/driver version but just adding my sample to the pool.

Found out that it only happens with the GLES3 renderer.

Happens to me on Windows 10 x64, Godot 3.1 stable
Radeon RX Vega 64 Driver version 19.5.2
Reproducing it is really a matter of using the inspectors tools for long enough it seems.


[BUG]: LIKE is broken for MySQL, maybe also sqlite

What version of drizzle-orm are you using?
0.28.5
What version of drizzle-kit are you using?
19.13
Describe the Bug
related to https://github.com/drizzle-team/drizzle-orm/issues/735 which could fix it in a more elegant way
LIKE is for case-sensitive searches, e.g. SELECT * FROM users WHERE id LIKE "fjSDfU3f;", do not work and are case-insensitive (which is as using ILIKE).
It's only case-sensitive once you declare column id with COLLATE utf8mb4_bin in the CREATE TABLE declaration or if you add it to the search query, which would be an easy fix, e.g.:
Expected behavior
SELECT * FROM users WHERE id LIKE "fjSDfU3f" COLLATE utf8mb4_bin;

or which is probably more work, introduce COLLATE in the table declaration as requested in https://github.com/drizzle-team/drizzle-orm/issues/735
Happy to submit a PR if you hint me the fix.
Environment & setup
MySQL

I'll close this in favor of #638


Feature Request: Specify fields that should remain required

Hi there, this is a really useful project! It would be great if we could pass a list of fields that should remain required in the resulting model—essentially, the opposite of the current ability to specify a subset of fields to be optional.

Hey, maybe this is what you are looking for: https://github.com/team23/pydantic-partial/blob/main/pydantic_partial/partial.py#L22

I think adding an required_fields keyword argument to the *_partial_model functions and removing them here would be an even cleaner solution as often you only need a few specific fields for PATCH requests for example, but need them always

Current solution would be to use:
PartialModel = create_partial_model(
    Model,
    *(
        set(model_compat.model_fields.keys())
        - {"the", "fields", "you", "want", "to" "keep"}
    ),
)

Is that working for you?

I wanted the partial model to just add a default value to all fields but keep whether the field is required or not from the full model.
This way all the fields may be omitted, but if they are given and aren't optional already in the full model Pydantic will reject null values.
Is that useful to you? See https://github.com/team23/pydantic-partial/pull/39


Models

added the model directory

Alright

how's the project even suppose to look like?

Since there's going to still a model and schema, it can alwyas be changed to suit the change.

This is the Project Goal for now


Render mark

I've made two versions of this (in two consecutive commits):

the function mark:  marks: [ () => svg'<text>function mark' ]

the render mark:  marks: [ { render: () => svg'<text>render mark' } ]

The second solution is imo much better since you can discover it by inspecting a mark. (It might be hard to figure out what initialize does without reading the documentation, but the render function is immediate and simple.)
closes #182

Closing in favor of #498.


Add Google-style docstrings for all classes and methods

Follow the specification here: https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html

[ ] al_courts.py
[ ] al_document.py
[ ] al_general.py

Considering reopenning this, given the success of https://github.com/SuffolkLITLab/docassemble-AssemblyLine-documentation/issues/302. I'm generally afraid of long-term trying to keep the specific arguments and all of their uses in manual documentation, away from the code. Closer to code leads to it being less of a maintaince burden when we add args and such to the code.
I've also got a solid example of converting our current docstrings to Google style. This is what the params section (the only part that would really change with a switch to Google style) looks like now:
    @param up_action {string} - the variable name of an event to be executed on the server if the
        thumbs up is pressed
    @param down_action {string} - the variable name of an event to be executed on the server i
        the thumbs down is pressed
    @param (optional) review_action {string} - the variable name of an event to be execute on the
        server when someone submits their text review
    @param (optional) thumbs_display {string} - text displayed to user describing the thumbs
    @param (optional) review_display {string} - text displayed to user describing the text input
    @param (optional) submit_review_button {string} - text on the button to submit their text review
    @param (optional) post_review_display {string} - text displayed to user after review is
        submitted
    @returns the HTML string of the widget

And would change to:
    Args:
       up_action (str): the variable name of an event to be executed on the server if the
           thumbs up is pressed
       down_action: the variable name of an event to be executed on the server if the
           thumbs down is pressed
       review_action: the variable name of an event to be execute on the
           server when someone submits their text review
       thumbs_display: text displayed to user describing the thumbs
       review_display: text displayed to user describing the text input
       submit_review_button: text on the button to submit their text review
       post_review_display: text displayed to user after review is submitted
   Returns:
       the HTML string of the widget

No bad IMO, we just need to get used to writing things like that.

A confusing docstring to keep in mind when doing this refactor: https://github.com/SuffolkLITLab/docassemble-AssemblyLine-documentation/pull/321#discussion_r1110010191


[FLINK-34559] Limit Global & Local Aggregation buffers

What is the purpose of the change
Limit Global Aggregation buffers

In case of large windows and/or lagging watermarks,
RecordsWindowBuffer processes buffered records and flushes the state
during the sync phase of the checkpoint causing checkpoint timeout.

This change limits the number of records buffered and the buffer size.

Limit Local Aggregation buffers

The buffer holds records for aggregation in memory and is flushed downstream on:
1) checkpoints, 2) watermarks, or 3) when it is full.
If it's too big (even if watermarks are progressing),
there might be much more data to flush than the memory available (classic flatMap problem).
That might lead to back-pressure and hard-blocking the task thread.

This change limits the buffer and the number of records.

Verifying this change
Please make sure both new and modified tests in this PR follow the conventions for tests defined in our code quality guide.
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

How about we simply add a set(ConfigOption) and set(String) to ExecutionConfig? It is not really necessary that ExecutionConfig picks up all configuration from ReadableConfig configuration. For a later runtime patching of ExecutionConfig, we could only use the set(String).

We'd still need to call these methods with specific constants or keys, right?
And doing so during run time would be problematic (the runtime would need to know these constants).


Typo in article's title in left-nav

The title of this article in the left-nav has a typo on the word "because":

Cannot RDP becasue "You must change your password before logging on the first time" error

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

ID: 4acc4877-5bec-9343-57bb-a81052112278
Version Independent ID: f4613a17-9bd6-dfb6-6340-30f236cb6966
Content: Azure virtual machine error You must change your password before logging on the first time - Virtual Machines
Content Source: support/azure/virtual-machines/must-change-password.md
Service: virtual-machines
GitHub Login: @genlin
Microsoft Alias: genli

@daniel-isaacs  Thanks for the feedback and submiting PR.


cmd/vet: incorrect detection of self-assignment

What version of Go are you using (go version)?
>go version
go version go1.9.1 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=d:\dev\gopath\
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=e:\temp\wintemp\go-build563293679=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config

What did you do?
Save https://play.golang.org/p/d5JNE7rvLc to main.go
Execute go vet main.go
What did you expect to see?
Nothing. The code is not self-assigning.
What did you see instead?
main.go:11: self-assignment of s[rng.Intn(len(s))] to s[rng.Intn(len(s))]
exit status 1

I'll take a stab at this later.


Add display name to rule eval status

Summary
This PR adds the ruletype display name to the response of the rule evaluation status:
{
  "entities":  [
    {
      "entity":  {
        "type":  "ENTITY_REPOSITORIES",
        "id":  "1fcf9bdd-748f-40e1-a24c-cb798db7634a"
      },
      "profiles":  [
        {
          "profileStatus":  {
            "profileId":  "4fd9ccf4-035e-4326-b637-b615e56070fd",
            "profileName":  "dependabot-go-github-profile",
            "profileStatus":  "failure",
            "lastUpdated":  "2024-04-02T01:14:05.981306Z",
            "profileDisplayName":  "dependabot-go-github-profile"
          },
          "results":  [
            {
              "profileId":  "4fd9ccf4-035e-4326-b637-b615e56070fd",
              "ruleId":  "2272622e-25b1-474a-9a65-eb2d0c92b387",
              "ruleName":  "dependabot_configured",
              "entity":  "repository",
              "status":  "failure",
              "lastUpdated":  "2024-04-02T01:14:08.159459Z",
              "entityInfo":  {
                "provider":  "github",
                "repo_name":  "bomshell",
                "repo_owner":  "puerco",
                "repository_id":  "1fcf9bdd-748f-40e1-a24c-cb798db7634a"
              },
              "details":  "denied",
              "guidance":  "Dependabot enables Automated dependency updates for repositories.\nIt is recommended that repositories have some form of automated dependency updates enabled\nto ensure that vulnerabilities are not introduced into the codebase.\n\nFor more information, see\nhttps://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file\n",
              "remediationStatus":  "failure",
              "remediationLastUpdated":  "2024-04-02T01:14:08.171215Z",
              "remediationDetails":  "cannot create pull request: POST https://api.github.com/repos/puerco/bomshell/pulls: 422 Validation Failed [{Resource:PullRequest Field: Code:custom Message:A pull request already exists for puerco:minder_add_dependabot_configuration_for_gomod.}], action failed",
              "ruleTypeName":  "dependabot_configured",
              "alert":  {
                "status":  "on",
                "lastUpdated":  "2024-04-02T01:14:08.185451Z"
              },
              "severity":  {
                "value":  "VALUE_UNKNOWN"
              },
              "ruleEvaluationId":  "a0260c9b-897a-4ed9-8204-c00fcf8f877f",
              "ruleDisplayName":  "dependabot_configured"
            }
          ]
        }
      ]
    }
  ]
}

/cc @peppescg
Change Type

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[ ] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 47.204% (-0.009%) from 47.213%
when pulling a2ac88075cc350a660f04e38dbbdf736dfa588b1 on puerco:name
into ef19751d92992f2ce044ef48c19535c5aa79c0ae on stacklok:main.


Featured Image Fails to Display

Hi! I have been searching online as well as through these issues but I found no solution yet.
Basically, I have a little blog using this theme: https://gitlab.com/stefano-tronci/website
It is deployed here: https://stefano-tronci.gitlab.io/website/
As you can see, the home page does not display the featured image. This is puzzling, because the post displays it correctly. What is more puzzling is that I have a very similar website that works properly:

https://gitlab.com/computational-acoustics/website
https://computational-acoustics.gitlab.io/website

The two websites are pretty much a copy of each other.
Any idea why the featured image doesn't seem to work on the first website?

Hi @stefano-tronci Have a look at the example site. It looks like you don't have a _index... in your repo. Here's an example https://github.com/theNewDynamic/gohugo-theme-ananke/blob/master/exampleSite/content/en/_index.md

Hi @stefano-tronci did this solve your problem?

Hey there, thank you for your suggestion! Unfortunately I haven't got a
chance to test it. I think I will test it tonight (UK time).
On Fri, 6 May 2022, 14:40 Regis Philibert, @.***> wrote:

Hi @stefano-tronci https://github.com/stefano-tronci did this solve
your problem?
—
Reply to this email directly, view it on GitHub
https://github.com/theNewDynamic/gohugo-theme-ananke/issues/549#issuecomment-1119635737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD7YFX3SPPYG3LL2YBBIVFDVIUOONANCNFSM5U4PCCEA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yep! That was it. Adding the _index.md fixed it. Thank you for your help!


NIFI-1564: No supported viewer issue

Addressing issue referencing the global jQuery variable in the content viewer.

This PR should be applied to both master and 0.x branches.

+1


"Cannot use sysprep..." Error from playbook  when  using cloud-init only deployment

running playbook with parameters:
Resulting error:
2019-07-14 09:48:03,868 p=10844 u=root |  Using module file /usr/lib/python2.7/site-packages/ansible/modules/utilities/logic/async_status.py
2019-07-14 09:48:04,026 p=10844 u=root |  The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_ovirt_vm_payload_txFuqn/main.py", line 2071, in main
) else None,
File "/tmp/ansible_ovirt_vm_payload_txFuqn/ansible_ovirt_vm_payload.zip/ansible/module_utils/ovirt.py", line 738, in action
getattr(entity_service, action)(**kwargs)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 31504, in start
return self._internal_action(action, 'start', None, headers, query, wait)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action
return future.wait() if wait else future
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait
return self._code(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback
self._check_fault(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault
self._raise_error(response, body)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error
raise error
Error: Fault reason is "Cannot use sysprep and cloud_init tags simultaneously when running VM.". HTTP response code is 409.
Full Log:
https://paste.fedoraproject.org/paste/vCsDHnqdjqpohJ9HvtC9FA/raw

suspect that sysprep parameter are propagated by mistake as empty dict to the :
https://github.com/oVirt/ovirt-ansible-vm-infra/blob/e734783f54e3010ae73b6f2cb9136478ad4ad115/tasks/manage_state.yml#L64

suspect that sysprep parameter is propagated by mistake as empty dict to the :
https://github.com/oVirt/ovirt-ansible-vm-infra/blob/e734783f54e3010ae73b6f2cb9136478ad4ad115/tasks/manage_state.yml#L64

Yes, please see: https://github.com/ansible/ansible/issues/44261#issuecomment-413564998

@mnecas Can you please take a look

Hi @eslutsky can you give me your playbook so i can try to recreate it?

Hi @eslutsky can you give me your playbook so i can try to recreate it?

Sure,
you can use this playbook:
https://paste.fedoraproject.org/paste/OMr4EehXONbjcKNcHsuvNg
during execution this error received:
TASK [ovirt.vm-infra : Wait for VMs to be started] ****************************************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: Error: Fault reason is "Cannot use sysprep and cloud_init tags simultaneously when running VM.". HTTP response code is 409.
failed: [localhost] (item={'failed': False, u'finished': 0, u'results_file': u'/root/.ansible_async/270615310005.13509', u'ansible_job_id': u'270615310005.13509', u'started': 1, 'changed': False}) => {"ansible_job_id": "270615310005.13509", "attempts": 1, "changed": false, "finished": 1, "item": {"ansible_job_id": "270615310005.13509", "changed": false, "failed": false, "finished": 0, "results_file": "/root/.ansible_async/270615310005.13509", "started": 1}, "msg": "Fault reason is "Cannot use sysprep and cloud_init tags simultaneously when running VM.". HTTP response code is 409."}
TASK [ovirt.vm-infra : Unset facts] *******************************************************************************************************************************************************************************
ok: [localhost]
TASK [ovirt.vm-infra : Logout from oVirt] *************************************************************************************************************************************************************************
ok: [localhost]
PLAY RECAP ********************************************************************************************************************************************************************************************************
localhost                  : ok=19   changed=0    unreachable=0    failed=1

@eslutsky thank you for the playbook, really helped.

Backport https://github.com/ansible/ansible/pull/59286

Will work from Ansible 2.8.3


495: Store the content of the stream into a temporary file for reuse

Fix for https://github.com/yegor256/takes/issues/495
this issue is related to the fact that the code in the use case relies on this constructor to build its response so when the InputStream has been consumed once, we get an IOException on the next calls.
The idea of this PR is to store the content of the input stream into a temporary file in order to be able to read the content as many times as we want and be able to do it securely from concurrent threads which was not the case otherwise as most InputStream implementations have not been designed to be shared which could affect the thread safety of the whole class RsWithBody.

@essobedo Thanks, I will find someone to review this PR soon

@krzyk it's yours,please review

@essobedo please see my comments

@krzyk thx for the remarks, here is a new version of the PR

@essobedo please see my additional comments

@krzyk Here is the new version of the PR, thanks for the remarks

@essobedo few variables have to inlined and we are ready to go

@krzyk please check this new version

@essobedo you missed one comnent

@krzyk my bad, here is the new version

@rultor merge pls

@rultor merge pls

@krzyk Thanks for your request. @yegor256 Please confirm this.

@essobedo see my comments

@yegor256 thx for the remarks, here is the new version of the PR, please check

@yegor256 Could you please recheck, thank you in advance.

@essobedo a few more comments. catching an exception is not a good idea in general: http://www.yegor256.com/2015/07/09/catch-if-cant-otherwise.html

@yegor256 Please see my answers and the last version of the PR.

@essobedo see above

@krzyk did you/I miss something here? why do we read the entire input stream in a ctor?? this looks very wrong to me

@yegor256 see my answer above and the description of the PR for more details.

@essobedo I understand your intention, but the design is wrong. your Body.Stream class is doing two things at a time: converting InputStream to Body and caching it in a file. That's against the single responsibility principle and is wrong in general. you need two classes, not one.

@yegor256 Here is a new version of the PR that doesn't break the single responsibility principle. please check again

@yegor256 could you please tell me what you think about the new version of the PR? Thank you in advance.

@essobedo it's better now, but check this out: http://www.yegor256.com/2015/05/07/ctors-must-be-code-free.html Constructors must NOT execute any code. Everything should happen in methods of a class. See how it's done in, say, RqForm.Base

@yegor256 It should be fine now, could you please check again?

@yegor256 please check again

@essobedo now it looks OK, but I don't like the fact that we're forcing everybody to use this file-caching mechanism. in many/most cases it's not required. if I just want to return my content in input stream, I just do it. take a look at this example: https://github.com/yegor256/rultor/blob/1.61.8/src/main/java/com/rultor/web/TkDaemon.java#L106-L147 You see? Just input stream works perfectly fine. I don't need any files to cache my content. This file-caching is a rather unique feature, which may be needed by someone, but not everybody. See?

@yegor256 unless I miss something but according to what I can see from the code that you point, for me it is not comparable because it creates a new stream at each call (it creates a new instance of SequenceInputStream composed of only new InputStream instances so not shared). In this case, we use a shared InputStream instance so once it has been read and closed it is no more useable as the next calls will fail because the stream is already closed (if we don't close it, we will get -1 at the next calls).
Here I use a file to be able to provide a new InputStream instance at each call like the code that you point, I don't see any better way to do it.
Here is a simple test case that illustrate the issue:
   @Test
    public void testStream() throws IOException {
        ByteArrayInputStream is = new ByteArrayInputStream("foo".getBytes());
        SequenceInputStream sis = new SequenceInputStream(Collections.enumeration(Collections.singletonList(is)));
        Assert.assertEquals((int)'f', sis.read());
        Assert.assertEquals((int)'o', sis.read());
        Assert.assertEquals((int)'o', sis.read());
        Assert.assertEquals(-1, sis.read());
        sis.close();
        sis = new SequenceInputStream(Collections.enumeration(Collections.singletonList(is)));
        Assert.assertEquals((int)'f', sis.read());
        Assert.assertEquals((int)'o', sis.read());
        Assert.assertEquals((int)'o', sis.read());
        Assert.assertEquals(-1, sis.read());
    }

Here it will fail at the second call because it returns -1 instead of 'f' as a ByteArrayInputStream doesn't care if it is closed or not but with other implementations you will get an IOException. To make it work we would need to reset the underlying stream before starting to read it again but the reset method is not always implemented and moreover it will only allow sequential read not concurrent ones.

@yegor256 Even if it is encapsulated into an immutable object, I don't believe that it is a good practice to share a mutable Object not necessarily Thread Safe such as an InputStream. This PR allows to fix this bad practice.

@yegor256 what do we do from here? any suggestion to go any further?

@essobedo but in most cases we don't need our input stream to be ready for multiple reads. This multiple reads is an exceptional situation. Usually, if I give an input stream to RsWithBody I expect it to be read only once. why would anyone be interested in reading it twice? maybe sometimes... but it's an exception, not a default situation

@yegor256 OK so If I understand you correctly for you, doing this is not a bug in takes but it is rather a misuse of takes, right? As I mention in the ticket itself, in this situation we are supposed to use Bug.class.getResource instead of Bug.class.getResourceAsStream, is it what you mean? If so what am I supposed to do within the context of this (false?) bug? I am supposed to simply add a warning in the Javadoc of all constructors of RsWithBody with an InputStream indicating that it is meant to be read only once so in case it should be used several times we are supposed to use the corresponding constructors with a byte array or a URL. Is it what you expect?

@yegor256 Or maybe you would like me to give access to the constructor RsWithBody(final Response res, final Body body) and use new Body.TempFile(new Body.Stream(body)) only in specific locations such as in public RsHTML(final InputStream body). But for constructors of RsWithBody with InputStream, I don't wrap new Body.Stream(body) with Body.TempFile. Is this what you want?

@yegor256 please check this new version of the PR in which I limited the fix to RsHTML and RsText in order to use the file-caching approach only on specific use cases as you wanted.
Please note that I had to modify Body.Stream to have the length of the Stream at creation time otherwise I get some failing tests because this.stream.available() was called too late so we get IOException instead.

@yegor256 please check again

@essobedo yes, this is an incorrect use of Takes, not a bug.

@essobedo one small comment above. the rest is cool

@yegor256 here is a new version of the PR, please check again.

@essobedo a few more questions. sorry for so many comments, but this part of the code is very actively used in many parts of the framework

@yegor256 what do you think about my answers?

@rultor try to merge

@rultor try to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor try to merge

@yegor256 Done! FYI, the full log is here (took me 21min)

@ypshenychka please, let us know what do you think about this ticket, according to our QA rules

@rultor deploy pls

@rultor deploy pls

@davvd OK, I'll try to deploy now. You can check the progress here

@rultor deploy pls

@davvd Done! FYI, the full log is here (took me 18min)

@davvd Quality is good.

@davvd Quality is good.

@ypshenychka many thanks

@krzyk 10 mins was added to the account of @ypshenychka (for QA review), in transaction 81205063. Thanks so much!


PHP Errors

I'm trying to run IKEv2 and L2TP over IPSec and L2TP isn't working. It was before on a separate box. I also noticed that it was asking for a connect client when I'm trying to install it. Is there only one mobile client for IPSec supported?
Crash report begins.  Anonymous machine information:
amd64
11.2-RELEASE-p4
FreeBSD 11.2-RELEASE-p4 #87 4f85556a02f(RELENG_2_4_4): Fri Nov  9 13:27:46 EST 2018     root@buildbot3:/crossbuild/ce-master/obj/amd64/9kCJYnqE/crossbuild/ce-master/pfSense/tmp/FreeBSD-src/sys/pfSense
Crash report details:
PHP Errors:
[15-Dec-2018 23:27:54 America/Toronto] PHP Warning:  explode() expects parameter 2 to be string, array given in /usr/local/www/vpn_ipsec_mobile.php on line 456
No FreeBSD crash data found.

You probably set the Pull Request against the wrong branch. Please re-submit

That PHP error appears to be from mismatched code between 2.3.x and 2.4.x or similar. The line in question hasn't changed in over two years, nor has anything around it. Something is very broken on your installation.
This site is not for support or diagnostic discussion. For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit.


Add info for Chromebook use

Hi there,
given quarantine measures for the SAR-CoV-2/Coronovirus 2020 pandemic driving the use of Chromebooks, can you add official guidance on how to use Teams on them? Even if it's "Use the Android app" or "Use the web app".

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

ID: 6457d204-d229-9154-28fd-ca9bbb4bddcd
Version Independent ID: f5d82846-41cb-3548-6997-ce23bd8f89c6
Content: Get clients for Microsoft Teams - Microsoft Teams
Content Source: Teams/get-clients.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@rburte-isp  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@rburte-isp The Teams app is available on Chromebooks for a while now - more details here. I'll add a note about that.
For the Web client, i think it's already covered. The Teams Web client is supported on all operating systems that can run the supported browsers stated in the article:

As long as an operating system can run the supported browser, Teams is supported

So as long as you use a supported web browser on your Chromebook, Teams will work as it should.

@rburte-isp Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Show utilitary methods for Neo-Cli

This is an update from #455 and complementing #535.
Some changes were made:

Adding the command show last-block:

Adding the block index on show last-transactions:

Changing the time format in show block:

It can be merged after #536.

@Thacryba I think the second function is very useful. However, it hasn't decompile tx compeletely. So op codes haven't be recognized yet. And since the json output can be very long in cli, I think it's more suitable to be made into rpcserver plugin and the first one and the third one are already existed. I recommend to improve the second one and made txid as a param in RPC.


add more rank profiles and guide text

work in progress, but commit now for easier progress

@oyving I will move the text in the readme to another doc, but we can merge for now to get the .sd changes in


Geolocator conflict with Xamarin.GooglePlayServices.Ads

Thank you for your plugin.
But I hate the way you close issues after your one comment.
Please try Geolocator Plugin and Xamarin.GooglePlayServices.Ads in one project. Thank you!

Please attach or upload a sample project. Without knowing your versions of this plugin, your sdks, or the ads nuget it will be hard for me to diagnose.

Xamarin.Forms : <IP_ADDRESS>
Xam.Plugin.Geolocator : 3.0.4
Xamarin.GooglePlayServices.Ads : v42.1021.1
Visual Studio 2017
JDK 1.8.0_131
NDK r14
I have try with new project. Just install from Nuget --> Build --> error
Here is my link

You need to update your NuGet Packages and also ensure you are building against 7.0 or 7.1 and it will build just fine.
Also, I would recommend looking into Ads Lite as it has less dependencies: https://blog.xamarin.com/lightweight-ads-for-android-apps/
LocatorTest.zip


Installation on Ubuntu 20.04 fails

I'm not able to install papermerge on fresh Ubuntu 20.04 Server, i see always the following error when i invoke manage.py and have no idea how i can fix this:
(.venv) me@papermerge:/opt/papermerge$ ./manage.py migrate Traceback (most recent call last):   File "./manage.py", line 24, in <module>     execute_from_command_line(sys.argv)   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line     utility.execute()   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute     self.fetch_command(subcommand).run_from_argv(self.argv)   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/management/base.py", line 330, in run_from_argv     self.execute(*args, **cmd_options)   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/management/base.py", line 371, in execute     output = self.handle(*args, **options)   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/management/base.py", line 85, in wrapped     res = handle_func(*args, **kwargs)   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 75, in handle     self.check(databases=[database])   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/management/base.py", line 392, in check     all_issues = checks.run_checks(   File "/opt/papermerge/.venv/lib/python3.8/site-packages/django/core/checks/registry.py", line 70, in run_checks     new_errors = check(app_configs=app_configs, databases=databases)   File "/opt/papermerge/.venv/lib/python3.8/site-packages/papermerge/core/checks.py", line 110, in binaries_check     binary = os.path.basename(binary_path)   File "/usr/lib/python3.8/posixpath.py", line 142, in basename     p = os.fspath(p) TypeError: expected str, bytes or os.PathLike object, not NoneType
I followed the Installation guide found here. Any Ideas what is missing here?
Info:

Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.2 LTS
Release:	20.04
Codename:	focal
Papermerge Version v2.0.0rc48

Thanks for quick heads up!
It is a nasty bug. Here is workaround:
1.First install dependencies:
$ pip3 install -r requirements/base.txt

Check installation path of stapler utility with

$ which stapler

Add that path (absolute path to stapler utility) to papermerge.conf.py:

BINARY_STAPLER = "/home/eugen/Lab/DMS/.venv/bin/stapler"

I added default value for stapler.
If you will get latest source code (via git pull command), it should work without workaround.

This was it! With the new Version it works!
Thanks for the fast support.


Example usage

Put more usage examples especially in the rosed.go file.

Also give ExampleX functions for ones where it makes sense to do so

grapheme-based indexing also need to be on the rosed.go file


Allow plugin configuration to be set from sonobuoy config

Currently the E2E tests (like which tests to run, etc) are driven by environment variables, and in order to change them you  have to change the plugin definition (./plugins.d/e2e.yaml).
It'd be nice to let the e2e.yaml plugin definition remain constant, and for plugin behavior to be configurable from the main sonobuoy.conf file, since it's specific from run-to-run.
This was mostly the idea from the beginning, but it doesn't currently work.
Example sonobuoy config:
{
  ...
  "plugins": {
    {
      "name": "e2e",
      "config": {
        "focus": "foo",
        "more": "config",
        ...
      }
  }
}

And the plugins[...].config section would be available in "/etc/sonobuoy/plugin-config.json" or similar on the worker side.

This is nice to have, but not important atm.

closing in preference of ksonnet-i-fying the configs.


Profile.Spec.LabelsToApply shows up incorrectly in yaml

- apiVersion: projectcalico.org/v2
  kind: Profile
  metadata:
    creationTimestamp: 2017-10-21T22:42:49Z
    name: k8s_ns.default
    resourceVersion: "44"
    uid: 2a2dcd3e-b6b1-11e7-a133-42010a800002
  spec:
    egress:
    - action: Allow
      destination: {}
      source: {}
    ingress:
    - action: Allow
      destination: {}
      source: {}
    labels:
      pcns.foo: bar

Expected Behavior

spec.labels should be spec.labelsToApply

For more context, it doesn't match the struct naming.


docs: added documentation for various show options

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Correct typos and expressions

I've noticed there where a couple of typos and a mix of formal/informal context. E.G. If you have any problem - "Si tiene algún problema" (formal) vs "Si tienes algún problema (informal)

[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] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Consider duration changes for animation updates

With this change, updates to the velocity-react duration prop will update the animation. (Transitioning a box across the screen then halving the duration requires that the animation be sped up, and so the animation should be recalculated.)

I'm not necessarily against this, but I want to make sure it's doing what you intend.
When the duration changes, the animation will restart from the current DOM state, without memory of any previous animation or duration. So, if the box is halfway across the screen and you half the duration, the new animation will actually proceed at the same rate, as it has only half the distance to go.
Is the effect you want better expressed through a custom tween or multi-step animation?

Tested this and the animation does speed up. For example, when I want the item to suddenly speed up in the middle, setting duration to something smaller works.

Closing this without a compelling use-case. I don't think duration changes are conceptually the right fit for the declarative way velocity-react works, due to the non-intuitive way they work with any in-progress animations.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b4om6ttday/clone/recipe/meta.yaml:25: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_b4om6ttday/clone/recipe/meta.yaml:36: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_b4om6ttday/clone/recipe/meta.yaml:46: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_b4om6ttday/clone/recipe/meta.yaml:46: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_b4om6ttday/clone/recipe/meta.yaml:46: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found


No sound in the xCode 7.1.1 and iOS 9.1

Hi,
I found not sound on my phone(iPhone 5S). The details:  There hasn't sound while play video by xCode 7.1.1 compile and run on iOS 9.1.

can you ensure you hear sound in safari when playing a video too?


Can't use Bitstamp

I can't start Zenbot using any form of the "Zenbot.sh trade bitstamp.xxx-xxx" because it can't backfill data and blocks the execution...

I agree, it won't trade at all even without backfilling, like bittfinex
`osboxes@osboxes:~/zenbot$ ./zenbot.sh trade bitstamp.xrp-usd
fetching pre-roll data:
cannot backfill bitstamp: exchange does not offer historical data
osboxes@osboxes:~/zenbot$ `

Now the backfilling problem is solved but I can't still trade anything with Bitstamp...

I see buy/sell decisions but no real API requests happen. Any ideas?

Seems the buy/sell commands doesn't work as well


Why aren't nested variables accessible?

Given the following helmfile and values file:
#values.yaml
test:
  nested: test

test2: test

#helmfile
releases:
- name: atlantis
  ...
  values:
  - atlantisUrl: {{ .Values.test.nested }}  (Doesn't work)
  - atlantisUrl: {{ .Values.test2 }}  (Does work)
environments:
  test:
    values:
      - values.yaml

Gives the following error:
in ./helmfile.yaml: error during helmfile.yaml.part.0 parsing: template: stringTemplate:19:63: executing "stringTemplate" at <.Values.test.nested>: map has no entry for key "test"

However using non nested values such as {{ .Values.test2 }} works fine.
How can I make nested values work?

I running into the same issue which I've described here.
I can make it work by using the index function but it's slightly more complicated and I feel like it ought to work without.

@mumoshu - Thanks for the explanation.
I can fix this by simply listing my environments before my releases. No need for a separator.
I think it's a bit of a shame that the order matters but I'm well aware that we don't live in a perfect world.

I can fix this by simply listing my environments before my releases. No need for a separator.

@tonsV2 You found it! Yes - that workaround also works in many cases 😃 Theoretically it isn't perfect though. So I'd recommend you to use --- as the go-to option in the future.

I think it's a bit of a shame that the order matters but I'm well aware that we don't live in a perfect world.

Yes. I'm not satisfied with the current state. It's just that I'm not yet sure what's the best/correct way to deal with this.

I can fix this by simply listing my environments before my releases. No need for a separator.

@tonsV2 You found it! Yes - that workaround also works in many cases  Theoretically it isn't perfect though. So I'd recommend you to use --- as the go-to option in the future.

The --- separator doesn't work for me. Helmfile only runs if I list the environments first.

I think it's a bit of a shame that the order matters but I'm well aware that we don't live in a perfect world.

Yes. I'm not satisfied with the current state. It's just that I'm not yet sure what's the best/correct way to deal with this.

As a programmer I can relate to this but I feel the current implementation of environments is a bit limited. Being able to specify things such as kube context per environment and values per release would be really nice. Please don't take this comment the wrong way I greatly appreciate your work and support here :-)

I ran into this problem today, and a co-worker suggested a solution I did not expect.  Leaving it here for the next person to find.
environments:
  default: {values: ['junk.env.yaml']}
releases:
- name: 'autoscaler'
  chart: '{{.Values.autoscaler.chartname}}'
  version: 'latest'

chart: '{{.Values.autoscaler}}'  would evaluate to a string-serialized version of the mapping.
chart: '{{.Values.autoscaler.chartname}}' would error with "map has no entry for key "autoscaler" "
chart: "{{.Values.autoscaler.chartname}}" same result with double-quotes.
chart: {{.Values.autoscaler.chartname}} would give me the string I expected from the .Environment.Values map.

The solution by @tonsV2 worked for me 🙌🏼


1.9 clusters are using the 1.8 dashboard

We need to update/test the new YAML for 1.9.
We should probably have a checklist of dependencies to check for when doing version upgrades.

It looks like the version numbers for the dashboard no longer directly correspond to the k8s version. #165 Does rev the dashboard version to the latest released version.


esy build fails due to missing .opam file in dune-private-libs

On my Windows 10, using esy 0.6.4 (in an administrator cmd shell), the following happens:
> esy build
info esy build 0.6.4 (using package.json)
info building @esy-ocaml/substs@0.0.1@d41d8cd9
info building ocaml@4.9.1000@d41d8cd9
...
...
...
info building @reason-native/console@0.0.3@d41d8cd9
error: build failed with exit code: 1
  build log:
    # esy-build-package: building: @opam/dune-private-libs@opam:2.5.1
    # esy-build-package: pwd: C:\Users\stefanz\.esy\3\b\opam__s__dune_private_libs-opam__c__2.5.1-f66a9529
    # esy-build-package: running: "dune" "build" "-p" "dune-private-libs" "-j" "4" "@install"
    Info: Creating file dune-project with this contents:
    | (lang dune 2.5)
    File "src/cache/dune", line 3, characters 14-37:
    3 |  (public_name dune-private-libs.cache)
                      ^^^^^^^^^^^^^^^^^^^^^^^
    Error: You cannot declare items to be installed without adding a
    <package>.opam file at the root of your project.
    To declare elements to be installed as part of package "dune-private-libs",
    add a "dune-private-libs.opam" file at the root of your project.
    Root of the project as discovered by dune: .
    error: command failed: "dune" "build" "-p" "dune-private-libs" "-j" "4" "@install" (exited with 1)
    esy-build-package: exiting with errors above...

  building @opam/dune-private-libs@opam:2.5.1
esy: exiting due to errors above

It's hard to find any further info on that. Is it a known issue with dune-private-libs or something higher up the dependency hierarchy?
Over at onivim the same issue popped up: https://github.com/onivim/oni2/issues/1816

I stumble on that also, my trick as a workaround is to remove ~/.esy and run inside of git bash.


NIFI-8420 update to latest jetty on 9.4.x line

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Is that NIFI-8421 commit supposed to be in this PR?

yep thanks.  kept them as distinct JIRAs/commits but had them on the same PR.  Probably should have avoided but given how cleanly isolated they are we should be good.  Just merged


New: class-name-casing rule (class-name from TSLint)

Implements https://github.com/nzakas/eslint-plugin-typescript/issues/5#issuecomment-321985325.

Awesome, code LGTM
Please prefix the title with 'New:' so the PR can be easily identified as a rule addition.

LGTM

Thanks! The older README.md cleanup PR that went in means this just needs to be rebased before going in

@JamesHenry Done!


[Distributed] Fix effectiveLabel implementation to expected semantics

This has been around for a while but might be nice to fix.
Resolves: rdar://97775548
The original report was on the swift forums:

https://forums.swift.org/t/accepted-se-0344-distributed-actor-runtime/56416
@ktoso I have played around a little with Xcode 14.0 beta 3 (I currently cannot check beta 4) and have noticed that the behavior regarding RemoteCallArgument does not match the documentation. For these functions, the properties are currently filled as follows:
// label: "a", name: "a", effectiveLabel: "a"
distributed func callMe(a: String) {}

// label: "b", name: "c", effectiveLabel: "b"
distributed func callMe(b c: String) {}

// label: nil, name: "d", effectiveLabel: "d"
distributed func callMe(_ d: String) {}
As per the documentation, in the first case, label should be nil.

I think, the behavior as currently implemented makes much more sense. However, effectiveLabel is now pretty superfluous and returns the wrong string in the third case.

I thought about this a bunch and arrived at the: we should make effectiveLabel do what it sounds like it should be doing: so it's the "label" at the call site, if you wanted to construct the hi(a:b:_:) yourself".

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test