Enhance Log Topics for Pulsar Functions

Is your feature request related to a problem? Please describe.
When using the logTopic feature of Pulsar Functions it works great, but seems a bit limited in it's usage as only the message body is being sent to the logTopic as byte[].
Describe the solution you'd like
Add an additional LogAppender.append method override that allows for the org.apache.logging.log4j.core.LogEvent object to be sent to the logTopic directly or allow the logTopic to except a custom schema and not just byte[]. This would allow consumers of the log topic to decipher what messages are of type INFO, WARN, ERROR, etc. The metadata in the org.apache.logging.log4j.core.LogEvent objects could be very valuable on the log consumption and analytics side.
src/main/java/org/apache/pulsar/functions/instance/LogAppender.java
Original
@Override
    public void append(LogEvent logEvent) {
        producer.sendAsync(logEvent.getMessage().getFormattedMessage().getBytes());
    }

Potential future maybe?
@Override
    public void append(LogEvent logEvent) {
        producer.sendAsync(logEvent);
    }

Describe alternatives you've considered
I have considered creating a custom schema and topic and then just having my functions publish to that via the following and not using the built in Logger at all:
context.newOutputMessage((Log) topicToWrite.get(), Schema.LOG).value(input).sendAsync();
I would rather use the functions built in Logger if at all possible.

@one70six sounds good to me.  We can even produce the logs with a schema e.g.
| level | classpath                                                   | message|
|INFO | org.apache.logging.log4j.core.LogEvent| foo

why not just define a Struct for this? use AVRO and JSON to serialize the struct to the log topic. It doesn't make sense to introduce a new schema type.

@sijie that is what i mean?

ok. I saw there is Schema.LOG in the issue. Just want to make sure everyone is on the same page.

Very cool guys. exactly what I was hoping for! Thanks!

Closed as stale. Please create a new issue if it's still relevant to the maintained versions.


Makefile:213: recipe for target 'tesseract.built' failed

After downloading the repo and install dependencies:
sudo apt-get install g++ # or clang++ (presumably)
sudo apt-get install autoconf automake libtool
sudo apt-get install pkg-config
sudo apt-get install libpng-dev
sudo apt-get install libjpeg8-dev
sudo apt-get install libtiff5-dev
sudo apt-get install zlib1g-dev
sudo apt-get install libicu-dev
sudo apt-get install libpango1.0-dev
sudo apt-get install libcairo2-dev
sudo apt-get install autoconf-archive
running the command:
sudo make leptonica tesseract
I get the error:
.....
Making install in unittest
make[2]: Entering directory '/home/longdt/Desktop/tesstrain-masterr/tesseract-4.1.0/unittest'
make[3]: Entering directory '/home/longdt/Desktop/tesstrain-masterr/tesseract-4.1.0/unittest'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/home/longdt/Desktop/tesstrain-masterr/tesseract-4.1.0/unittest'
make[2]: Leaving directory '/home/longdt/Desktop/tesstrain-masterr/tesseract-4.1.0/unittest'
make[1]: Leaving directory '/home/longdt/Desktop/tesstrain-masterr/tesseract-4.1.0'
Makefile:213: recipe for target 'tesseract.built' failed
make: *** [tesseract.built] Error 2
Please help me, regarding above error.

Please file your issue in the Tesseract repository or even better the Tesseract forum. It is not related to tesstrain.

Got similar error...Any solution to solve this issue

@RonakDedhiya As mentioned above, this is a Tesseract-related issue which is not related to tesstrain. Pls. place an issue there.

@RonakDedhiya, please use the Tesseract user forum for questions. Don't use the issues for that.


Can someone tell me what to fill here in 'k3s.yml' [server: [LOAD-BALANCER-DNS]:6443 # Edit this line]

Environmental Info:
K3s Version: v1.21.7+k3s1

Node(s) CPU architecture, OS, and Version: 2node,centos7.9 x86_64

Cluster Configuration: 2server,1nginx_lb

Describe the bug: >

kubectl get pods --all-namespaces
Unable to connect to the server: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>

Steps To Reproduce:

Installed K3s:

Expected behavior:

Actual behavior:

Additional context / logs:

k3s.yaml

apiVersion: v1
clusters:
- cluster:
    server: https://<IP_ADDRESS>:6443 # nginx ip

/etc/profile

# MySQL
#export K3S_DATASTORE_ENDPOINT="mysql://root:root@tcp(<IP_ADDRESS>:3306)/k3s_xiaowu"
# etcd
export K3S_DATASTORE_ENDPOINT="http://<IP_ADDRESS>:2379"
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
export INSTALL_K3S_VERSION=v1.21.7+k3s1

nginx.conf

stream {
    upstream k3s {
        least_conn;
        server <IP_ADDRESS>:6443  max_fails=3 fail_timeout=5s;
        server <IP_ADDRESS>:6443  max_fails=3 fail_timeout=5s;
    }
    server {
       listen 6443;
       proxy_pass k3s;
    }
}

Backporting

[ ] Needs backporting to older releases

It sounds like you're putting the K3s servers behind an external load-balancer. If you're doing this, you should use the --tls-san flag on your servers to add the hostname and/or IP address of the load-balancer to the certificate.

It sounds like you're putting the K3s servers behind an external load-balancer. If you're doing this, you should use the --tls-san flag on your servers to add the hostname and/or IP address of the load-balancer to the certificate.

thank u,i have finished it


Add MeanAbsoluteErrorResult

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

Project coverage is 100.00%. Comparing base (2aa500d) to head (2624af7).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #268   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           92        93    +1
  Lines         2255      2284   +29
  Branches       207       210    +3
=========================================
+ Hits          2255      2284   +29

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


🐛 .documents: Documented API missing

This a 🐛 bug report.
.documents is not accepting an object as second parameter even though it's documented in the README.
Expected Behavior
var someState = { render: 'me' }

// Documented API:
// `compiler.documents(routename, [opts], done(err, { buffer, hash }))`
compiler.documents('/', {
  state: someState
}, noop)

// Render the document passing `state` to the render function.

Current Behavior
uncaughtException { AssertionError [ERR_ASSERTION]: 'object' == 'function'
    at Bankai.documents (/application/node_modules/bankai/index.js:172:10)
    at Server.http.createServer (/application/server.js:107:17)
    at Server.emit (events.js:189:13)
    at parserOnIncoming (_http_server.js:676:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:109:17)
  generatedMessage: true,
  name: 'AssertionError [ERR_ASSERTION]',
  code: 'ERR_ASSERTION',
  actual: 'object',
  expected: 'function',
  operator: '==' }

Possible Solution
Maybe build on https://github.com/choojs/bankai/pull/446?
Context
I would like to just prerender the document instead of letting the client wait to receive it's initial state via WebSockets.
Code Sample
const server = http.createServer((request, response) => {
  if (request.url === '/') {
    compilerCli.documents('/', { state }, (error, node) => {
      response.setHeader('content-type', 'text/html')
      gzip(node.buffer, request, response)
    })
  }
  compilerHtml(request, response, function () {
    response.statusCode = 404
    response.end('not found')
  })
})

Your Environment

Software
Version(s)

Choo
6.13.3

Maybe @yoshuawuyts ? 🎈


Assignmnet

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
kunzhi-yu
Checklist

[+ ] I can confirm that my changes are working as intended

I updated pull request, please see @kunzhi-yu


Update gpgtools.rb

Closes https://github.com/caskroom/homebrew-cask/issues/28911.
I cannot test this, as I have gpg already installed via brew.
There is an uninstall.sh buried inside the dmg (I do not know why this is not used?), and these are the lines of the script I am attempting to reproduce:
***SNIP***

function rmv () {
	rm -f "$@"
}

***SNIP***

killall -kill gpg-agent

***SNIP***

[[ "$(readlink /usr/local/bin/gpg2)" =~ MacGPG2 ]] && rmv /usr/local/bin/gpg2
[[ "$(readlink /usr/local/bin/gpg)" =~ MacGPG2 ]] && rmv /usr/local/bin/gpg
[[ "$(readlink /usr/local/bin/gpg-agent)" =~ MacGPG2 ]] && rmv /usr/local/bin/gpg-agent

***SNIP***

The uninstall.sh should be added as well.

The uninstall.sh should be added as well.

Done.

@vitorgalvao not sure about this:
>>> brew cask style Casks/gpgtools.rb
== Casks/gpgtools.rb ==
C: 31:  5: %w-literals should be delimited by [ and ].
C: 32: 24: Don't use parentheses around the condition of an if.

Crap, that's what I though it meant! Thanks @vitorgalvao.


Zip file extraction fails due to package name mismatch

When extracting a zip file from Contacts & Organizations package using our utility function zip_subfolder() there is a name mismatch because in that project's cumulusci.yml the project name is "Contacts & Organizations". The function checks each file in the zip to see if the filename starts with this path, and in the zip the filenames are under path "Contacts & Organizations". This results in no files extracted, and exception is thrown when the expected package.xml is not found in the extracted files directory.
reproduce:
From inside Contacts & Organizations repo with packaging org already set up: cci flow run ci_master --org <packaging org>

We could fix this by searching for "&" in the package name and replacing with "&". But first I'd like to understand why it is listed in cumulusci.yml as "&". Seems it should be "&" and escaped as needed for use in URLs.

The formatting difference between the two &'s was lost in translation, but in general I'm not opposed to changing the package name in the cumulusci.yml file for C&O to fix this issue.
However, I have a suspicion there are other tasks that will fail if you change the package name.  We'll need to run the entire build cycle through for the package (ci_feature in scratch org, ci_master and release_beta against packaging, and ci_beta against a scratch org).


[Scenes] Fix SceneTableSize

Currently, the attribute SceneTableSize is dictated by CHIP_CONFIG_MAX_SCENES_PER_ENDPOINT from CHIPConfig.h and doesn't get modified from the Zap configuration.
We need to allow users to defined the size of the scene table by zap from the scenes-server.cpp

If we want this defined via ZAP, why are we doing it via AttributeAccessInterface at all?

Currently we are only getting the SceneCount and RemainingCapacity through the AttributeAccessInterface, SceneTableSize should not rely on it.

Then I am confused.  We're not using CHIP_CONFIG_MAX_SCENES_PER_ENDPOINT for the attribute value... Is this issue then about setting CHIP_CONFIG_MAX_SCENES_PER_ENDPOINT or some equivalent automatically to the largest SceneTableSize set in ZAP across all endpoints?

Yes, that is the actual problem. CHIP_CONFIG_MAX_SCENES_PER_ENDPOINT should be equivalent to the zap parameter, otherwise someone trying to configure a device with a SceneTableSize > CHIP_CONFIG_MAX_SCENES_PER_ENDPOINT would face unexpected Resource exhausted errors.


Merge Input and ContextInput?

TIPs and iota.go will revert so we don't have to do this change anymore.


[Skype] Unstable activities delivery to bot's endpoint through the Skype channel

Bot Info

Bot handle: OrganizerBot
App ID: 6b24e2e7-9aab-42cc-9c57-1a9ab77ecd3b
SDK Platform: REST API
Active Channels: Skype, Telegram
Deployment Environment: Heroku

Issue Description
Hello. Activities sent from Skype (messages, bot addition to contact list, bot removal from, contact list), mainly does not reach bot's endpoint and like 1 of 20 times reaches it with 3-5 min latency. In the same time, activities sent through Telegram work normal. What can cause that behavior?

Hi @TheGreenEvil ,
Can you tell us more about how "activities" are sent in each case?  There really is not enough detail here for anyone to give you much insight.
Sincerely,
IoTGirl

Hi @IoTGirl, thanks for responding. When I talked about "activity", I mean activity object that Microsoft Bot Framework sends to my endpoint on every user action , and I really doesn't know how they sent, on bot sides I am dealing only with receiving and handling them

Are there specific activity object types that exhibit the issue?

Yesterday all activities that I am using in my bot (messages, relation updates) behaved that way. But today seems like messages start to work fine, but relation updates still delivering with 3 min latency

Just to confirm, the same activity on other channels does not have the latency issue, only Skype?

Yes

Hi @TheGreenEvil ,
I have escalated this issue to the Skype Bot Team and they have added it to their backlog (1184801 for tracking).  They would very much like to thank you for reporting this issue and a link to this thread is attached.  If you have any more detail as to the type of relation updates and any differences in timing involved, please don't hesitate to add more details here.
Please note that because the Team runs on an Agile schedule, I can't give you a definite timeline for this to be reviewed in depth but should the team have more questions, they will ask you through this GIT instance.
Sincerely,
IoTGirl

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Disabling a plugin causes floatPrecision to be ignored

Describe the bug
According to the README, the way to disable a single plugin is as follows (svgo.config.js):
const {extendDefaultPlugins} = require('svgo');
module.exports = {
    floatPrecision: 1,
    plugins: extendDefaultPlugins([
        {
            name:   'cleanupIDs',
            active: false,
        },
    ]),
};

However, this seems to cause floatPrecision to be ignored as numbers are no longer rounded.
My input SVG:
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
	 viewBox="0 0 24 24" enable-background="new 0 0 24 24" xml:space="preserve">
<path id="clip" fill="none" stroke="#9160AD" stroke-width="0.25" stroke-miterlimit="10" d="M13.332,9.362l-5.22,5.22
	c-0.614,0.614-0.614,1.535,0,2.149c0.614,0.614,1.535,0.614,2.149,0l7.293-7.293c0.998-0.998,0.998-2.61,0-3.608l0,0
	c-0.998-0.998-2.61-0.998-3.608,0l-7.83,7.83c-1.305,1.305-1.305,3.378,0,4.683l0,0c1.305,1.305,3.378,1.305,4.683,0l8.137-8.06"/>
</svg>

Output without the plugins value in the options (newlines added for readability):
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" xml:space="preserve">
<path fill="none" stroke="#9160AD" stroke-width=".3" stroke-miterlimit="10"
d="m13.3 9.4-5.2 5.2c-.6.6-.6 1.5 0 <IP_ADDRESS> 1.5.6 2.2 0l7.3-7.3A2.5 2.5 0 1 0 14 5.8L6 13.7a3.3 3.3 0 0 0 0 4.6 3.3 3.3 0 0 0 4.7 0l8.1-8"/>
</svg>

Output with the plugins value in the options (newlines added for readability):
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" xml:space="preserve">
<path id="clip" fill="none" stroke="#9160AD" stroke-width=".25" stroke-miterlimit="10"
d="m13.332 9.362-5.22 5.22c-.614.614-.614 1.535 0 2.149.614.614 1.535.614 2.149 0l7.293-7.293a2.548 2.548 0 0 0 0-3.608 2.548 2.548 0 0 0-3.608 0l-7.83 7.83a3.29 3.29 0 0 0 0 4.683 3.29 3.29 0 0 0 4.683 0l8.137-8.06"/>
</svg>

If I specify --precision 1 on the command line it gets ignored in the same way.

Good catch. Fixed it here https://github.com/svg/svgo/commit/d58a7e6089ccf15ecc3928427d55e6b9601094af

Fixed in v2.2.1

I'm afraid, but the bug is still present with the very example I posted originally. It seems like the value of floatPrecision gets inherited into all plugins, except the ones that define their own default value for floatPrecision.


haskell.packages.ghcjs.ghcjs-base: fix build

Description of changes
The latest aeson doesn't build in ghcjs because it includes text-short
in its dependency tree, which hangs on checkPhase because it uses C FFI.
But since ghcjs-base has an upper bound on aeson<1.6 anyway, just
override it.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

cc @dfordivam

Looks good to me


@zeit/next-css link displaying 404

404 page not found
@zeit/next-css
can anyone help me
Thanks

@mritgupta took me quite a while to figure out you meant on nextjs.org/docs. It's fixed now. Next time please follow the issue template.

Yes, it fixed. Thanks, @timneutkens


[Dark Mode] - Scene should have dark and light mode switches.

When the boss comes and leaves the scene should be able to toggle dark and light modes with it's own functions.

Currently implemented with a border outside the canvas element.


add a clean to ensure we do not lock files for a windows build (#50) (merge v2 -> v3)

add a clean to ensure we do not lock files for a windows build

wrong PR


Release on npm not up to date

Thanks for a great library. However, running "npm install" installs version 0.15.0, but not the most recent release. Are there any issues that prevent uploading newer releases to npmjs?

@andialbrecht I have just published to npm the latest version. I forgot to run the command in the latest releases.
Thanks for noticing!

Great, thanks!
José Manuel Pérez<EMAIL_ADDRESS>schrieb am So., 28. Feb. 2016
07:51:

Closed #30 https://github.com/JMPerez/spotify-web-api-js/issues/30.
—
Reply to this email directly or view it on GitHub
https://github.com/JMPerez/spotify-web-api-js/issues/30#event-569573256.


fix fix cu compaction correctness check

Proposed changes
Issue Number: close #xxx
Problem summary
During concurrent import, the same row location may be marked delete multiple times by different versions of rowset. Duplicate row location need to be removed.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

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

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.18 seconds
stream load tsv:          471 seconds loaded<PHONE_NUMBER>9 Bytes, about 151 MB/s
stream load json:         40 seconds loaded<PHONE_NUMBER> Bytes, about 56 MB/s
stream load orc:          68 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230302122011_clickbench_pr_107284.html

run buildall


Path for languages and translations won't work with Hapi 14.1.0

Starting with Hapi 14.1.0, hapi-swagger inserts too many slashes into the language and translations requests. Like:
http://example.org/swaggerui//lang/en.js
http://example.org/swaggerui//lang/translator.js

resulting in 403 - forbidden status codes.
seems to be similar or to be a regression to https://github.com/glennjones/hapi-swagger/pull/273

Hi there I have not been able to replicate this issue. I did find a problem the basePath property related to the double // into side a path which I have fixed in v7.0.0
Could you update to version v7.0.0 and tell me you still have the problem

v7.1 seems to fix this bug. I haven't tested it for older versions.


chore: Stop OSX builds on Travis frequently timing out

See https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
We regularly have OSX builds failing with:
Makefile:125: No code-sign identity found (CODE_SIGN_IDENTITY is not set)
Application version : 1.0.0-beta.19+c817076
Release type        : snapshot
Host platform       : darwin
Host arch           : x64
Target platform     : darwin
Target arch         : x64
Makefile:125: No code-sign identity found (CODE_SIGN_IDENTITY is not set)
./scripts/build/dependencies-npm.sh \
		-r "x64" \
		-v "1.4.4" \
		-t electron \
		-s "darwin"
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

10 minutes is a very long time for this task, though – is there possibly something going on we should investigate?

I suspect Travis is having network connectivity issues, which they're refusing to admit to. I've got an ongoing support email thread with them (which @jviotti is CCed on) because I frequently have to manually restart failed builds, but they're not being very responsive :-/

Another example (again from OSX) where it fails with the same error but in a slightly different place:
><EMAIL_ADDRESS>install /Users/travis/build/resin-io/etcher/node_modules/mountutils
> node-gyp rebuild
  CXX(target) Release/obj.target/MountUtils/src/mountutils.o
  CXX(target) Release/obj.target/MountUtils/src/darwin/functions.o
  SOLINK_MODULE(target) Release/MountUtils.node
><EMAIL_ADDRESS>postinstall /Users/travis/build/resin-io/etcher/node_modules/electron-prebuilt
> node install.js
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

Yeah, looks like timeout issues, or something like that. The build job seem to hang for more than 10 minutes on commands that retrieve stuff from the internet. Lets see how this goes :+1:


Performance (strategical issue)

### Business
- [ ] https://github.com/voedger/voedger/issues/271
- [ ] https://github.com/voedger/voedger/issues/283
- [ ] #292
- [ ] #298
- [ ] #303
- [ ] https://github.com/voedger/voedger/issues/306
- [ ] https://github.com/voedger/voedger/issues/310
- [ ] https://github.com/voedger/voedger/issues/322
- [ ] https://github.com/voedger/voedger/issues/323
- [ ] https://github.com/voedger/voedger/issues/326
- [ ] https://github.com/voedger/voedger/issues/318
- [ ] https://github.com/voedger/voedger/issues/333
- [ ] https://github.com/voedger/voedger/issues/345
- [ ] https://github.com/voedger/voedger/issues/282
- [ ] https://github.com/voedger/voedger/issues/351
- [ ] https://github.com/voedger/voedger/issues/362
- [ ] https://github.com/voedger/voedger/issues/368
- [ ] https://github.com/voedger/voedger/issues/379
- [ ] https://github.com/voedger/voedger/issues/380
- [ ] https://github.com/voedger/voedger/issues/398
- [ ] https://github.com/voedger/voedger/issues/530
- [ ] https://github.com/voedger/voedger/issues/532
- [ ] https://github.com/voedger/voedger/issues/538
- [ ] https://github.com/voedger/voedger/issues/344
- [ ] https://github.com/voedger/voedger/issues/541
- [ ] https://github.com/voedger/voedger/issues/542
- [ ] https://github.com/voedger/voedger/issues/400

### Misc
- [ ] https://github.com/voedger/voedger/issues/299
- [ ] https://github.com/voedger/voedger/issues/342
- [ ] https://github.com/voedger/voedger/issues/382

Migrated to https://github.com/orgs/voedger/projects/11/views/18


lib/systems/platforms.nix: abort on failed platform detection instead of silently assuming pc

This patch causes the autodetection code in lib/systems/platforms.nix to abort if it cannot detect the platform, rather than silently assuming the "pc" platform.
Motivation for this change
I'm about to submit PRs for mips64el that get it to the point where it can bootstrap itself and build all the software you'd normally find on a router.  Much of the userspace currently running on my four octeons was built this way (there is still a Debian /bin, /usr, /etc, but I'm working on getting rid of that).
The silent assumption that mips64el routers are actually Intel PCs caused me an enormous amount of frustration.  My motivation for this patch is to save others from experiencing that frustration when porting nixpkgs to new architectures.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Latest push adds a commit message, no other changes.

Ping...

Yeah this is just ancient back compat. Fully support ripping of the bandaid and doing this. While I am sorry this caused you issues, it is good you can attest to the "helpful" default being actually not so helpful!

Actually on second thought we could also return an {}. This whole module is kind of legacy, but the idea is then one would end up with bank gcc, linux-kernel, and rustc configs, which seems mostly safe?
Really, the linux-kernel  stuff shouldn't be here at all, except for the extent to which the "Kernel headers" derivation relies on it.

Actually on second thought we could also return an {}

Okay, after looking more carefully, yes, that is a better idea.
I pushed a patch implementing this, as well as an additional patch with some comments explaining what (I think) platforms.nix is all about, and why an empty attrset is okay here.  If the comment-commit is incorrect you can just drop it before merging.

Rebased to latest master.

So the result is that you end up with blank configs now rather than pc?

So the result is that you end up with blank configs now rather than pc?

@Mindavi, it appears that you are asking about @Ericson2314's recommended change here: https://github.com/NixOS/nixpkgs/pull/161156#issuecomment-1060040343
This file (lib/systems/platforms.nix) is responsible for supplying just these three attributes: linux-kernel, gcc, and rustc.
Technically you'll get a null for these three attributes.  However it is definitely safe to assume that code using these attributes is prepared to deal with gcc and rustc not being defined, because many of the working entries in this file don't define it.
Regarding linux-kernel the situation is less certain, but some code (lib/systems/default.nix for example) is already designed to deal with that attribute being missing.

I have updated the commit message; the content of the commit is unchanged.

Hopefully this doesn't break everything :)


OTP538u error "object temperature out of range" on Firmata subplatform

When trying to run the examples/javascript/otp538u.js program using the Firmata subplatform, I receive the following error:
                roundNum(tempIRSensor_obj.objectTemperature(), 2) +
                                          ^

Error: UPM Out of Range: objectTemperature: object temperature out of range.
    at Error (native)
    at checkTemp [as _repeat] (/root/test/temp.js:44:29)
    at wrapper [as _onTimeout] (timers.js:275:11)
    at Timer.listOnTimeout (timers.js:92:15)

I bet this is the same issue as in #432. The raw values from the ADC need to be scaled down, thus I will add the option to this driver too. We are actually working towards a generic analog class that will allow setting a scale & offset for calibration and all analog sensors will be modified to incorporate this.

Yes, because even changing the third param to 3.3 results in same error:
// analog voltage, usually 3.3 or 5.0
var OTP538U_AREF = 3.3;

Also, I tried switching the voltage on the shield to 3.3V, but same error.

@jontrulson any thoughts, are the hard-coded coefficients for this sensor potentially causing this? I recall this sensor was incompatible with the G2 and had to be 'customized' to the Edison to some extent.

I remember it being a difficult sensor to work on :)  The issue with G2 was the 'usual' issues I reported with some analog sensors not working well (or at all).  On edison, the sensor worked - I don't recall having to do anything special.  It required a nominal distance from the target of 9cm.
It works my measuring ambient temperature via a thermistor and a lookup table (RT, indexed by computed resistance), then, measuring the thermopile voltage, and with that looking it up in another table (indexed by computed ambient temp and thermopile voltage, IIRC).
The ambient temperature seems to at least be in range or you would be seeing a different exception.  So "something" in the thermopile analog measurement itself or the voltage computation is malfunctioning, since an appropriate range is never found in the VT (thermopile) table, hence the exception.  It thinks the object temperature is either below -20C or above 200C, which seems unlikely, or (more likely) the voltage it's searching for in the table is just really wrong to start with.
As to what that "something" is, debugging would be needed to find out.  Nothing leaps out at me.  First thing to do is get the ambient temperature and maybe work from there.  Does the ambient temperature seem to be reasonable?
Maybe find out what is being computed for 'voltage' at line 180, then look in thermopile_vt_table.hpp and see what is going on.

Looking at the constructor - I do see a potential problem.  And yes, @Propanu, you were correct -- for the Edison we did need to insist on an ADC with a 12 bit resolution, which was not possible on the G2.  That could be why I didn't log it as a problem on G2.
I believe the original Seeed code was using a 1.2v analog ref voltage to get around the 1024 limit of the arduino, since the sensor required 1mV resolution.  Does this firmata platform support 12b ADC resolution?  Maybe something else to look at...

No, Firmata is running on an Arduino 101 and thus is limited to 10-bit resolution only for Arduino IDE compatibility. Would this be a quick fix? To add a line that checks whether we're on a subplatform and then set the resolution in the calculations accordingly?

Well, I'm not sure... It would seem to me that if this is the problem, it would still be working (no exceptions thrown), it just would not be very accurate.
It would be nice to be able to query MRAA to find out the highest available ADC resolution supported - but as you can see right now it is just setting 12b unconditionally, since IIRC mraa_aio_set_bit() is just a scaler and it doesn't care whether the resolution is actually supported by the HW.

Ok, I've committed some changes to the driver that should allow it to work on the 101 via firmata.  There were a couple of issues - the main one being that setting an ADC resolution beyond 10b on the 101 yields nonsensical results.  In addition, after the first ADC read, there seems to be a time period where all ADC reads just return 0, so I've added a hack to the ctor to handle that case - read from both ADC's, discard the results, and sleep for half a second before continuing operation.
Be sure to power the sensor via the 3.3v pin, and make sure to select 3.3v as the aref in the constructor.  The commit is (dc93fb11ff761a8a1b3302c54d9787e93ec663ec).
Good luck.

@deadprogram did the fix work for you?

Hi @Propanu just wondering when version 0.8+ of UPM is going to go live on the 01org repos so the gateways will have this fix available. Thanks!

Hi @deadprogram, the RPMs should be available: https://download.01.org/iotgateway/. Let me know if I can close this. Thanks!

This is now working, thanks very much!

Thanks for the confirmation!


(fix) protect error component against bad input

Signed-off-by: Dan Selman<EMAIL_ADDRESS>Issue #226
Changes

Protect ErrorComponent against non array input.

Flags

cicero-core has also been updated to ensure errors from parse are ParseException

👍 If I understand the comment under "flags" correctly, that means the individual elements within the errors map will always be the correct format that the logger expects since they will always be ParseExceptions? So we do not need to worry about edge cases such as the one originally noted in the issue?

Correct. This is a "belt and braces" fix! :-)


Add wait-for-attachments

Thanks for contributing! 🍄

LINKED ISSUES: Closes #3881

TEST URLS: any page with a comment form

SCREENSHOT:

My first attempt at this was to listen to the change event of the <file-attachment> element and then look at the is-uploading class, but since it's added/removed asynchronously it's much easier to just watch for it. Not to mention the change event can be fired for things that have nothing to do with file uploading, like when the user modifies then deselects the textarea.

I was hoping this was a literal single class to be added since GitHub already has code taking care of the whole operation. I noticed that on upload they call textarea.setCustomValidity("uploading") and the invalidity of the form disables the Comment buttons on the isNewIssue page

I was hoping this was a literal single class to be added since GitHub already has code taking care of the whole operation. I noticed that on upload they call textarea.setCustomValidity("uploading") and the invalidity of the form disables the Comment buttons on the isNewIssue page

Alternatively I see upload:setup and upload:complete being fired, which could make it simple enough

Alternatively I see upload:setup and upload:complete being fired, which could make it simple enough

I rewrote the feature using the suggestions of https://github.com/sindresorhus/refined-github/issues/3881#issuecomment-758372304 and it works great!
The "Close with comment" buttons are unaffected though, do we extend the feature to them too?

I rewrote the feature using the suggestions of https://github.com/sindresorhus/refined-github/issues/3881#issuecomment-758372304 and it works great!
The "Close with comment" buttons are unaffected though, do we extend the feature to them too?

Can you fix the conflicts?


Additionally added Go 1.13 and 1.14 to Travis configuration.

Thanks!


[Bug] Tabline doesn't highlight kebab case filenames

When I have a file with a - character, e.g. foo-bar.ts, the tabline fails to highlight the current selected file.

This  PR fixes: https://github.com/ThePrimeagen/harpoon/pull/290
Just need to ask @ThePrimeagen to merge it XD

Fixed, can you close this PR?


When you change coins and enter in the rate field - values in receive and rate are deleted

Precondition
Wallet created and opened, settings node BTC configured, open tab atomic swap
Steps

click create offer
enter in the Send field "1" and in rate "10"
click in filed Send
click change coin
add in the rate filed "2"

Expected: adds "2" and calculates receive
Actual: in filed rate and receive  values deleted
Video.zip

not fixed
build: 5.0.9065.2877

checked


CustomEvent inheritance change breaks vim-mode in 1.12

This commit, added in 1.12 released a day ago, removes originalEvent from dispatched events. This breaks vim-mode's use of the same event for multiple different keys:
  '1': 'vim-mode:repeat-prefix'
  '2': 'vim-mode:repeat-prefix'
  '3': 'vim-mode:repeat-prefix'

I've poked around at the new events from the vim-mode point of view, and without the originalEvent, there's no way to fix it other than to create tons of unique events, like in this commit, which is so bad I can't bring myself to make a PR out of it.
It seems like the breaking commit is attempting to keep the API the same, but the original event keys are part of the event prototype, not the event, so they're not copied. It looks like there's been some work on that file since the breaking commit, but nothing in the last day or two, so I'm hoping this isn't a duplicate.
For reference, the vim-mode code that's referencing the missing originalEvent is here and here. And the break is pretty dramatic, making vim-mode more or less unusable.

The vim-mode bug, with plenty of :+1:'s, is here: https://github.com/atom/vim-mode/issues/863

/cc @nathansobo @maxbrunsfeld

Will release a hotfix. Thank you.

Fixed in https://github.com/atom/atom/pull/8848


Module 19 - Secure DevOps Kit for Azure (AzSK) replaced by Azure Tenant Security Solution (AzTS)

Module 19 describes the Secure DevOps kit for Azure (AzSK). This kit is being phased out in FY21:
AzSK Sunset Notice
In the next version, the Azure Tenant Security Solution (AzTS) (developed by the same team) should be referenced instead:
Azure Tenant Security Solution

Thanks for your help :) This is a Skillpipe/Slideck related issue , which has been reported internally in other channels. GitHub issues should reflect lab instructions related issues.


Analytic Events not being delivered

Seems that using appcenter_sdk_flutter rather than flutter_appcenter_bundle
Our events are no longer being delivered.
I'd like to know if AppCenter.enable() is enabled on launch.
Seems that awaiting the result of AppCenter.enable() can cause our app to halt launching.
if (!kDebugMode) {
  await AppCenter.start(secret: "xxx");
  await AppCenter.enable();
  await AppCenterAnalytics.enable();
  await AppCenterCrashes.enable();
}

@markst Thanks for issue.
Do you know if it's on Android or iOS or both?

I believe only Android.
here's a version of my main.dart:
void main() async {
  runZonedGuarded<Future<void>>(() async {
    if (!kDebugMode) {
      await AppCenter.start(secret: "bc07463f-240e-49fd-8a5c-6351c11b4b44");
      AppCenter.enable();
      AppCenterAnalytics.enable();
      AppCenterCrashes.enable();
    }

    FlutterError.onError = (final details) async {
      if (details.exception is HttpExceptionWithStatus) {
        // Ignore Cached network errors:
        return;
      }
      await AppCenterCrashes.trackException(
        message: details.exception.toString(),
        type: details.exception.runtimeType,
        stackTrace: details.stack,
      );
    };
    runApp(App());
  }, (Object error, StackTrace stack) {
    log(error.toString(), stackTrace: stack);
    if (kReleaseMode) {
      AppCenterCrashes.trackException(message: error.toString(), stackTrace: stack);
    }
  });
}

ah seems the culprit is just await AppCenter.start(secret: "xx") it never completes so halts the entire app

You're right, it was due to WidgetsFlutterBinding.ensureInitialized.


How to using related_products

How to using related_products. I have using related_products in product.template but it show not found filed related_products

It returns an empty list or an error?


Audit secret holding data types and implement erase on drop

Data types that hold secrets (e.g. PrivateKey) can leave their sensitive data in memory when Dropped and when accidental copies are made.
Consider using something like secrecy that zeroes the memory when dropping.

This is already implemented in tari's keys, the underlying implementation, that's why we don't need to do it.

I saw the impl Zeroize for Scalar so for now we can close this.


Provide .proto files with Editions Syntax and .class files compatible with protobuf-java v4

Is your feature request related to a problem? Please describe.
It is currently not possible to fully use Protobuf Editions in most of my company's protobuf definitions, because the dependency com.google.api.grpc:proto-google-common-protos is not provided in a Protobuf 2023 version. We depend on types like google.type.Date almost everywhere.
Transcompiling our own .proto-Files leads to Java code that is dependent on com.google.protobuf:protobuf-java in v4, but the precompiled classes in com.google.api.grpc:proto-google-common-protos require v3 and there are binary incompatible changes between the two. It is therefore not possible to use com.google.api.grpc:proto-google-common-protos as before.
Describe the solution you'd like
A new version of the library is published that contains .proto files in Protobuf 2023 syntax and .class files compatible with com.google.protobuf:protobuf-java v4.x.y
Describe alternatives you've considered
If no new version of the library is provided by google itself, we'd have to resort to distributing our own company-internal fork of the library that contains the updated .proto files (optional) and .class files precompiled with protoc v4.
Since the Java-Runtime v3 reaches end of support within a year and our company (and I imagine other companies as well) cannot switch all or protobuf over night, this cannot remain unresolved for long.

Hi @joh-ivu, thanks for reporting this issue! This is a known issue to us and we are discussing multiple options with the Protobuf team internally. The solution though, is not likely going to be migrate all the existing protos to Protobuf 2023 syntax.
We are aware that Java-Runtime v3 reaches end of support within a year, so we will provide solutions in the next few months. If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub, which may help us speed up the process.
Separately, is there any new features you want to use from Protobuf Editions?

I am under the impression that proto3-Syntax will still compile for a while, even with newer versions of protoc. So that's not what I'm most worried about. I'm more worried about the protobuf-java dependency so if it's possible to release the same protos, but with .class-files that depend on protobuf-java v4, then that would be fine for me as well.

See the responses 1 and 2 from the protobuf team. They are still figuring out the best way but the good news is the support for 3.25.x is extended to Q1 of 2026.


Add proper SELinux labeling to buildah run

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

@nalind @TomSweeneyRedHat PTAL

@nalind What do you think of committing this, so that @umohnani8 can move forward with here secrets patch.

@nalind Could you take a look at this PR?

We might need to up the --deadline value used in tests/validate/gometalinter.sh a bit.

@nalind passed the tests with the increase of timeout.

CI environments are still skipping the test in selinux.bats.

Ok the problem is not the VM's, the problem is we are running the tests in a docker container and libselinux tells tools in a container that SELinux is disabled.  I will attempt to get the docker command to not fool libselinux.

Adding the following to the docker run command gets libselinux to understand that SELinux is enabled.
-v /sys/fs/selinux/:/sys/fs/selinux -v /etc/selinux:/etc/selinux
Now we will see what this breaks.

Well this is not going to work.  I think it is probably best if we move the packages out of the container to run the SELinux tests.
The problem with turning on SELinux inside the container is rpm will start labeling the content and this is causing it to blow up.

@rh-atomic-bot r+


srs-librtmp win7 build failed

https://github.com/winlinvip/simple-rtmp-server/pull/223
https://github.com/winlinvip/simple-rtmp-server/issues/213
I merge from code of @allspace, but compile failed.
Please fix it in srs-librtmp branch, then I will merge into master.

srs.librtmp see: https://github.com/winlinvip/srs.librtmp
I delete the srs-librtmp branch of srs, for it's ok for srs to export srs-librtmp single file or project.


mc-jones/update contributing readme auth instructions

The contributing doc was outdated after the consolidation of ARTSY_* and CLIENT_* env vars: https://github.com/artsy/force/pull/6261.
The doc has been updated and the ARTSY_ID and ARTSY_SECRET oss env vars have been removed.
https://artsy.slack.com/archives/CP9P4KR35/p1619727446165700

Thank you! 💯


Search Input Clear Button

Regarding the previous ticket (https://app.zenhub.com/workspaces/app-dev-team-646fdb4400ed8c0021aceeb4/issues/gh/bcgov/platform-services-registry/2891), we want to enhance the behavior of the clear button in the search input field.

Display the X button only when there is text in the input field.
Show a hover tooltip explaining the button's function when it is displayed.

works as expected


Optimized coalesce for VSMs.

Added mapAccumulate.
Renamed repartition -> coalesce.

@tpoterba I was addressing your comment (coalesce) and adding a few other improvements.  I will follow up with another commit.

ah, alright.  I assumed you were done and wanted it in per our 3 step triage plan


Demo Hand interaction MRTK2.5.1 deployment error

Describe the bug
Each time I try to build the hololens2 hand interaction demo scene, it builds and compiles in the visual studio editor but then when I try to debug/deploy it throws this error and complains about the two pdb files not being able to be loaded. At that point you can not move forward and you must click stop. It has still deployed in the headset so upon a restart you will be able to open the app. However for debugging purposes, this is not helpful.
(MRTK 2.5.1)
To reproduce
Steps to reproduce the behavior:

New project in Unity versions 2019.4.13f, 2019.4.15f and 2019.4.16f
Open and build the hand interaction demo scene with preset build settings
Open the solution in Visual Studio(2019 enterprise edition)
Set to Debug on the device (hololens2) and then click the play button
Debugger cannot find pdb files and throws an error
Click stop
Reopen the newly deployed app on the device which works

Expected behavior
Build to the device in such a way that debugging is possible
Screenshots

Your setup (please complete the following information)

Unity Version:  2019.4.13f, 2019.4.15f and 2019.4.16f
MRTK Version: 2.5.1

Target platform (please complete the following information)

HoloLens 2

Additional context
Add any other context about the problem here.

Ah yeah, this sounds like a known issue in Unity (@JBrentJ?) we've been running into with UWP. Are you able to debug using a Release build? I've tended to be able to do just about everything I need to do by debugging Release builds instead of Debug builds.

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


WIP: rest: Make backend honor the REST protocol

Codecov Report

Merging #887 into master will increase coverage by 1.23%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master     #887      +/-   ##
==========================================
+ Coverage   53.95%   55.19%   +1.23%
==========================================
  Files          94       94
  Lines        7706     7729      +23
==========================================
+ Hits         4158     4266     +108
+ Misses       2937     2832     -105
- Partials      611      631      +20

Impacted Files
Coverage Δ

src/cmds/restic/global.go
23.35% <0%> (ø)
:arrow_up:

src/restic/backend/test/tests.go
57.74% <100%> (ø)
:arrow_up:

src/restic/backend/rest/rest.go
71.17% <54.16%> (+62.33%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0c2834e...280f05b. Read the comment docs.

Codecov Report

Merging #887 into master will increase coverage by 1.23%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master     #887      +/-   ##
==========================================
+ Coverage   53.95%   55.19%   +1.23%
==========================================
  Files          94       94
  Lines        7706     7729      +23
==========================================
+ Hits         4158     4266     +108
+ Misses       2937     2832     -105
- Partials      611      631      +20

Impacted Files
Coverage Δ

src/cmds/restic/global.go
23.35% <0%> (ø)
:arrow_up:

src/restic/backend/test/tests.go
57.74% <100%> (ø)
:arrow_up:

src/restic/backend/rest/rest.go
71.17% <54.16%> (+62.33%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0c2834e...280f05b. Read the comment docs.


Bug suspected in MS-SSIM\SSIM metric

MS-SSIM was used to measure two image tensors (BxCxHxW),
set reduction flag to None to get the losses without any reduction.
When I executed it, I got an error of size mismatch for this line:
https://github.com/Lightning-AI/metrics/blob/19355a9d2c51b3b39b311694d7b8e6856a73eae6/src/torchmetrics/functional/image/ssim.py#L407
When debugging the code, I realized that the betas repetition one line before is incorrect.
I believe that instead of
betas = torch.tensor(betas).unsqueeze(1).repeat(1, sim_stack.shape[0])
it should be
betas = torch.tensor(betas).unsqueeze(1).repeat(1, sim_stack.shape[1])
The shape of betas after this command should be (len(origin_betas), batch_size), and this is not what actually happens
(betas is already a column tensor, each element is power for each scale,  so we want to repeat it with the amount of the batch size).
In addition, the next two lines raise warnings:
https://github.com/Lightning-AI/metrics/blob/19355a9d2c51b3b39b311694d7b8e6856a73eae6/src/torchmetrics/functional/image/ssim.py#L408
https://github.com/Lightning-AI/metrics/blob/19355a9d2c51b3b39b311694d7b8e6856a73eae6/src/torchmetrics/functional/image/ssim.py#L409

UserWarning: To copy construct from a tensor, it is recommended to use sourceTensor.clone().detach() or sourceTensor.clone().detach().requires_grad_(True), rather than torch.tensor(sourceTensor)

The fix can be:
sim_stack = sim_stack ** betas.to(device=sim_stack.device);   cs_stack = cs_stack ** betas.to(device=cs_stack.device)
(since betas is already a tensor)

Hi @amichayfeldman,
Could you provide an minimal example to reproduce the shape error you are encountering?

I can confirm this bug, I fixed it as part of #1231


Multi symbol operator and array indent

This is what we have for a single symbol operator:
fn =
  first
    $ second
        [ some
        , thing
        ]

An this for multi-symbol:
fn =
  first
    /\ second
      [ some -- smaller line indent
      , thing
      ]

A smaller line indent in this case looks less natural and aesthetic.
Should this be expected?

Yeah, this is to avoid same-column alignment.
-- If you only indent 2 spaces
example =
  foo
    $ case _ of
      A -> B

-- If you always indent an additional 2 spaces
example =
  foo
    >>> case _ of
        A -> b

With the current rule you get
example =
  foo
    $ case _ of
        A -> B

example =
  foo
    >>> case _ of
      A -> B

Since application operators are 1-character, and composition operators are all 3-characters, this issues is pretty common. I didn't want to do arbitrary column alignment against operator width.

Well but anyway, this:
example =
  foo
    >>> case _ of
        A -> B

looks better than this:
example =
  foo
    >>> case _ of
      A -> B

Sure, thanks for the input. The feedback I got during testing was that the same-column alignment for such common cases looked awkward.

For now, this is working as intended. If I see consistent feedback that this is undesirable, I will reconsider it, but I haven't so far.

I had a few samples when I tried to compare, so I'll put them here. In some way, a bigger indent seems a bit prettier to me, though I agree it is not so obvious and noticeable at glance.
Sample 1:
      Array.catMaybes
        $ result.cities
        <#> \city -> do
          name <-
            Map.lookup lang result.langInfo
              >>= Map.lookup city.id
              >>= pure
              <<< _.name
          pure
            { city, name }

And this is formatting with more indentation:
      Array.catMaybes
        $ result.cities
        <#> \city -> do
            name <-
              Map.lookup lang result.langInfo
                >>= Map.lookup city.id
                >>= pure
                <<< _.name
            pure
              { city, name }

Sample 2:

        >>= case _ of
          Left b -> Just b
          Right b -> getBorder b

        >>= \brd ->
          Just
            [ A.strokeWidth (show brd.width)
            , A.stroke (Color.toCssString brd.color)
            ]
            <#> \attrs ->
              [ Svg.path
                  ( [ A.d borderPath
                    , A.fill "transparent"
                    ]
                      <> attrs
                  )
                  []
              ]

Formatting with bigger indentation:

        >>= case _ of
            Left b -> Just b
            Right b -> getBorder b

        >>= \brd ->
            Just
              [ A.strokeWidth (show brd.width)
              , A.stroke (Color.toCssString brd.color)
              ]
              <#> \attrs ->
                  [ Svg.path
                      ( [ A.d borderPath
                        , A.fill "transparent"
                        ]
                          <> attrs
                      )
                      []
                  ]

Sample 3:
    _drawBorder getBorder borderPath =
      Svg.path
        ( [ A.d borderPath
          , A.fill "transparent"
          ]
            <> fromMaybe []
              ( item.borders
                  >>= case _ of
                    Left b -> Just b
                    Right b -> getBorder b

                  >>= \brd ->
                    Just
                      [ A.strokeWidth (show brd.width)
                      , A.stroke (Color.toCssString brd.color)
                      ]
              )
        )
        []

Formatting with bigger indentation:
    drawBorder getBorder borderPath =
      Svg.path
        ( [ A.d borderPath
          , A.fill "transparent"
          ]
            <> fromMaybe []
                ( item.borders
                    >>= case _ of
                        Left b -> Just b
                        Right b -> getBorder b

                    >>= \brd ->
                        Just
                          [ A.strokeWidth (show brd.width)
                          , A.stroke (Color.toCssString brd.color)
                          ]
                )
        )
        []


Unit | Component | sl date time: Computed timezoneString is set and updated correctly

not ok 423 PhantomJS 1.9 - Unit | Component | sl date time: Computed timezoneString is set and updated correctly
    ---
        actual: >
            null
        message: >
            Died on test #1     at test (http://localhost:7357/assets/test-support.js:3025)
                at testWrapper (http://localhost:7357/assets/test-support.js:6192)
                at test (http://localhost:7357/assets/test-support.js:6205)
                at http://localhost:7357/assets/tests.js:23230
                at http://localhost:7357/assets/vendor.js:152
                at tryFinally (http://localhost:7357/assets/vendor.js:33)
                at http://localhost:7357/assets/vendor.js:158
                at http://localhost:7357/assets/test-loader.js:60
                at http://localhost:7357/assets/test-loader.js:51
                at http://localhost:7357/assets/test-loader.js:82
                at http://localhost:7357/assets/test-support.js:6024: 'undefined' is not a function (evaluating 'validTimeZonesArray.includes(this.get('timezone'))')
        Log: |
    ...

Will likely be resolved by https://github.com/softlayer/sl-ember-components/issues/1503

Resolved by https://github.com/softlayer/sl-ember-components/issues/1503


Reduce the amount of dependencies

Currently we depend on Req+Jason, and we can't compile those easily on Fly due to limited memory.
We could make both of those optional by hardcoding the style inside the library, which may be the plan with #17. Then if someone passes a URL or binary as style, we check if Req/Jason is available before continuing.
However, I think this can still be an issue with Kino.MapLibre, because we support multiple styles there by default, right? Maybe we should support only the default style and if someone wants to change it, they can change it in the code?
Thoughts?

Oh, maybe we can support the :style to be an atom and the atom will point to one of the hardcoded styles we have, like the three we use in the Kino?


Automation process to handle issue transfers between opensearch-project repos.

Is your feature request related to a problem? Please describe
Need an automation process to handle transferring of issues between repos. Right now its manual and user tags @opensearch-project/admin group to do the issue transfer, example https://github.com/opensearch-project/security-analytics-dashboards-plugin/issues/964, https://github.com/opensearch-project/observability/issues/1808#issuecomment-1979370370, https://github.com/opensearch-project/dashboards-observability/issues/1483#issuecomment-1979080660 and someone from @opensearch-project/admin do it manually.
Acceptance Criteria
A very high level process using GitHub App and can be improved based on feedback.

Start by creating a generic infra GitHub App (this can be extended for other automations in future).
Add a issueTransfer class for this app that can take care of transferring the issue
Add a label transfer.
GitHub App should respond to this label action (Only maintainers have access to change/add labels per github).
The github app should be generic for multiple purposes.
Looks for the comment from maintainers that has the destination repo.
If no comment then GitHub App should be add a comment as label transfer added but not provided any destination repo.
Transfer the issue.
If failed add a comment as failed transferring with an error message and then tagging @opensearch-project/admin group.
Needs SOP to help maintainers to understand the process.

Describe alternatives you've considered
No response
Additional context
No response

More exit criteria needs to added with different options, due to this can cause a lot of github API calls by the bot.

Similar to https://github.com/opensearch-project/opensearch-build/issues/4455 on the fundamental of github app. Add together.

Test code in progress with probot now.


Bug : select-one is not focusable with Tab key

Because this.input is hidden.
Dirty solution : https://github.com/chymz/Choices/commit/e8a5158db74c610575de768d65e7c96192015b42

Could possibly get round this by giving the input a tabindex attribute.

As of version 1.0.3, single select inputs are now focussable. I think this needs revisiting at some point as once a choice has been selected, the element loses focus (unlike the behaviour of normal select inputs). Happy to add you as a contributer if you have any ideas on getting around this!

Hi !
Thanks for your reactivity :)
On this issue we need to check/fix multiple problems:

Keep focus if one item is selected
If search is set to false focus is good, but we can't navigate with keyboard arrows. Also if we go to the next select with tab key, hideDropdown() is not called ?

I'll try to look this !


Channel configuration for node

With multichannel gateways it can be usefull to send different CFLists in JoinAccept for nodes.

Yes, I agree, this is currently not (yet) possible.

I probably won't implement this. I've just merged an updated way to manage channel configuration into the master branch. This will allow you to configure up to 16 channels in total: https://github.com/brocaar/loraserver/blob/master/docs/content/features/channel-configuration.md.


feat(undo): Numeric option parameter

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

v1.2.0
GitHub release

Your semantic-release bot :package::rocket:


OrderedSet has non-unique items

I'm seeing non-unique elements in an OrderedSet.
 ▿ 17 : <Foo: 0x2835abb80>
  ▿ 18 : <Foo: 0x2835abb80>

(lldb) po storage.seen[18] == storage.seen[17]
true

Information

Package version: 1.0.2
Platform version: 12.2
Swift version: swift-driver version: 1.26.21 Apple Swift version 5.5.2 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)

Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[x] I've searched for existing GitHub issues.

Steps to Reproduce
protocol Hashing: Hashable {
    var uuid: String { get }
}

extension Hashing {
    static func == (lhs: Self, rhs: Self) -> Bool {
        lhs.uuid == rhs.uuid
    }

    func hash(into hasher: inout Hasher) {
        hasher.combine(uuid)
    }
}

final class Foo: Hashing {
    let uuid: String
}

actor Storage {
    private(set) var seen = OrderedSet<Foo>()

    func update(item: Foo) {
        seen.updateOrAppend(item)

        if conditionRequiringReordering {
            seen.remove(item)
            seen.append(item)
        }
    }
}

I've noticed that this isn't always reproducable.
If I do OrderedSet(storage.seen.elements) the duplicates are removed.
Expected behavior
OrderedSet has all unique elements
Actual behavior
OrderedSet has not got unique elements

Is there any chance the uuid of the duplicate items have changed after the item got added to the collection?
I'm asking because Foo is a reference type, which can be prone to such mutations behind the back of the set. If a uuid of an existing item changes, then it will likely no longer be in the right hash table bucket, breaking the collection's invariants, and preventing it from being found.

Hey @lorentey modifying uuid is exactly what happens (by design). It seems your analysis of will likely no longer be in the right hash table bucket is correct and I'll look at an alternative implementation. Thank you.


Delegate custom attributes to images in ChargebackContainerImage

Custom attributes in this report would turn out nil since they actually belong to the container image.
@lpichler Please review
cc @simon3z
@miq-bot add_label bug, chargeback, providers/containers

it turns out the entity was set correctly by ChargebackContainerImage but was overridden by the abstract Chargeback class
cc @isimluk @lpichler

@zeari This is good find.

@miq-bot remove_label euwe/no
@miq-bot add_label euwe/yes

Euwe backport details:
 $ git log -1
commit 40cfb807ee4311dcc85672f23ee61bd0ed4c1ca9
Author: Šimon Lukašík<EMAIL_ADDRESS>Date:   Mon Mar 20 17:52:37 2017 +0100

    Merge pull request #14395 from zeari/delegate_custom_attributes_to_images

    Delegate custom attributes to images in ChargebackContainerImage
    (cherry picked from commit 6d5d478e0bc6f2726bee568d49da070d6e94794a)

    https://bugzilla.redhat.com/show_bug.cgi?id=1434411


ci: remove nodejs 10 tests

Pull Request Test Coverage Report for Build 537003282

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

Totals

Change from base Build 530324126:
0.0%

Covered Lines:
44

Relevant Lines:
52

💛  - Coveralls


[BUG]: Creating Model From EQ

Im not even sure if this is an error with our integration or an issue with the equations extracted
or maybe even the pdf for the test itself
Hmi-server:
2024-06-13T18:46:37.668895623Z 2024-06-13 18:46:37 [INFO] REQUEST COMPLETED | MiraController.convertAMRtoMMT | 1313 ms | method=POST; uri=/mira/amr-to-mmt?project-id=1ba7bfb5-1eee-48e1-aae4-b3735b9b4c6e;  [software.uncharted.terarium.hmiserver.interceptors.RequestLoggingInterceptor:72]
skema-unified (Im assuming this is the right skema container but I have no idea):
2024-06-13T18:45:00.065454773Z httpx.RemoteProtocolError: Server disconnected without sending a response.
Equations:

Project:
https://app.staging.terarium.ai/projects/3215b073-4869-4b1d-8cfb-1c2f961b1108/workflow/6ba011b2-e2f7-4ba2-aeb5-cc6e745b44b0?operator=98d264ef-719c-435d-ba08-23c6a2bb59a3

Being tracked under a different ticket


Migrate perf results and CFT to this repo

migrate our perf test CFT here, as well as all the old results.

PR merged


Filter capabilities

Issue Type: Feature Request
Hi All: could you add filtering by name for tables, programmability and views please?  Thanks for the great work!
Azure Data Studio version: azuredatastudio 1.11.0 (460c739a8d90bdbbde39e01abfb8ecdc278ea787, 2019-09-06T18:08:50.974Z)
OS version: Windows_NT x64 10.0.17763

Closing this as a duplicate of https://github.com/microsoft/azuredatastudio/issues/8052 as some cleanup


draw circle broken when freehand enabled

When the new freehand mode is enabled, it is no longer possible to draw a circle by performing two individual clicks, as was possible in 3.18. For example:

click once to place the centre
click once to place the radius

Without freehand mode (working): https://jsfiddle.net/kuhrmhae/
With freehand mode (broken): https://jsfiddle.net/4advhud2/2/
In the second fiddle, it is only possible to complete the circle by dragging the mouse.  Performing a single click does nothing.
I guess this happened as a result of https://github.com/openlayers/ol3/pull/5970 but have not checked.

You are right, the current behavior in freehand mode is unexpected. I created #6067 to fix it.

When the new freehand mode is enabled, it is no longer possible to draw a circle by performing two individual clicks, as was possible in 3.18.

In 3.18, when the draw interaction was in freehand mode, it was not possible to draw a circle.  See http://openlayers.org/en/v3.18.0/examples/draw-features.html.  If you hold Shift in that example, freehand mode is enabled.  And you cannot draw a circle in that example while in freehand mode (clicks do nothing and dragging creates a zoom box).
@ahocevar's fix in #6067 looks good to me.  But I wanted everybody to be clear that in freehand mode, you draw by dragging (not with two individual clicks).    This part was working in 3.19.0.  The part that was broken was that if you clicked without dragging, drawing would start but not finish.


Sort out problems and get tasks done

I've now finished checking every file on the webpages to sort out things.
This means it's easier to make changes because everything is more organised.
After I merged the previous pull request, this one has been created for sorting out any
other problems / getting tasks done - a few from the older pull request are not finished.
I can improve the formatting on the Questions & Answers / FAQ page to give it a
better appearance (shapes, colour, smaller text) using some code from the contributors
and genetic modification pages. A hyperlink has been added to the nav-bar.
Also, there's the unusual problem on my contributor page (also the Q&A page), where
something unknown is making text look bigger than normal. I've done some comparing of
webpage files, fixed un-closed tags so text after them isn't inside them (gives a different size)
and added the HTML5 document type tag to pages.
After checking the code, I think only content in h3 or h4 tags (headings) has the problem
because other things like the nav-bar don't change their size. An idea to try is finding out the
computed values for CSS font-size. This can be done in Google Chrome or Microsoft Edge,
using the web browser Developer Tools (which also show where the value comes from).
Another option is adding some JavaScript code to a page that shows the results of this function.

Some things done in the previous pull request (and when I checked every file):

[x] A few small changes as well as many more edits to sort out adding
header links code into a new file src/navbar.html and removing it from 14 files.

[x] Older code was replaced with the newer method for including the header nav-bar
code on all pages from the separate file that it was moved it to - getting the nav-bar file
content for each page using a JavaScript library for Asynchronous JavaScript And XML (AJAX).

[x] The style tag is only allowed in the <head>  section of a page - there was some outside it.
However, for any <style> elements that can't be added/moved there, a new scoped attribute
only in HTML5 allows the styles to apply to its parent element and the content of that element.

[x] The reason relative URLs isn't working is probably because Github Pages is only served
over HTTPS on the default domain (there's information about that in repository settings).
To use them in hyperlinks, a HTML tag called <base> can be added on a page. It goes in the
head tag (where it's allowed) with a "href" or "target" attribute, like hyperlinks.
It has the following description and use:

The <base> tag specifies the base URL/target for all relative URLs in a document.
There can be at maximum one <base> element in a document, and it must be inside the <head> element.

Here's some tasks that need to be sorted out:

[ ] A small piece of JavaScript code could be added to your nav-links file (in a <script> tag).
It should contain a call-back function, that runs after the HTML includes JS library you're using
has loaded the nav-links content on a page, which does the following four steps:
(summary: the code adds the "active" style to a navigation link for the current page)

• get a list of all the header navigation link elements and save it to a variable
var link_tags = document.querySelectorAll("body > div.navbar > ul > li > a");
- this uses a function which returns all elements in the document with the chosen CSS selector(s),
as a list of JavaScript element objects (Document Object Model nodes) in a NodeList object.
• run a for loop (that the following steps go inside) to get each item from that list (a DOM node),
using a variable to access them by index number (from 0 to the last item with the .length property).
for (var i = 0; i < link_tags.length; i++) {......}
• do a conditional if statement to compare the href property of the current list item
(complete URL of an anchor node / <a> tag hyperlink) with the complete/full page URL,
to check if they are equal values (==).
There's two similar variables to choose from for the page URL - the page location (seen in a
web browser address bar (location.href) or the HTML document location (document.URL).
I think the first option is a good choice here - the nav-links don't end with "index.html" files.
• when the previous statement is true, set the className property on the list item (node) to
the value "active" so this <a> hyperlink has the class attribute that gives it the right CSS styles. link_tags[i].className = "active";
<script>function nav_links_add_active () {
    // JavaScript call-back function, that "holds back" code
    // to run it after the "HTML includes" JS library has loaded
    // the nav-bar links content (this file) on a page.
    // The small piece of code finds any navigation hyperlinks
    // to the current page and gives them the "active" CSS style.
    [... add code here ...]
}; </script>

Some things done in the previous pull request (#12) and when I checked every file:

[x] A few small changes as well as many more edits to sort out adding
header links code into a new file src/navbar.html and removing it from 14 files.

[x] Older code was replaced with the newer method for including the header nav-bar
code on all pages from the separate file that it was moved it to - getting the nav-bar file
content for each page using a JavaScript library for Asynchronous JavaScript And XML (AJAX).

[x] The style tag is only allowed in the <head>  section of a page - there was some outside it.
However, for any <style> elements that can't be added/moved there, a new scoped attribute
only in HTML5 allows the styles to apply to its parent element and the content of that element.

[x] The reason relative URLs isn't working is probably because Github Pages is only served
over HTTPS on the default domain (there's information about that in repository settings).
To use them in hyperlinks, a HTML tag called <base> can be added on a page. It goes in the
head tag (where it's allowed) with a "href" or "target" attribute, like hyperlinks.
It has the following description and use:

The <base> tag specifies the base URL/target for all relative URLs in a document.
There can be at maximum one <base> element in a document, and it must be inside the <head> element.

Here's some tasks that need to be sorted out:

[ ] A small piece of JavaScript code could be added to your nav-links file (in a <script> tag).
It should contain a call-back function, that runs after the HTML includes JS library you're using
has loaded the nav-links content on a page, which does the following four steps:
(summary: the code adds the "active" style to a navigation link for the current page)

• get a list of all the header navigation link elements and save it to a variable
var link_tags = document.querySelectorAll("body > div.navbar > ul > li > a");
- this uses a function which returns all elements in the document with the chosen CSS selector(s),
as a list of JavaScript element objects (Document Object Model nodes) in a NodeList object.
• run a for loop (that the following steps go inside) to get each item from that list (a DOM node),
using a variable to access them by index number (from 0 to the last item with the .length property).
for (var i = 0; i < link_tags.length; i++) {......}
• do a conditional if statement to compare the href property of the current list item
(complete URL of an anchor node / <a> tag hyperlink) with the complete/full page URL,
to check if they are equal values (==).
There's two similar variables to choose from for the page URL - the page location (seen in a
web browser address bar (location.href) or the HTML document location (document.URL).
I think the first option is a good choice here - the nav-links don't end with "index.html" files.
• when the previous statement is true, set the className property on the list item (node) to
the value "active" so this <a> hyperlink has the class attribute that gives it the right CSS styles. link_tags[i].className = "active";
<script>function nav_links_add_active () {
    // JavaScript call-back function, that "holds back" code
    // to run it after the "HTML includes" JS library has loaded
    // the nav-bar links content (this file) on a page.
    // The small piece of code finds any navigation hyperlinks
    // to the current page and gives them the "active" CSS style.
    [... add code here ...]
}; </script>

After not having time to help with making the website and adding my ideas for it, I chose to merge
all 236 commits (that this repository is behind Magnogen:master) so I have the newest version of his
website and close this pull request because I'm not going to do the task ideas on his website.


Add Grove to TO unit tests and TO API tests Docker images

What does this PR (Pull Request) do?

[x] This PR fixes #4839

#4665 introduced Grove as a dependency of Traffic Ops Golang, so now the unit tests Docker image needs to include Grove. This PR adds it to the Docker image.

#4665 introduced Grove as a dependency of the TO Go client library, and Grove requires golang.org/x/sys/unix. This PR adds Grove and golang.org/x/sys/unix as Traffic Ops API Tests Docker image build dependencies.

Which Traffic Control components are affected by this PR?

Traffic Ops

What is the best way to verify this PR?

docker-compose -f traffic_ops/app/bin/tests/docker-compose.yml up --build

If this is a bug fix, what versions of Traffic Control are affected?

master (78e4b005fc)

The following criteria are ALL met by this PR

[x] This PR fixes an existing test
[x] Bugfix from master only, no documentation necessary
[x] An update to CHANGELOG.md is not necessary
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

#4665 introduced Grove as a dependency of Traffic Ops Golang, so now the unit tests Docker image needs to include Grove. This PR adds it to the Docker image.

I don't object to this fix - but, we should really fix that dependency. TO shouldn't depend on Grove. We should move the grove/web things it needs to lib/go-rfc.

Made sure docker-compose -f traffic_ops/app/bin/tests/docker-compose.yml up --build passes. Thanks for fixing this.
I do agree with @rob05c that we should remove that dependency in the future.

@srijeet0406 or @rob05c - want to create an issue so this doesn't get lost?

@mitchell852 I'll create an issue

@srijeet0406 I just did: https://github.com/apache/trafficcontrol/issues/4841


chore: add WithDebugLogging Option

Add Option WithDebugLogging to allow users starting proxy with NewCommand to enable debug logging.
Improve debug logging for fuse path with additional debug log messages.

Let's port these to AlloyDB too please.


Get/ Set current dateTime in config.xml

Hi everyone,
I am a beginner of norconex http collector,
try to modify the HTML and execute run.bat,
and I am using solr to check the result.
It seem that I have to change the "crawler id" each time otherwise the data will be covered,
than I try to use current dateTime as id
This is what i try to do:
crawler id="datetime()"
But I have no idea how to write the config.xml
"${variable}" become String =.=
after google, CurrentDateTagger may be an potion, but i don't know how to call the api T_T
can anyone give me an example ?

@essiembre
Hi Sir, guess you are the boss here, please safe my life T_T

I would need a better understanding of what you are trying to do.   Typically, you want your initial crawl to crawl everything matching your config settings, then subsequent crawls to only capture additions, modifications, and deletions, updating your Solr index accordingly, making sure there are no duplicates.
It seems you want to do the opposite?  I.e., always crawl everything and never overwrite previously crawled documents, effectively causing duplicates (multiple instances of the same document in your index, but crawled at different times).
If I understand you correctly, there are several ways to do this.  Here are a couple.
Recrawling everything:
The easiest way is to wipe out your "workdir" before you start the HTTP Collector.  More specifically, the crawl store.  That will make it lose the history of whatever was crawled before.
Another option is to disable creating checksums for documents, so it has nothing to compare them on each crawl.  This can be done by adding this to your crawler section:
<metadataChecksummer disabled="true"/>
<documentChecksummer disabled="true"/>

Keeping all instances of a document:
You started well on that one by making the id dynamic.  A more robust approach would be to use a UUID.  In your importer section (as pre or post handler), you can use the UUIDTagger.   If you want to keep track of when each instance of a document was crawled, I recommend using CurrentDateTagger in a separate field (keep UUID as the document reference).

Hi Sir,
Thanks for your reply, sorry for the confusion.
This is my config.xml:

http://localhost/abc.html

1
let say I want to add new url def.html, my config will be:

http://localhost/abc.html
http://localhost/def.html

1
In this case, I have to change the crawler id each time if i do some change(add/update/del).
Or I can do this:

http://localhost/abc.html
http://localhost/def.html

1
In this case, I don't have to change the crawler id. But if I remove the abc.html, the date will also gone.
So I better do this:
<crawler id= CurrentDateTagger ( here should be current dateTime, I don't know how to import or call this API ) >

http://localhost/abc.html
http://localhost/def.html

1
In this case, I don't have to change the crawler id. even I remove the abc.html, the date will still exist.
Am I thinking right ?

You do not need to change the crawler ID if you add/remove URLs in your config, they will be added/removed from your index on the next crawl.

Can you just share your code about set current datetime as crawler ID ?
I try to google "CurrentDateTagger" before but still don't know how to do T__T
plz x 10000
@essiembre

I am trying my best to help, but I am still struggling to understand what you are trying to achieve.    The crawler ID is not meant to change so there is no out-of-the-box way to dynamically update it (using timestamp or else).
The only reason I see why you may want to do this is to start with a "fresh" crawl each time.  If so, disabling the checksummers as suggested earlier should do the same for you.  Another approach is to wipe out your "workdir" before running the crawler.  That will be the same as if you never ran it before.

I just add a complex-config.variables and it work :

but after I create a new dir and run the bat, the "backup" file is missing,
only "latest" file in  norconex-collector-http-2.9.0\newFileName-output\complex\logs
which code handle the backup dir ?

Backup-related code is located here.

thank you, boss <3


[WIP] Update transmission + vaccine numbers for delta.

Issue: #869

massaged the markdown so that the table showed up as intended; addressed percentage display issues exposed by the change from 9% to 14%.

Great work on this @beshaya and @jy2wong !!


feat: support to extract init container failure message

When the pod fails to run, taksrun additionally obtains the init container status to display the error message.
Changes
Now, when an error occurs in the init container, the taskrun clearly displays the error message.
Fixs: #5645
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
When an error occurs in the init container, the taskrun clearly displays the error message.

/kind bug

/kind feature

/kind bug

/kind feature

/test check-pr-has-kind-label

/test check-pr-has-kind-label

/ok-to-test

/test check-pr-has-kind-label

/retest

/retest

fixes https://github.com/tektoncd/pipeline/issues/5645

test

/retest


The refresh token should be revocable

Components
This proposal is about the OAuth2 module of SteemConnect. To be more precise - about the https://steemconnect.com/api/oauth2/token/revoke endpoint.
Proposal
At the moment, there is no way to revoke refresh token via the https://steemconnect.com/api/oauth2/token/revoke endpoint.
Currently, this endpoint revokes the access token provided in the Authorization header.  I believe it would be really useful for developers to be able to also revoke the refresh token.
Mockups / Examples
My proposal is to change the current behavior of the https://steemconnect.com/api/oauth2/token/revoke endpoint. Here is how it IMO could work:

The core concept is that not the access_token provided in the Authorization header is being revoked, but token provided in the request's body.
It would enable a developer to implement revoking both refresh token and access token using the same endpoint.
As you can see, the headers section would include:

Content-Type: application/x-www-form-urlencoded
Accept: application/json
Authorization: <access_token>

and body:

token, the access_token or refresh_token to revoke
token_type_hint, there developer should specify the type of token (access_token or refresh_token) provided in the token field

In my opinion, if token_type_hint was refresh_token, SteemConnect should revoke both access token and refresh token.
If token_type_hint was access_token, SteemConnect should only revoke access token.
For more information check this paper:

https://tools.ietf.org/pdf/rfc7009.pdf

Benefits
With revocable refresh token via the /api/oauth2/token/revoke endpoint, a developer would be able to delete all tokens of the user if one didn't need them anymore. My proposal would enable to use offline scope more safety.
Posted on Utopian.io -  Rewarding Open Source Contributors

The refresh token is just a jwt token signed by our server without any expiration. We don't store it.
So to revoke it just make your app delete it.