Is fork broken?

Hello. I've built latest TSDuck (Windows) but somehow it now crashes when fork plugin is used. Doesn't crash with an older version (3.21-1819).
Here's the ouptut of the latest version crashing:
C:\>tsp --version
tsp: TSDuck - The MPEG Transport Stream Toolkit - version 3.23-1962

C:\>tsp -d -v -b 10000000 -I null -P regulate -P fork "tsp -O ip <IP_ADDRESS>:6000" -O ip <IP_ADDRESS>:15000
tsp: Debug: debug level set to 1
tsp: Debug: ====> tsp -d -v -b 10000000
* Debug: debug level set to 1
* Debug: null: debug level set to 1
* Debug: null: ====> tsp -I null
* Debug: ip: debug level set to 1
* * Debug: registering processor plugin "regulate", status: ok
Debug: ip: ====> tsp -O ip <IP_ADDRESS>:15000
* Debug: trying to load "C:\Program Files\TSDuck\bin\tsplugin_regulate.dll"
* Debug: regulate: debug level set to 1
* Debug: regulate: ====> tsp -P regulate
* Debug: fork: debug level set to 1
* Debug: fork: ====> tsp -P fork 'tsp -O ip <IP_ADDRESS>:6000'
* Debug: tsp: buffer size: 89,240 TS packets, 16,777,120 bytes
* Debug: fork: creating process "tsp -O ip <IP_ADDRESS>:6000"
* regulate: minimum packet burst duration is 2,000,000 nano-seconds
* Debug: null: initial buffer load: 44,620 packets, 8,388,560 bytes
* null: initial input bitrate is 10,000,000 b/s
* Debug: control commands: found 2 packet processor plugins
* Debug: null: input thread started
* Debug: ip: output thread started
* Debug: fork: packet processing thread started
* Debug: regulate: packet processing thread started
* regulate: regulated at bitrate 10,000,000 b/s
* Debug: regulate: new regulation, burst: 2,406,400 nano-seconds, 16 packets

Actually it seems fork plugin wasn't built at all, so when I pasted over the new dlls and exes, the fork plugin remained from previous version and that's probably why it fails. I will try building the installer.

Hi Jan,
Now, the plugin fork and a number of other simple and basic plugins are included in tsduck.dll. There is no longer any tsplugin_fork.dll. If I remember correctly, 8 plugins are now fully included in tsduck.dll. For technical reasons, the code of these plugins was already in tsduck.dll and the DDL's were just triggers to register in tsduck.dll plugins which were already in tsduck.dll. So, to remove useless complexity, the DLL's were removed.
If you build and run an installer, the installation will remove the obsolete DLL's and you will be safe. But if you build the current code of TSDuck inside a build area where a rather old built was performed, the old tsplugin_fork.dll remain. I need to investigate what is the impact of having a builtin plugin and an external plugin with the same name. Maybe this is the root cause of your problem.
Anyway, before building a completely new version of TSDuck, I recommend to cleanup the build area first (make distclean on Linux and macOS, run cleanup.ps1 on Windows).

Checking the code, the presence of a plugin DLL with the same name as a builtin plugin should be completely ignored. So, the problem must be somewhere else. I will look into it.

I did a fresh install of Windows 10 a week ago, so this was the first time I was building TSDuck here. Even with the installer, I'm unable to run the fork plugin. I tried the installer I just built as well as TSDuck-Win64-3.22-1953.exe downloaded from your website. I also tried both Windows portable versions downloaded from tsduck.io. I restarted Windows. Nothing helps.

OK, I found the issue. This is a bug which was introduced between version 3.21 and 3.22. Easy to fix, a silly omission. But the bad news is that the official release 3.22 is affected. So, I need to release 3.23 asap.

I fixed the issue in the repo. You may try it. In the meantime, I start the early unexpected production of official version 3.23.

Thank you, fork is good now.

Version 3.23 is released with the fix.


More coherent scheduling

One approach used near the top-level of client and server is to iterate through a closure until it returns "yes I'm done do the next thing", e.g. fetching network input. Another one used slightly further down is to run things for a set amount of time. We could probably merge these two strategies and get better overall behavior with less code.

In general we want a threading/scheduling mechanism that lets us say:

X thread can't be starved for much longer than T
X thread is more important than Y thread


[1.9.x] Fixed #26026 -- Checked if the QuerySet is empty

https://code.djangoproject.com/ticket/26026

Hi @andersonresende, thanks for your contribution.
Please open a new PR against the master branch instead and commiters will take care of the backport if required. One this is done mark the ticket has ''has patch'' and add a comment pointing to the newly created PR.
In order to prevent future regression you should also add a test to the suite. I suggest you add an additional assertion here where you make sure passing an object that is not an instance of Queryset returns False.

Thanks, I will push again!


Add Temperature Sensor

Is is possible to use the PurpleAir api for a temperature sensor?

Resolved in v3.0.0
Please note the release notes which require sensor(s) to be reconfigured.


Completed HeapSort and updated readme.md assigned to me for hakincodes

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
(Write your answer here.)
Checklist

[ ] I've read the contribution guidelines.
[ ] I've checked the issue list before deciding what to submit.
[ ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

@siddharth25pandey Could u pls check now and review and merge it :)

@Kajol-Kumari pls review asap :)


(PUP-1042) Add setting for puppet apply to write catalog summary

Adds a write_catalog_summary setting that controls whether the classes.txt
and resources.txt are updated after applying a catalog. It preserves existing
behavior, so by default, the agent and device applications and ACE code will
continue to write the summary, while the apply application will not unless the
option is specified on the command line or settings.
Additionally, the puppet apply --write-catalog-summary option (using dashes)
still works and will override what is specified in puppet.conf (using
underscores).

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

Tests are failing on 2.3 because ruby's optparse behaves different before and after 2.4 due to 2.4 normalizing underscores to dashes automatically. I'll need to fix this.


Bug 5390 - [Wdrozenie] [Python] Cache'owanie

https://gist.github.com/romanj/515d0350e7281971d302

:+1:


Unable to decode a nested array of buffers

Attempting to decode an array of buffers in a larger buffer seems to fail.
Here is an example:
import { defineFormat, Type } from "tinybuf";

const Entity = defineFormat(6, {
  id: Type.String,
});

const GameState = defineFormat(7, {
  entities: [Type.Buffer],
});

// Encode
const buffer = GameState.encode({
  entities: [
    Entity.encode({
      id: "e1",
    }),
    Entity.encode({
      id: "e2",
    }),
    Entity.encode({
      id: "e3",
    }),
  ],
});

// Decode
const payload = GameState.decode(buffer);
payload.entities.forEach((entityBuffer, index) => {
  payload.entities[index] = Entity.decode(entityBuffer);
});
console.log(payload);

Here is a live example: https://codesandbox.io/p/sandbox/sxdlyg

It seems like you can fix this by doing the following:
const payload = GameState.decode(buffer);
payload.entities.forEach((entityBuffer, index) => {
  const test = entityBuffer.buffer.slice(
    entityBuffer.byteOffset,
    entityBuffer.byteLength + entityBuffer.byteOffset,
  );
  payload.entities[index] = Entity.decode(test);
});

Not sure if there is a better / more appropriate way of extracting these nested buffers.


Selecting a variable in the linear/graph view shiould also focus it in the stack/variable view

Version and Platform (required):

Binary Ninja Version: 4.0.4958
OS: macOS
OS Version: 14.4.1
CPU Architecture: x64

Bug Description:
Selecting a variable in the Disassembly view does not change focus in the Stack pane.
Steps To Reproduce:

Open Stack pane via new icon in upper right.
Click on a variable.
Observe that the focus in the Disassebly view changes to the selected variable.
Now select a different variable by clicking in the Disassembly view.
Notice that the focus in the Stack pane is still the formerly selected variable.

Expected Behavior:
If I click on a variable in the Disassembly view, the same variable should have focus changed to it in the Stack pane. This behavior would then match what happens in the Variables pane.

This sounds like a nice feature to have. I have spent (wasted) considerable time just trying to locate the same variable in the stack view.
Getting this feature done probably requires certain notification system that we do not yet have. But I remember people have been asking for it, and the debugger might also benefit from it


Add clarity to how to contribute to GitHub Docs

Why:
To clarify where the contribution button is on the GitHub Docs page.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adding where to find the contribution button on the GitHub Docs main page
Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@SmashedFrenzy16 Thanks so much for opening a PR! I'll get this triaged for review :zap:


Keep environment variables on calling plugin

Trying to convert https://github.com/walterwanderley/sqlc-grpc into a plugin

We intentionally limit the environment variables sent to process-based plugins to ensure that those plugins can't easily steal credentials stored in the environment. I'm happy to add an allowlist of variables though and include just those. Which environment variables does your plugin need access to?

Ok, Just need the PATH env.

Merged the other PR, will be available in the next release :)


feat: Display example RPC requests as a useable CURL command

Also displaying generic code snippets for popular languages, as well as in raw JSON format.
A new ExampleRequest component has been made to facilitate this, as well. This component takes a method prop for the name of the RPC method being called, as well as an optional params prop which can pass the object that should be used to populate the RPC request object.
Refs: #565

Preview is available here:http://soroban-docs-pr568.previews.kube001.services.stellar-ops.com/


Possibility to configure without restarting Windows

Hello!
Just wanted to mention that it's perfectly possible to make the configuration and start using it immediately, without restarting the operating system.
The major obstacle to achieve this was of course, the trouble with LanmanServer, as it grabs the 445 port very early, and as you may know, stopping this service doesn't close the port.
But it turns out that it's perfectly possible to close the 445 port in a running system with the command net stop srvnet /y. This command will stop the services Srvnet, Srv2 and LanmanServer, and when that happens, port 445 is no longer listening.
After configuring the portproxy rule, you can then run the command net start LanmanServer, which starts everything back again, while the portproxy keeps active.

Hm, tried that on Windows 11 23H2 and unfortunately did not work - had to restart the system for netstat -an to show expected result...

Thanks for reminding me about this one - I now have access to Windows 11 23H2 myself and your suggestion works beautifully for me.
However, I'd still recommend people to restart -  just to make sure the change is truly persistent.


Local nodemon

This eliminates the global nodemon dependency. It adds nodemon to devDependencies in package.json. It also modifies the npm run dev script so that the locally installed package is used instead.
cc @raquo

Thanks for the good PRs, @brianswisher! I've merged them and released as 2.1.0

Cool, Thanks @raquo! I'll know for next time to have better commit message than "init commit"; it's fine for the branch, but less helpful once it's merged.

Hehe no worries :)


feat(hardware-trezor): whitelist trezor safe 3 device model

Context
This PR enables new Trezor Safe 3 device model
Jira
Important Changes Introduced

Trezor Safe 3 device is whitelisted now

Is it recommended practice from the manufacturer to be so defensive @tomislavhoracek ? Why not make it unrestricted and we can then list the devices that have been tested?

recommended practice from the manufacturer to be so defensive @tomislavhoracek ? Why not make it unrestricted and we can then list the devices that have been tested?

@rhyslbw I'm not sure about the manufacturer but Vacuumlabs suggested and said there is a lack of Trezor Model One support. So we made it more defensive, even in Daedalus.
But I get your point and I agree with you. Maybe we can enable it for all and exclude just Model One support. Then we will have support for the upcoming Safe 5 as well.

Does the VacuumLabs library make a similar guard on the Model One? If not, I think we can just drop it here and leave it up to  applications to implement it if desired.

Does the VacuumLabs library make a similar guard on the Model One? If not, I think we can just drop it here and leave it up to applications to implement it if desired.

I'm pretty sure I saw a guard. But, let me double check that

@rhyslbw ok, there is no classic guard,  in the new @trezor/connect pkg, as before but I found this:
https://github.com/trezor/trezor-suite/blob/develop/packages/connect/src/utils/__tests__/deviceFeaturesUtils.test.ts#L31-L57
Seams like Cardano is not supported at all on Model One.
p.s. T1B1 is Model One and T2T1 is Model T
Shall we keep a guard then?

Nice. Please remove it @tomislavhoracek as it's not the SDK's concern. Do we also have similar guards in the Ledger package?

ve similar guards in the Led

Yeah, we have it in SDK Ledger pkg. But we were just extending support how the devices were released. There is no concern about not supporting Cardano on one of them. I can remove a guard there as well

Great. This will simplify maintenance requirements. Thanks @tomislavhoracek!

Great. This will simplify maintenance requirements. Thanks @tomislavhoracek!

Definitely. Thank you @rhyslbw 🙂


Local paths in wgl.h

Describe the bug
The (apparently machine-generated) file https://github.com/pyglet/pyglet/blob/master/pyglet/gl/wgl.py contains a lot of references to local paths. This may or may not be a privacy issue, but it should be probably be addressed in the generator script.
It's also noteworthy that the backslashes in the multiline strings can generate syntax warnings in recent Python versions.
System Information:
N/A
How To Reproduce
N/A

Thanks for opening the ticket. That file was last regenerated back in 2007 by one of the original authors, so I don't think there is any concern about the file paths in the comments.  :slightly_smiling_face:
Still, no harm in removing them. This spec doesn't change, so it's not useful to keep the comments.
It turns out that in addition to the back-slashes, there were even tab characters in there, so I've stripped those out as well.


Move survey upload to thunk

Summary

[ ] move our survey submission to a Redux thunk

Motivation
Should errors occur reading/writing to Gaia it will protect stability of the app, since the error will be "caught" in the thunk and not passed along to live components. It will also make it easier to debug should these errors occur (credit @Afrogrrrl for the great description)

I can take this


Improve Binary Installation Process for K8s Tools

Issue #, if available:
The method for installing the eksctl and associated commands is not secure as it creates a file in a system-wide directory owned by a user (user = whoever the person is logged in as).
Description of changes:
Cleanup aligned with previous PR
https://github.com/aws/eks-anywhere/pull/5680
Instead of using mv (and chmod in some of the examples), use the "install" command with appropriate flags
ex - replace first line (mv) with the second (install)
sudo mv /tmp/eksctl /usr/local/bin/
sudo install -m 0755 /tmp/eksctl /usr/local/bin/eksctl
Testing (if applicable):
Documentation added/planned (if applicable):
N/A - this is an upd ate, not an add.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve
/cherrypick release-0.18


Database

I wasn’t able to test the application as there was no database data provided with the files. Is there anyway to get a copy of the database backup to run the script?

Yup its seems no DB

you can check on folder assets, brother

you can check on folder assets, brother

I wasn’t able to test the application as there was no database data provided with the files. Is there anyway to get a copy of the database backup to run the script?

you can check on folder assets, brother

I wasn’t able to test the application as there was no database data provided with the files. Is there anyway to get a copy of the database backup to run the script?

you can check on folder assets, brother


Why Access Token is mandatory in configuration for In-Context Editor?

We need to provide user E-Mail and Password in 'PhraseApp Sign in' form when we start translating.
Translator can be another user who did not generate this access token.

Hi @jjustaments - the access token you provide in the configuration does not have to belong to the account signing in to the In-Context-Editor. The access token is only needed to pre-filter blacklisted keys.
So you do not have to create a token for the translator.
Also please note there is currently a issue that prevents Translator accounts from using the In-Context-Editor. This should be fixed within the next few hours, as a temporary workaround you can create a developer account.

Ok, thanks for the explanation.


[WFRP4e System] The submit button doesnt create my character

After going through all of the character creation steps I click on submit in the character creation window but I dont see my character in the Actors tab. In the Chat Messages tab I see that he was created though. I'm not sure if this is a bug or if its a permissions issue but all the other players say they can see their characters in the Actors tab after they created their characters.
ThanksFrom: mrcrabcakes2630foundry: 12.331wfrp4e: 8.2.3wfrp4e-core: 6.0.1wfrp4e-ua1: 6.0.1Active Modules: warhammer-lib

User cannot reproduce


TypeError: Symbol.asyncIterator is not defined.

TypeScript Version:  3.0.0-dev.201 version 2.8.3

Search Terms:
Code
async function* geoJSON(mapConfigurations: DirectionsRequest ): AsyncIterableIterator {
let status = false;
console.log(status);
let result: AcyncIterable = null;
while (!status) {
result = await this.getRouteList(mapConfigurations);
status = !status;
console.log(result);
yield result; // "result" + status + ": " + result;
}
}
export function calculation(req: Request) {
let ps =  JSON.parse(R.prop("0", req.body));
let result: any;
let points =  R.pickAll(["origin", "destination", "waypoints"], ps);
console.log("Points: ", points);
(async function () {
try {
const routeList = new Peer.API.RouteList(points.origin, points.destination, points.waypoints);
              let result_query = routeList.query;
              let jsonX = geoJSON(result_query);

           console.log("calculation", await jsonX.next());

        // routeList.feedback();
        // result = new Peer.API.Tools(xpath, 43, 5);
                    // const xpath = asyncIterable[Symbol.asyncIterator]();
         // await xpath.next().then((str) => result = new Peer.API.Tools(str.value, 43, 5) );
                } catch (err) {
              console.error(err);
            }
         })();
      //   return { distance: result.totalDistance, cost: result.totalPrice, points: result.Polyline };

}

// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.

Expected behavior:
Points:  { origin: '50.001170,36.244462',
destination: '49.920557,36.276551',
waypoints: '50.013326,36.244069|50.034276,36.214594|50.033834,36.171648' }
TypeError: Symbol.asyncIterator is not defined.
at __asyncGenerator (/home/geo/PROJECTS/SERVER-AEP/stage.1-TS-Driverlist/build/compiled/CIM/Peer.js:4:38)
at geoJSON (/home/geo/PROJECTS/SERVER-AEP/stage.1-TS-Driverlist/build/compiled/CIM/Peer.js:314:16)
at /home/geo/PROJECTS/SERVER-AEP/stage.1-TS-Driverlist/build/compiled/CIM/Peer.js:335:29
at Object.calculation (/home/geo/PROJECTS/SERVER-AEP/stage.1-TS-Driverlist/build/compiled/CIM/Peer.js:345:11)
at BlogController.post (/home/geo/PROJECTS/SERVER-AEP/stage.1-TS-Driverlist/build/compiled/routing/controllers/BlogController.js:28:47)
at ActionMetadata.callMethod (/home/geo/PROJECTS/SERVER-AEP/stage.1-TS-Driverlist/node_modules/routing-controllers/metadata/ActionMetadata.js:108:48)
at /home/geo/PROJECTS/SERVER-AEP/stage.1-TS-Driverlist/node_modules/routing-controllers/RoutingControllers.js:92:140
at
at process._tickCallback (internal/process/next_tick.js:182:7)
undefined
client connected
Actual behavior:
tsconfig.json
{
"version": "2.8.3",
"compilerOptions": {
"outDir": "build/compiled",
"lib": [
"es2017",
"esnext.asynciterable",
"dom",
"es2015.promise",
"esnext"
],
"target": "es2018",
"module": "commonjs",
"moduleResolution": "node",
"allowSyntheticDefaultImports": true,
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"sourceMap": true,
"removeComments": false,
"noUnusedLocals": false,
"noUnusedParameters": false,
"noImplicitAny": true,
"declaration": true,
"baseUrl": ".",
"typeRoots": [
"node_modules/@types"
]
},
"include": [
"src//*"
],
"exclude": [
"build//*",
"node_modules",
"tmp"
]
}
Playground Link:
Related Issues:

Please try to come up with a complete example that can be tested on its own -- I see a lot of errors in the code you posted because context is missing.

pls see attached zip.folder in routs.yml U'll find
{  "origin" :  "50.001170,36.244462" ,  "destination" :  "49.920557,36.276551" ,  "waypoints" :  "50.013326,36.244069|50.034276,36.214594|50.033834,36.171648" }
to ctp+C in html localhost:8001
yarn start

Kind Regards Eugene

Вторник, 29 мая 2018, 18:18 +03:00 от Andy<EMAIL_ADDRESS>Please try to come up with a complete example that can be tested on its own -- I see a lot of errors in the code you posted because context is missing.
—
You are receiving this because you authored the thread.
Reply to this email directly,  view it on GitHub , or  mute the thread .

In order to post something as a potential compiler bug it needs to be a contained example -- please try to narrow this down to a short single file that can be posted here in its entirety.

@geomen888 : upgrade the node version to latest.


Update index.md

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks, @scjane :) That was some bad spelling.


Panic when using $nil as a key

Using $nil as a key in a map leads to a panic when accessed:
⬥ elvish
⬥ xx = [&]
⬥ xx[$nil] = foo
⬥ put $xx
▶ panic: interface conversion: string is not hashmap.node: missing method assoc

goroutine 924 [running]:
github.com/elves/elvish/vendor/github.com/xiaq/persistent/hashmap.(*bitmapNodeIterator).fixCurrent(0xc00051c880)
	/opt/pkg/gopkg/src/github.com/elves/elvish/vendor/github.com/xiaq/persistent/hashmap/hashmap.go:437 +0xa5
github.com/elves/elvish/vendor/github.com/xiaq/persistent/hashmap.(*bitmapNode).iterator(0xc0002dda40, 0xc000267d01, 0x166b5c0)
	/opt/pkg/gopkg/src/github.com/elves/elvish/vendor/github.com/xiaq/persistent/hashmap/hashmap.go:423 +0x6d
github.com/elves/elvish/vendor/github.com/xiaq/persistent/hashmap.(*hashMap).Iterator(0xc0002d2c90, 0x1544940, 0xc0002d2c90)
	/opt/pkg/gopkg/src/github.com/elves/elvish/vendor/github.com/xiaq/persistent/hashmap/hashmap.go:65 +0x34
github.com/elves/elvish/eval/vals.Repr(0x1544940, 0xc0002d2c90, 0x8000000000000000, 0x20, 0x4)
	/opt/pkg/gopkg/src/github.com/elves/elvish/eval/vals/repr.go:57 +0x288
github.com/elves/elvish/eval.relayChanToFile(0xc0002ce120, 0xc000010010, 0x15a1074, 0x4, 0xc000430074)
	/opt/pkg/gopkg/src/github.com/elves/elvish/eval/std_ports.go:42 +0xec
created by github.com/elves/elvish/eval.newStdPorts
	/opt/pkg/gopkg/src/github.com/elves/elvish/eval/std_ports.go:26 +0xf9
Exception: elvish exited with 2
[tty], line 1: elvish

I get "Compilation error: variable $nil not found".  What version and system are you running this on?

@doubleagent, you are probably using the stable version. it crashes on master.

Aha. This is not surprising. I have not implemented support for nil keys in the hash map module...


Maybe throw exception if SingleThreadSparkeyReader is used incorrectly

@danielnorberg Any thoughts on this approach?

I think I'd just annotate with @NotThreadSafe and be done with it.
As for this PR, without volatile you might still pay the overhead of the cache line invalidation and get unreliable use detection. Also, I think the JVM might be allowed to freely move or even completely remove the inc/dec. (in which case you won't pay for it but...)

On Jun 3, 2015, at 03:46, Kristofer Karlsson<EMAIL_ADDRESS>wrote:
@danielnorberg Any thoughts on this approach?
―
Reply to this email directly or view it on GitHub.

Note that the volatile is quite affordable if uncontended, especially if it's used by only one thread.

On Jun 3, 2015, at 03:46, Kristofer Karlsson<EMAIL_ADDRESS>wrote:
@danielnorberg Any thoughts on this approach?
―
Reply to this email directly or view it on GitHub.

But as always, JMH to verify.

On Jun 3, 2015, at 03:46, Kristofer Karlsson<EMAIL_ADDRESS>wrote:
@danielnorberg Any thoughts on this approach?
―
Reply to this email directly or view it on GitHub.

Then maybe I should just add synchronized to all methods - that should also be fairly cheap if it's uncontested.

That sounds potentially like an anti pattern.
Regardless, JMH and verify.

On Jun 3, 2015, at 13:50, Kristofer Karlsson<EMAIL_ADDRESS>wrote:
Then maybe I should just add synchronized to all methods - that should also be fairly cheap if it's uncontested.
―
Reply to this email directly or view it on GitHub.


Able to trigger double the selfhost build tasks simultaneously

Not sure how, I think I pressed Ctrl Shift B twice real fast:

Duplicate of https://github.com/microsoft/vscode/issues/141774. There's a difficult to remove delay between when the build command is executed and when the tasks are considered to be running.


Wire generate: Support generics

Is your feature request related to a problem? Please describe.
When I  used wire to build the code with go generics in golang:1.18, but It didn't work and throw some error.
There are some code, command and log in Additional context.
Describe the solution you'd like
I think that wire should support code with go generics as soon as possible for golang:1.18. It must a great power to help developers to build the apps.
Describe alternatives you've considered
Nothing.
Additional context
Code
main.go
package main

import "fmt"

type Message struct {
	Msg string
	V   int
}

func NewMessage(v int) Message {
	return Message{Msg: "Hi there!", V: v + 1}
}

type Greeter struct {
	Message Message // <- adding a Message field
}

func NewGreeter(m Message) Greeter {
	return Greeter{Message: m}
}

func (g Greeter) Greet() Message {
	return g.Message
}

type V interface {
	int | float32
}

func NewV[T V]() T {
	return 2
}

type Event struct {
	Greeter Greeter // <- adding a Greeter field
}

func NewEvent(g Greeter) Event {
	return Event{Greeter: g}
}

func (e Event) Start() {
	m := e.Greeter.Greet()
	fmt.Println(m.Msg, m.V)
}

func main() {
	e := InitializeEvent()

	e.Start()
}

// func main() {
// 	v := NewV[int]()
// 	message := NewMessage(v)
// 	greeter := NewGreeter(message)
// 	event := NewEvent(greeter)
// 	event.Start()
// }

wire.go
//go:build wireinject

package main

// The build tag makes sure the stub is not built in the final build.

import "github.com/google/wire"

func InitializeEvent() Event {
	wire.Build(NewEvent, NewGreeter, NewMessage, NewV)
	return Event{}
}

Command
wire

Error log
wire: ~/test/wire/main.go:27:6: expected ';', found '|'
wire: ~/test/wire/main.go:31:2: expected '}', found 'return'
wire: ~/test/wire/main.go:31:9: expected ';', found 2
wire: ~/test/wire/main.go:27:2: int is not an interface
wire: ~/test/wire/wire.go:10:47: undeclared name: NewV
wire: generate failed

#360 provides a workaround. See comment for details. Note that this may not work for many use cases of generics. Full support is not planned.

Full support is not planned.

Wow.


Update displayed filing date based on changed acceptance criteria

Update displayed filing date based on changed acceptance criteria

PR Moved to a new branch/pr as git wont let me commit anything -> https://github.com/companieshouse/confirmation-statement-web/pull/145


Fix path for Cypress artifacts upload

Cypress has been moved into the tests folder, so we also need to update the PATH for Cypress artifacts used in the upload action.
VR: https://github.com/rancher/elemental/actions/runs/3794824595

The failure of the VR is due to another issue and the videos are uploaded, so this PR is good and can be merged.


FR: Add Cloud NGFW Essential capability with optional Standard or Enterprise based IPS in the TEF 3-networks-hub-and-spoke folder and associated terraform-google-modules

shadow
https://github.com/terraform-google-modules/terraform-example-foundation/issues/1183
TL;DR
A request by a large federal client for IDS or NGFW (formerly Firewall+)capabilities in the TEF that includes GPS(Standard) IPS(Enterprise) and micro segmentation
Add GCP Cloud NGFW (Firewall plus)
NGFW https://cloud.google.com/security/products/firewall?hl=en#cloud-ngfw-tiers
NGFW https://cloud.google.com/firewall/docs/about-firewalls
NGFW enterprise with IPS https://cloud.google.com/firewall/docs/about-intrusion-prevention
https://www.paloaltonetworks.com/blog/network-security/netsec-google-cloud-firewall-plus/
likely location next to https://github.com/terraform-google-modules/terraform-example-foundation/tree/master/3-networks-hub-and-spoke/modules/hierarchical_firewall_policy
Links
GCP Firewall plus - https://cloud.google.com/blog/products/identity-security/introducing-google-cloud-firewall-plus-with-intrusion-prevention
config connector IDS version https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/solutions/ids
Palo Alto VM Series NGFW https://cloud.google.com/architecture/partners/palo-alto-networks-ngfw
PA VM Series NGFW example https://registry.terraform.io/modules/PaloAltoNetworks/vmseries-modules/google/latest/examples/standalone_vmseries_with_metadata_bootstrap
IDS https://cloud.google.com/security/products/intrusion-detection-system?hl=en
https://github.com/GoogleCloudPlatform/terraform-google-network-forensics
standard firewall https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_firewall
Fortinet based Fortigate NGFW https://github.com/fortinet/fortigate-tutorial-gcp
Terraform Resources
No response
Detailed design
No response
Additional information
No response

see https://github.com/terraform-google-modules/terraform-google-network/tree/master/modules/network-firewall-policy
see https://github.com/hashicorp/terraform-provider-google/issues/17030
b/321386368

See ngfw terraform support

https://github.com/hashicorp/terraform-provider-google/issues/15779
https://github.com/hashicorp/terraform-provider-google/pull/18139


HTML with angular in JSON being sanitised

Subject of the issue
Using HTML in JSON with variables/bindings
Your environment

2.11.0
1.5.7
firefox 47

Expected behaviour
HTML from translate JSON should render correctly with links
Actual behaviour
Doesn't load links
I have JSON files with translations, one key include html, such as:
{"content": "<a ui-sref="app.register">Click here to register now"}
I cannot get this to load using .
I have tried using all different useSanitizeValueStrategy's including "null", yet the link refuses to load!

Hi!
Thanks for the report. To help out - can you setup a short Plunker (plnkr.co) so we have a running example to take a look on?

Hello,
this is a general reminder: We are still waiting for your reply with additional details. If you cannot help us, we cannot help you.
Looking forward to hear from you.

Hello,
I'm closing this issue due inactivity. We have asked for additional details, but you could not helped us. Therefore we close this issue as not reproducible.
If you still have an issue, please create a new issue because we cannot be sure to track closed issues.


You CAN edit security roles for Application users now.

The documentation incorrectly states (regarding Application users) "The security role that is assigned to these accounts cannot be updated either. This is to prevent any service outages."  This functionality now exists in the Power Platform admin center.  New security roles may be assigned and existing ones may be removed.

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

ID: 436a3b84-3edb-8d4e-bc7e-51488b8f879a
Version Independent ID: 634e9777-62b1-01e6-6db1-eafbfe5d8d7d
Content: Special system users and application users - Power Platform
Content Source: power-platform/admin/system-application-users.md
Service: power-platform
Sub-service: admin
GitHub Login: @paulliew
Microsoft Alias: paulliew

@Turbo549, thanks for letting us know about this.  The content has now been updated.  The updated content will be published at noon, Pacific time.


vertex color

Hello,
Some applications (like meshlab) append rgb values to vertex lines. From wikipedia:

Some applications support vertex colors, by putting red, green and blue values after x y and z. The color values range from 0 to 1

When I tried the tool with obj file with vertex color, the output obj lost the color. Would it be possible to enhance the tool to keep vertex color?

I used this project for my meshes that have color information supplied in the vertices. All you have to do is add a Vec3 after the position and average the two vertex colors when collapsing an edge. There's also a function called `compact_mesh that copies vertices, so you have to make it copy the color info too. You really only end up adding like 4 lines to the code and the simplification retains all color info perfectly.

@Lin20 your solution is a good one. Since this message was posted, the repository has been updated to track OBJ format texture coordinates. The TEXCOORD attribute could provides a template for how to handle per-vertex colors. In other words, the TEXCOORDs intepolate across a 2D texture (u,v), while for vertex colors you will want to interpolate the Red, Green and Blue components (r,g,b).


Support object values for MDLC

Like https://github.com/NLog/NLog/pull/743
for
https://github.com/NLog/NLog/pull/833

@304NotModified I completed it. Do you want to pull request?

PR is always good :)

PR merged!

Thank you! What is the right time to update MDLC wiki page for this update?

before release I think.

Should we remove the 'needs document on wiki' label as it documented?

That's possible. But I ignore those labels on closed issues.
Do you think it's better to remove it?

Not sure.
It seems that it is a reminder to document, so it should be removed when complete the documentation task for clarity of next search result.
It also seems that it is a step to close the issue. Such as: You should not close unless to complete the documentation. Otherwise you may forget to document it.
Also it seems that this discussion is trivial thing :) Forget.


ID-947 Upgrade logback to fix vulnerability. Take 2.

I accidentally only upgraded it for the migration last time wooops. This time I double checked with a dependency scan.

I had to also upgrade terra-common-lib because it was referencing an old logback fn


[AutoPR dns/resource-manager] DNS multi-api Python

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3354

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2874

(message created by the CI based on PR content)


can't move '/etc/nginx/conf.d/service.conf

parsons-web_1  | start nginx
parsons-web_1  | ssl_key=le-key.pem, ssl_cert=le-crt.pem
parsons-web_1  | sed: can't move '/etc/nginx/conf.d/service.confaAMhFd' to '/etc/nginx/conf.d/service.conf': Resource busy
parsons-web_1  | sed: can't move '/etc/nginx/conf.d/service.confOAlfDc' to '/etc/nginx/conf.d/service.conf': Resource busy
parsons-web_1  | '/etc/nginx/conf.d' -> '/etc/nginx/conf.d.disabled'
parsons-web_1  | start letsencrypt updater
parsons-web_1  | trying to update letsencrypt ...
rhel 7 | 3.10.0-327.36.1.el7.x86_64
Docker version 1.12.2, build bb80604

seems like modern docker doesn't allow mv to mounted files anymore.  Had to change this sed part to work on non-mounted resource. Should be fixed.

thanks!
but something strange happens when trying to verify the domain, letsencrypt say:
"The server could not connect to the client to verify the domain :: Could not connect to..."
maybe nginx not have time to run... i mean sleep 5;

5sec should be enough to start nginx.
Are you sure your server accessible from outside on 80? I mean firewall, NAT, things like this

yes, i check this in first thing...
I'm doing build image with sleep 10 for example and try to check problem...

and I guess you set LE_FQDN, right? Anyway, if you can post full output of letsencrypt it may help.

yes np
docker-compose.yml:
parsons-web:
restart: always
image: umputun/nginx-le
volumes:
- ./etc/ssl:/etc/nginx/ssl
- ./etc/nginx-service.conf:/etc/nginx/service.conf
- ./public_html:/var/www/parsonstemp.boloinc.com/public_html:ro
environment:
- TZ=Canada/Central
- LETSENCRYPT=true
-<EMAIL_ADDRESS>- LE_FQDN=parsonstemp.boloinc.com
ports:
- 80:80
- 443:443

docker-compose up

Creating network "callbackend_default" with the default driver
Creating callbackend_parsons-web_1
Attaching to callbackend_parsons-web_1
parsons-web_1  | start nginx
parsons-web_1  | ssl_key=le-key.pem, ssl_cert=le-crt.pem
parsons-web_1  | '/etc/nginx/conf.d' -> '/etc/nginx/conf.d.disabled'
parsons-web_1  | start letsencrypt updater
parsons-web_1  | trying to update letsencrypt ...
parsons-web_1  | Failed authorization procedure. parsonstemp.boloinc.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Could not connect to parsonstemp.boloinc.com
parsons-web_1  | IMPORTANT NOTES:
parsons-web_1  |  - If you lose your account credentials, you can recover through
parsons-web_1  |    e-mails sent to<EMAIL_ADDRESS>parsons-web_1  |  - The following errors were reported by the server:
parsons-web_1  |
parsons-web_1  |    Domain: parsonstemp.boloinc.com
parsons-web_1  |    Type:   connection
parsons-web_1  |    Detail: Could not connect to parsonstemp.boloinc.com
parsons-web_1  |
parsons-web_1  |    To fix these errors, please make sure that your domain name was
parsons-web_1  |    entered correctly and the DNS A record(s) for that domain
parsons-web_1  |    contain(s) the right IP address. Additionally, please check that
parsons-web_1  |    your computer has a publicly routable IP address and that no
parsons-web_1  |    firewalls are preventing the server from communicating with the
parsons-web_1  |    client. If you're using the webroot plugin, you should also verify
parsons-web_1  |    that you are serving files from the webroot path you provided.
parsons-web_1  |  - Your account credentials have been saved in your Certbot
parsons-web_1  |    configuration directory at /etc/letsencrypt. You should make a
parsons-web_1  |    secure backup of this folder now. This configuration directory will
parsons-web_1  |    also contain certificates and private keys obtained by Certbot so
parsons-web_1  |    making regular backups of this folder is ideal.
parsons-web_1  | cp: can't stat '/etc/letsencrypt/live/parsonstemp.boloinc.com/privkey.pem': No such file or directory
parsons-web_1  | cp: can't stat '/etc/letsencrypt/live/parsonstemp.boloinc.com/fullchain.pem': No such file or directory
parsons-web_1  | '/etc/nginx/conf.d.disabled' -> '/etc/nginx/conf.d'
parsons-web_1  | reload nginx with ssl
parsons-web_1  | 2016/10/19 15:16:33 [emerg] 27#27: BIO_new_file("/etc/nginx/ssl/le-crt.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/nginx/ssl/le-crt.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
parsons-web_1  | nginx: [emerg] BIO_new_file("/etc/nginx/ssl/le-crt.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/nginx/ssl/le-crt.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
^CGracefully stopping... (press Ctrl+C again to force)
Killing callbackend_parsons-web_1 ... done

I think understand what the problem is:
mv -v /etc/nginx/conf.d /etc/nginx/conf.d.disabled
/etc/nginx/conf.d/default.conf point to  /usr/share/nginx/html;
and listen 80 port...

yeah, i was able to reproduce it and hopefully got it fixed. Give it a try pls, but it worked for me just fine on fresh DO droplet

oh... thanks for quick response... i also create pull request with this fixes :)

sorry for this, but we have problem again:
server_name _;
return 301 https://$server_name$request_uri;

and we have redirect to https://_

it is not a problem, but may confuse the user... i mean default nginx config


Update OpenTelemetry packages

Description
Updates Steeltoe to depend on stable OpenTelemetry packages, where available. Fixes broken build.

EnableGrpcAspNetCoreSupport was replaced by environment variable OTEL_DOTNET_EXPERIMENTAL_ASPNETCORE_ENABLE_GRPC_INSTRUMENTATION, see https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/test/OpenTelemetry.Instrumentation.Grpc.Tests/GrpcTests.server.cs
Replace usage of IDeferredTracerProviderBuilder, see https://github.com/open-telemetry/opentelemetry-dotnet/issues/4228

Quality checklist

[x] Your code complies with our Coding Style.
[x] You've updated unit and/or integration tests for your change, where applicable.
[ ] You've updated documentation for your change, where applicable.
If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
[ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.

/azp run Steeltoe.All


craft ai js client v2.0

We have already identified stuffs that should be improved for this v2.

[ ] Remove deprecated functions
[ ] Add an explicit method destroy (or terminate to the client) to release hanging sockets
[ ] Remove support for anything before Node v6
[ ] Get rid of babel
[ ] Find a way to run unit tests in the browser as part of the CI
[ ] Get rid of moment (#95)
[ ] Get rid of as much as possible from lodash
[ ] Accept iterators in functions taking a list of stuffs
[ ] Better management of the rate limiting of the API #131

Let us know what you'd like in this upcoming release.

validation tools

Support taking decisions from operations #122.


Initial work on decoupling plugins from creation flow

This PR includes the initial foundations for allowing us to selectively disable plugins. Starts to address the concerns uncovered in #55
Includes:

New table for Plugins
UI and API for viewing an editing plugin state
Selectively disables the 'ticket' plugin and uses the dispatch admin UI instead
Links a plugins .enabled() function with what is stored in the database
Adds newly installed plugins to the database and enables them

Not Included in this PR but will be in future PRs:

Any ability to store the configuration of the plugins or a way to interactively test whether they are working.

Looks good to me. Just a few nits here and there. Awesome contribution!


About the use of single 4090 GPU for training

Hello, I am using a single 4090 24G GPU to train train_movielens.sh, I have changed the batchsize from 4 to 1 as set in your script, and I have increased the accumulate_grad_batches, but I am still getting the error Out of memory. According to my understanding you are using single A100 80G GPU for training, the 24G GPU I am using should be enough to train finetuning with batchsize=1, and I think 24G GPU should be enough to fine-tune the model of LLAMA 7B with LORA, so I am not sure why it will report an error? I wonder if you would be willing to help me with this? Are there any other friends who can share their experiences？
Thanks.

Thanks for your attention to our work. Perhaps the problem is that the Llama model itself takes up a certain amount of GPU memory.


Disabling VBO in DisplayList for ATI/AMD graphic cards is not relevant anymore

In file "gl.cpp".
At line 1982.
There is a method "glglue_check_ati_vbo_in_displaylist_bug(...)".
This method is called at line 2525 in same file.

=> This method should be deleted, and no longer called, because the problem has been solved a long time ago by ATI/AMD.

Thanks again Yves for your issue thorough report.


Refactor all machine

Cool! I guess once this is merged we can start the PR against the develop branch :)

@LiuYuHui Can I merge this?

@LiuYuHui Can I merge this?

@gf712 yes :D


Certificate Conversion to Base 64 - HA RKE Add-on Install

There's lots of room for error when converting certificates to base 64. Make visuals and gifs. Improve existing content.

As this install is no longer supported in v2.1.0+, we don't need to add these docs.


Calculated DMRG-CASCI energy too high

Hi,
I've performed a DMRG-CASCI(18,18)/cc-pVDZ computation for the tetracene molecule, where (18,18) is just the active space containing Pi bonding and anti-bonding orbitals. Using GVB orbitals as the initial guess (orbital shape similar to Pipek-Mezey localized orbtials), I've compared the results from Block and QCMaquis:
QCMaquis: different values of nsweeps are tested
nsweeps = 5, E = -688.897193 a.u.
nsweeps = 9, E = -688.897265 a.u.
nsweeps = 15, E = -688.897297 a.u.
Block: -688.899740 a.u.
max_bond_dimension = 1000 is used among all calculations. It seems the DMRG-CASCI energy of QCMaquis slowly becomes lower with the increase of nsweeps. Is there any option or keyword to accelerate the convergence (e.g. orbital ordering, do not canonicalize localized orbitals, etc)?
The OpenMolcas input file is attached
tetracene_cc-pVDZ.zip
Thanks for any suggestion!

There are several ways to accelerate convergence in QCMaquis, one recommended way is to use the Fiedler orbital ordering and CI-DEAS. To enable them in the OpenMolcas interface, you may use the Fiedler and CIDEAS keywords of the DMRGSCF module (see https://molcas.gitlab.io/OpenMolcas/sphinx/users.guide/programs/dmrgscf.html). Additional possibility is to use the perturbative correction in the first several sweeps. This can be achieved e.g. with the following QCMaquis input (to be added to the RGInput...EndRG or DMRGSettings...EndDMRGSettings block in OpenMolcas):
nsweeps = 10
ngrowsweeps = 2
nmainsweeps = 3
alpha_initial = 0.0005
alpha_main = 1e-5
alpha_final = 0
twosite_truncation = heev

Thanks for your help @kommerck .
I tried some options with a fixed nsweeps = 9:
E = -688.897265 a.u. (using &RASSCF and RGinput)
E = -688.897250 a.u. (using &DMRGSCF)
E = -688.897254 a.u. (using &DMRGSCF and Fiedler = ON)
These energies differ little. When I tried the perturbative correction, an Intel MKL error occurred
Intel MKL ERROR: Parameter 10 was incorrect on entry to DSYEVD.

We can speculate the error is due to an improper SVD on a matrix, but I do not know how to solve the problem. Or, if there is any other suggestion?
Files are attached. Many thanks.
tetracene_perturb.zip

Unfortunately I cannot reproduce the intel MKL error, your input runs fine for me. Have you compiled OpenMolcas/QCMaquis with ILP64 MKL interface?
Also using Fiedler=ON and perturbative correction (both at the same time), I get an energy of -688.8997325 a.u. after only two sweeps.

Sorry for the delayed feedback. Yes, the OpenMolcas/QCMaquis is compiled with ILP64 MKL interface. I conclude this from
ldd rasscf.exe | grep 'lp'
ldd dmrgscf.exe | grep 'lp'

the results are
libmkl_gf_ilp64.so => /opt/intel/compilers_and_libraries/linux/mkl/lib/intel64/libmkl_gf_ilp64.so (0x00002af8a5e60000)
libalps.so => /home/jxzou/software/OpenMolcas_q/bin/./../qcmaquis/lib/libalps.so (0x00002af8ac526000)

Then I thought maybe the version of GCC matters, or a re-compilation might solve the MKL error. However, the same error occurs after I tried these boring things. On the other hand, using no perturbative correction, and nsweeps = 40, the energy is -688.897320 a.u.
Could you please tell me your versions of GCC, GSL, HDF5, BOOST, Intel MKL, OpenMolcas and QCMaquis? I want to take a try using your versions. I think maybe versions of MKL or QCMaquis matters.

Thank you. I used the same input file in tetracene_perturb.zip. All versions of packages are the same as described in 278, the calculation is run on the same node. The only difference is this time I specify LINALG=Internal.
And I downloaded the lapack-3.9.0.tar.gz and unzip it into External/lapack/. If I did not do that, this directory is empty and compilation of OpenMolcas will result
CMake Error at CMakeLists.txt:1861 (message):
   LAPACK+BLAS sources not available, run "/usr/bin/git submodule update --init /home/jxzou/software/OpenMolcas_q1/External/lapack"

But my node cannot access to the Internet. So I manually downloaded lapack-3.9.0.tar.gz and unzip it into External/lapack/. After successful compilation, running ldd dmrgscf.exe|grep lp leads to
        libalps.so => /home/jxzou/software/OpenMolcas_q1/bin/./../qcmaquis/lib/libalps.so (0x00002b73f0d8f000)

And ldd dmrgscf.exe|grep mkl leads to
        /opt/intel/mkl/lib/intel64/libmkl_rt.so (0x00002ba5b19cb000)

So I supposed LINALG=Internal worked. Then the DMRG-CASCI(18,18) energy is -688.897228 a.u., which is still 2 mH higher. Adding Fiedler=ON leads to -688.897226. I've uploaded the output file, which may do some help.
tetracene_perturb1.zip
Sorry for the lengthy descriptions.

With modifying your OpenMolcas input after Gateway/Seward to
&DMRGSCF
ActiveSpaceOptimizer=QCMaquis
Fiedler=ON
OOptimizationSettings
Charge = 0
Spin = 1
RAS2 = 18
nActEl= 18 0 0
FILEORB = tetracene_cc-pVDZ_uhf_gvb42_2CASCI.INPORB
CIonly
EndOOptimizationSettings
DMRGSettings
 conv_thresh = 1E-7
 max_bond_dimension = 1000
 nsweeps = 6
    ngrowsweeps = 2
    nmainsweeps = 3
    alpha_initial = 0.001
    alpha_main = 1e-4
    alpha_final = 0
    twosite_truncation = heev
EndDMRGSettings

Thanks. I copy your input and submit two jobs. For the LINALG=MKL version, it leads to the same MKL DSYEVD error. While for the LINALG=Internal version, the result is strange
 Fiedler orbital ordering: 9,10,6,13,3,5,16,14,1,18,1
terminate called after throwing an instance of 'std::runtime_error'
  what():  Number of orbitals in the orbital order does not match the total number of orbitals

Program received signal SIGABRT: Process abort signal.

Maybe this is a truncated line? Files are attached.
tetracene_perturb2.zip

Are you using the latest QCMaquis version? Your output shows QCMaquis version 3.0.1, whereas we are at 3.0.3.

Yes, I used QCMaquis 3.0.1, as I said in 278. I'll try 3.0.3.

Hi, QCMaquis-3.0.3 works excellent! By using your recommended input,
for LINALG=Internal, I got -688.899738 a.u. within 6 nsweeps (cost 1h 55min);
for LINALG=MKL, keeping the perturbative correction still leads to MKL DSYEVD error. But remove the perturbative correction, I got -688.899741 a.u. within 6 nsweeps (cost 26min).
I'll use QCMaquis >= 3.0.3, no perturbative correction and LINALG=MKL for OpenMolcas in the future.
By the way, anything updated in QCMaquis-3.0.3 concerning MKL DSYEVD?

Which distribution are you using? So far I could not reproduce that error (I know you listed your software version in the OpenMolcas issue, but I'm interested specifically in the distribution so that I can fire up a Docker image to test it).
The DSYEVD call in question is wrapped by Boost numeric bindings, which we provide as part of the ALPS/Boost distribution, so I cannot immagine they could be doing something wrong.

Oh, I just realize that maybe you are asking me the Linux distribution. It's CentOS 7.4.1708. More specifically, the result of command cat /proc/version is
Linux version 3.10.0-693.el7.x86_64<EMAIL_ADDRESS>(gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Tue Aug 22 21:09:27 UTC 2017

The result of command lsb_release -a is
LSB Version:    :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.4.1708 (Core)
Release:        7.4.1708
Codename:       Core


Added money editing options

I think it would be good to be able to edit money as well :-)
A localization for all languages for the CEMoney key has also been added.

Damn... I accidentally committed localized comments in Resources.Designer.cs (I don't know how I did it) so you can ignore this file and add it manually
        public static string CEMoney {
            get {
                return ResourceManager.GetString("CEMoney", resourceCulture);
            }
        }

Damn... I accidentally committed localized comments in Resources.Designer.cs (I don't know how I did it) so you can ignore this file and add it manually
<data name="CEMoney" xml:space="preserve">
    <value>Money</value>
</data>

Visual Studio 20XX regen automaticaly Resources.Designer.cs each time you update Resources.resx.
All *.Designer.cs should not be edited manually (except at merge time maybe).

Visual Studio 20XX regen automaticaly Resources.Designer.cs each time you update Resources.resx. All *.Designer.cs should not be edited manually (except at merge time maybe).

So should I fix it or can you handle it? I would have to create a new PR for that.

carding and loading is an act to be done by legitimate people
need verification on how to get quick cc , PayPal transfers and more ?
have you been looking for a place to buy cc and get legit money TRANSFER services like PayPal,  western union and more ?
visit https://t.me/credit_card_uk

Visual Studio 20XX regen automaticaly Resources.Designer.cs each time you update Resources.resx. All *.Designer.cs should not be edited manually (except at merge time maybe).

So should I fix it or can you handle it? I would have to create a new PR for that.

I don't understand why you can't update your own PR ? Push a commit that fix your branch mimic2300:feature/gold_edit ?

Conflict fixed

Moved to: https://github.com/EtienneLamoureux/TQVaultAE/pull/444


Simple example. Typescript error?

Could you please provide a small example of working with this library with Typescript?
Like, I want to use this in my render function:
    <Spring
      from={{ opacity: 0 }}
      to={{ opacity: 1 }}>
      {props =>
hello
}
    </Spring>

It causes Typescript type errors and I don't know how to solve it :( Apparently there should be a way to work with this on Typescript since there are definitions etc. But I can't figure how.
Type '{ children: (string | ((p: {}) => Element))[]; from: { opacity: number; }; to: { opacity: number; }; }' is not assignable to type '(IntrinsicAttributes & IntrinsicClassAttributes<Spring<{}, {}>> &
Readonly<{ children?: ReactNode; }> & Readonly<SpringProps<{}, {}>>) | (IntrinsicAttributes & IntrinsicClassAttributes<...> & Readonly<...> & Readonly<...>)'.
  Type '{ children: (string | ((p: {}) => Element))[]; from: { opacity: number; }; to: { opacity: number;
}; }' is not assignable to type 'Readonly<SpringProps<{ children: (string | {})[]; from: { opacity: number; }; to: { opacity: number; }; }, { opacity: number; }> & { children: (string | {})[]; from: { opacity: number; }; to: { opacity: number; }; }>'.
    Types of property 'children' are incompatible.
      Type '(string | ((p: {}) => Element))[]' is not assignable to type 'SpringRendererFunc<{ children: (string | {})[]; from: { opacity: number; }; to: { opacity: number; }; }, { opacity: number; }> & (string | {})[]'.
        Type '(string | ((p: {}) => Element))[]' is not assignable to type 'SpringRendererFunc<{ children: (string | {})[]; from: { opacity: number; }; to: { opacity: number; }; }, { opacity: number; }>'.
          Type '(string | ((p: {}) => Element))[]' provides no match for the signature '(params: { opacity: number; } & { children: (string | {})[]; from: { opacity: number; }; to: { opacity: number; }; }): ReactNode'.

There was just a new PR that i merged yesterday, hopefully it fixes it. All TS types for this lib are done by contribution (since i myself don't use/know TS). I released it under<EMAIL_ADDRESS>could you try if that makes it better?

My bad, I found an issue and it wasn't a bug. You should place props in brackets & specify type: any & place function body part in brackets too. So now it is (props:any)=>(some jsx) and it is no error in Typescript.
May be it will be a good idea to add this note in examples for TS users.
This works:
<Spring
  from={{ opacity: 0 }}
  to={{ opacity: 1 }}>
  {(props:any) => (
hello
)}
</Spring>

Would you make a PR for a "Types" page in the docs? Like i said, i don't know TS much to be able to document it. Gonna close the issue here, but there's another that's been open for some time dealing with TS.

Would you make a PR

Never did it previously, I'll try :)


CSS Styling not working

I have just gone through the install (automated) and have no CSS styling, it is a vanilla install on WAMP64

Check for 404 errors on your bootstrap.min.css, bootstrap.min.js & jquery.min.js files. It appears they didn't include them. Just download the latest versions of each yourself, worked for me.

@pepsimatt Could you expand on that? I'm having the same issue.

@n0tj View your source & click all of these links: bootstrap.min.css & bootstrap.min.js & jquery.min.js
You'll see they all 404.  You need to download them yourself (google them). Then put them in the corresponding path/folder (which also needs to be created).

@n0tj You should run composer install at the root of the install directory from a command line, that should pull in all necessary dependencies.


feat(mat-datepicker-typography): allow to customize font-size in the datepicker

Feature Description
Hello !
The datepicker-theme currently uses a default body font-size of 13px (see _datepicker-theme here)
Which makes this not personalizable, as it doesn't come any of the defined variables from the typography config $config-or-theme passed as an argument to mat-datepicker-typography.
The feature request is to allow customization of the mat-calendar-body font size by using typography config params.
Maybe there's a reason why it's like that currently, but I'm not aware of it so I created a feature request.
Thank you !
Use Case
I'm customizing the font-family of the datepicker and other material components to match my design system, so I'd like to customize the font-size of the text in the datepicker to make it uniform with my other font-sizes.

Just a note: I'm aware this can be customized with
$mat-calendar-body-font-size: 14px;
@include mat-datepicker-typography($custom-typography);

but is there a reason to not make this depend on the config?


Save the model in the saved_model format.

          Save the model in the `saved_model` format.

This can be done by doing model.save("model_name").
Tensorflow will save the model in the saved_model format if you don't put .h5 in "model_name".
Originally posted by @yochananscharf in https://github.com/serizba/cppflow/issues/219#issuecomment-1290196967
Sorry, I am having a similar problem.
When I try to save this dummy model:
import tensorflow as tf

input = tf.keras.Input(shape=(5,))

output = tf.keras.layers.Dense(5, activation=tf.nn.relu)(input)
output = tf.keras.layers.Dense(1, activation=tf.nn.sigmoid)(output)
model = tf.keras.Model(inputs=input, outputs=output)

model.compile()

model.save('model')

I get ths error:
ValueError: Invalid filepath extension for saving. Please add either a `.keras` extension for the native Keras format (recommended) or a `.h5` extension. Use `model.export(filepath)` if you want to export a SavedModel for use with TFLite/TFServing/etc. Received: filepath=model.

If  I actually save it with a .h5 or a .keras extension at the end I get an error at runtime in the cpp script that is like:
2024-11-02 17:35:43.198951: I tensorflow/cc/saved_model/reader.cc:83] Reading SavedModel from: complex_model.keras
2024-11-02 17:35:43.198995: I tensorflow/cc/saved_model/loader.cc:466] SavedModel load for tags { serve }; Status: fail: NOT_FOUND: Could not find SavedModel .pb or .pbtxt at supplied export directory path: complex_model.keras. Check that the directory exists and that you have the right permissions for accessing it.. Took 49 microseconds.
terminate called after throwing an instance of 'std::runtime_error'
  what():  Could not find SavedModel .pb or .pbtxt at supplied export directory path: complex_model.keras. Check that the directory exists and that you have the right permissions for accessing it.
Aborted (core dumped)

OK, solved it by using
model .export('model')

in python and passing the model path via argv[] as an argument to main in cpp program.


Added corner positions, template engine support, size option and title bar option

I should'v made these independent pulls, but didn't get the chance. Let me know if I should. Also if merged, we gotta put back a few of the things in the README file. They weren't valid for the individual fork.
--Cheers

Great work :) :+1:


(bsc#1145599) Remove sysctl.conf top precedence

Why is this PR needed?
By default, sysctl.conf has top precedence over anything else that
can be configured on /etc/sysctl.d. In order to not let default
configurations override our own, when bootstrapping or joining a node,
move /etc/sysctl.conf contents to a /etc/sysctl.d/00-defaults
file, so we can override them if needed.
Thank you @lcavajani.

I like it but given this is not a ship stopper for RC1, let's merge it after RC1.

hpc20s14-kvm140-worker01:~ # sysctl --system
* Applying /boot/sysctl.conf-4.12.14-197.15-default ...
...
* Applying /etc/sysctl.d/00-defaults.conf ...
...
* Applying /usr/lib/sysctl.d/50-coredump.conf ...
...
* Applying /usr/lib/sysctl.d/50-default.conf ...
...
* Applying /usr/lib/sysctl.d/50-kubeadm.conf ...
...
* Applying /etc/sysctl.d/90-skuba-net-bridge-bridge-nf-call-iptables.conf ...
...
* Applying /etc/sysctl.d/90-skuba-net-ipv4-ip-forward.conf ...
...
* Applying /usr/lib/sysctl.d/99-sysctl.conf ...
* Applying /etc/sysctl.conf ...

Closed, please check https://bugzilla.suse.com/show_bug.cgi?id=1145599#c2 :clap:


Information required: how to setup plugin using packer

Hello, and thank you for your contribution. I have a question (comes from the issue I've faced). How to setup/configure the plugin using packer properly? My issue is that I couldn't specify plugin options, such as, vim.g.solarized_italics, vim.g.solarized_termtrans and so on. Even default option for italic font doesn't work for me.
After nvim has loaded the values are set to the options correctly, but it's probably performed after the color scheme has loaded. With tradition color scheme plugins (not lua) I didn't see such an issue. May you @ishan9299 pls a bit elaborate in this regard?

I am not familiar with packer. I don't use it but after a quick glance at README you can try this. As far as Italics are considered make sure that the font you are using has a italic font variant.
use 'ishan9299/nvim-solarized-lua'
-- your settings here
vim.g.solarized_italics = 1
vim.g.solarized_diffmode = 'normal'
vim.cmd('colorscheme solarized')

Also you need to make sure that the options are set before setting the colorscheme.

of cause, that snippet straight from my setup, but it doesn't work for me

OK, It's a setup issue, here is minimal setup which works as expected:

gut everything (clear nvim)
install packer following instruction here https://github.com/wbthomason/packer.nvim
init.lua:

vim.o.termguicolors = true
vim.o.background = 'light'

return require('packer').startup(function(use)
  use 'wbthomason/packer.nvim'
  use { 'ishan9299/nvim-solarized-lua',
  config = function()
	vim.g.solarized_diffmode = 'normal'
	vim.g.solarized_italics = 1
	vim.cmd('colorscheme solarized')
  end}
end)

-- this this a comment

my apologies...


Added comparison operators >, <=, >= to SourceLocation

this one is self-explanatory ;)

Thank you here as well:)


test(JSX): handle null and undefined

upgrade expect-to-equal-jsx
cc @redox once this merged you can continue pagination tests I believe

:+1:


Training with multiple TPU cores is incorrect and slower

System Info
- `Accelerate` version: 0.10.0
- Platform: Linux-5.13.0-1023-gcp-x86_64-with-glibc2.29
- Python version: 3.8.10
- Numpy version: 1.22.4
- PyTorch version (GPU?): 1.11.0a0+gitbc2c6ed (False)
- `Accelerate` default config:
        - compute_environment: LOCAL_MACHINE
        - distributed_type: TPU
        - mixed_precision: no
        - use_cpu: False
        - num_processes: 8
        - machine_rank: 0
        - num_machines: 1
        - main_process_ip: None
        - main_process_port: None
        - main_training_function: main
        - deepspeed_config: {}
        - fsdp_config: {}

Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[ ] My own task or dataset (give details below)

Reproduction
First, train with 8 TPU cores (run the script twice and count the second one to exclude the time used to download the datasets)
$ pipenv run accelerate config
In which compute environment are you running? ([0] This machine, [1] AWS (Amazon SageMaker)): 0
Which type of machine are you using? ([0] No distributed training, [1] multi-CPU, [2] multi-GPU, [3] TPU): 3
What is the name of the function in your script that should be launched in all parallel scripts? [main]:
How many TPU cores should be used for distributed training? [1]:8

$ time pipenv run accelerate launch accelerate/examples/nlp_example.py
...a lot of irrelevant warnings...
epoch 0: {'accuracy': 0.3125, 'f1': 0.0}
epoch 1: {'accuracy': 0.671875, 'f1': 0.8004750593824228}
epoch 2: {'accuracy': 0.6796875, 'f1': 0.8079625292740047}

________________________________________________________
Executed in  157.17 secs   fish           external
   usr time  474.51 secs  592.00 micros  474.51 secs
   sys time   99.76 secs    0.00 micros   99.76 secs

Next, train with 1 TPU core
$ pipenv run accelerate config
In which compute environment are you running? ([0] This machine, [1] AWS (Amazon SageMaker)): 0
Which type of machine are you using? ([0] No distributed training, [1] multi-CPU, [2] multi-GPU, [3] TPU): 3
What is the name of the function in your script that should be launched in all parallel scripts? [main]:
How many TPU cores should be used for distributed training? [1]:1

$ time pipenv run accelerate launch accelerate/examples/nlp_example.py
...a lot of irrelevant warnings...
epoch 0: {'accuracy': 0.6838235294117647, 'f1': 0.8122270742358079}
epoch 1: {'accuracy': 0.7205882352941176, 'f1': 0.8256880733944955}
epoch 2: {'accuracy': 0.7156862745098039, 'f1': 0.8215384615384616}

________________________________________________________
Executed in  150.81 secs   fish           external
   usr time  352.98 secs  419.00 micros  352.98 secs
   sys time   34.38 secs  210.00 micros   34.38 secs

Expected behavior
+ The `accuracy` and `f1` should be very close, but they are way off, and things are particularly weird in epoch 0 when we use 8 cores.
+ Using 8 TPU cores should be much faster, but it's slower (157.17s vs 150.81s).

This is not a bug, you are multiplying the batch size by 8 when training on TPU, so it's logical to get different results. You probably need to adapt the other hyperparameters a bit to get the same results.

@nalzok as Sylvain recommended, to be able to compare these properly we need to multiply the bs by 8. Here's the results after I've done so, which shows they're quite similar.
Re; speed, my best guess is it it might be due to communicating on all 8 cores + rendezvous etc. We also do not train very long, and the speedup should be faster when training for longer periods of time I believe.
From main:

On Accelerate 0.10.0 (which I'd consider close enough):

Interesting. I just tried reproducing the bug with a fresh install of accelerate, and I am no longer getting the weird epoch 0: {'accuracy': 0.3125, 'f1': 0.0}. I guess that means the bug has been fixed, or maybe it was only a little glitch on my local system.
I want to keep the issue open for a little longer though. Could you provide a simple example where using 8 TPU cores is significantly faster than using 1 core? I understand there is synchronization overhead, so I would accept even a 2x speed up with 8x more hardware resources, but using more hardware really shouldn't make the computation slower.

Thanks for your time!
To clarify, I am on a TPU v3-8 machine on GCP (obtained through TRC), not Colab. Additionally, the architecture is a TPU VM instead of a TPU node, so there are no networking roundtrips (i.e. $XRT_TPU_CONFIG is localservice;0;localhost:51011).

@nalzok I can stem the issue to the fact that the batch size on the eval vs train dataloaders are different, causing memory reallocation to occur. Can you try making the train and eval bs to be the same? (still working on getting myself setup).
But doing this in colab I got the following times:

8 cores first time: 152s
8 cores second run: 74.74s
1 core w/ 8x batch size to keep equal: 125s

@nalzok the bug is indeed with the NLP example script, I'll put in a fix tommorow. What I did here was took the NLP Example notebook (found here and I could get the right training results on 8 cores


Consider getting inspiration from ZKVM

This is great work! Do consider taking inspiration from ZkVM, since it implements a nice Bitcoin Script-like language (w/ bulletproofs as the proof system). You might get some nice ideas about the lang design from there https://github.com/stellar/slingshot/tree/main/zkvm

Thank you! That's a very cool project - will definitely go there for inspiration from time to time.

Thank you! That's a very cool project - will definitely go there for inspiration from time to time.

You are also doing a great project.  I have  a  question.  The sentence "A way to specify secret inputs which can change between program executions is not yet available, but will be provided in the future." , do it means the project doesn't support  the secret inputs at present, so it is not zero-knowledge?

Thank you! You could provide secret inputs using a PUSH operation - but these inputs then become a part of the program - so, that's very limiting, and is definitely not the intent of how it should work.
In the future, you'll be able to provide a list of secret inputs, and there will be another operation (something like READ or maybe a different name). Every time READ is executed, it will take a value from the input list and push it onto the stack.

Thank you very much for your reply. I really expect it. I wonder is it a general-purpose VM for arbitrary zero-knowledge implementation? Then many privacy-related problems on the blockchain can be solved by it. I feel it is will be very powerful

@Federico2014 I've just released a new version of the VM. It now has full support for unlimited number of secret inputs (as well as many other nice things) :)


fix(use-shopify): better define Variables type

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Open the PR and close the Issue

As per we discussed at the BSSw meeting today.

People should not submit a PR out of thin air. But if they do, then it should be treated like an issue starting in the backlog, moving to "Topic Review" and then "Item Review".

People should not submit a PR out of thin air. But if they do, then it should be treated like an issue starting in the backlog, moving to "Topic Review" and then "Item Review".

I agree.

@pagrubel said:

This step doesn't take care of the case where a PR is sent without going through the other phases, or its not clear to me anyway.

I added a note on how to handle suggested contributions submitted as a PR instead of an Issue.  Can you please take a look and review & approve the PR if you like.

@markcmiller86, can you merge in the updated 'master' branch and fix merge conflicts and push back to branch?

Ok, this just got merged as #406


PLMPGM-620 [SEC-APP-REQ-2] | CodeQL action for Static application security testing (SAST)

This change addresses the SEC-APP-REQ-2 SAST requirement as per ESSv9 assessment and recommendations for ROS

Codecov Report
Base: 72.45% // Head: 72.45% // No change to project coverage :thumbsup:

Coverage data is based on head (c0772cf) compared to base (3ccdd87).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #289   +/-   ##
=======================================
  Coverage   72.45%   72.45%
=======================================
  Files          26       26
  Lines        1238     1238
=======================================
  Hits          897      897
  Misses        341      341

Flag
Coverage Δ

unittests
72.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thanks @saltgen for PR, merging this now!


This issue

keops2.2.3/Linux_yhq-acloud_5.4.0-150-generic_p3.9.19/nvrtc_jit.so: cannot open shared object file: No such file or directory

hello, boy!

hello, how to solve this issue: keops2.2.3/Linux_yhq-acloud_5.4.0-150-generic_p3.9.19/nvrtc_jit.so: cannot open shared object file: No such file or directory

Hi, this is not related to our code. Apparently there is something wrong with your installation of pykeops. I suggest trying to remove the pykeops installation and reinstalling it.


Unexpected behavior of pro_rad1 for x < 1.0

The docstring for scipy.special.pro_rad1 says "Computes the prolate sheroidal radial function of the first kind and its derivative (with respect to x) for mode parameters m>=0 and n>=m, spheroidal parameter c and |x| < 1.0." However, when trying to compute the function with m = n = 0 and c = 1 on the interval (-1.0, 1.0), I get an array full of nan values.
Looking at the wrapper code in https://github.com/scipy/scipy/blob/d1203c280a8661536d64f17e6a90d7ef000302d5/scipy/special/specfun_wrappers.c#L953, is it possible that the comparison is wrong? That is, it returns nan when (x <= 1.0), when it should be testing for abs(x) > 1.
In [5]: scipy.special.pro_rad1(0, 0, 10, 200)
Out[5]: (0.00046907225742714526, -0.0017336833438237117)

In [6]: scipy.special.pro_rad1(0, 0, 1, 0.9)
Out[6]: (nan, nan)

The documentation is probably wrong, the fortran code specifies x > 1.

From what I know about this class of function, it would make more sense for it to be defined on (-1, 1) though

For example, http://reference.wolfram.com/language/ref/SpheroidalS1.html

Ah, never mind, that may not actually show it evaluated on that interval after all

So, I did some digging into this: I built a version of SciPy locally with those checks on x removed and checked it against Mathematica on the range of interest. It looks like there's no constraint built into the underlying algorithm that keeps it from producing accurate values on the interval that's currently masked out (for the arguments I used, anyway).

Interestingly, the spiky numerical artifacts look like they're coming from the Mathematica side; the SciPy values look smooth.

Let me echo here that as a user of this class of function, it is definitely the case that the value is well defined for x<1. For our use cases in computational optics we have working code in Mathematica and are trying to replicate it in Python but cannot because of this bug.

@josePhoenix it would be great if you could submit your code changes together with an added unit test and change to the docstring as a PR.

@rgommers Great, will do. I got our library to borrow us the reference for the special function code (Computation of Special Functions by Chang and Jin) and want to check if they discuss any limitations that we should know about before amending the docstring. I'll use their tabulated values for a test case as well, unless that's not considered a good way to write test cases for functions like this.

@josePhoenix excellent. Taking known values from literature is a good way to get a test case.

Curiously, the authors didn't see a need to evaluate the function for x < 1.005!
However: they evaluate and plot the prolate angular wave functions for 0 < eta < 1, and there's a "joining factor" relating the prolate angular wave functions to the prolate radial wave functions that is a function of the m and n indices and the c parameter (section 15.3.3). Since it appears to me (without going through all the gnarly math) that the joining factor is finite and nonzero, and clearly the prolate angular wave function is well defined for small eta from their plots, the lack of values near zero in the plots and tables appears to be a choice of the authors'.
(One of my colleagues tells me the fashion has been lately to use these special functions in wavelet transforms where the x < 1 region is not useful.)
I'll open a pull request with my changes shortly.

Ah, I see that for m >= 1, the code indeed refuses to produce values for |x| < 1.0. This makes sense with the definition in eqn 15.3.5, which has a (1 - 1/x^2)^(m/2) term that would tend to negative infinity for |x| < 1.0.
I'll make the C code check for |x| < 1.0 only in the case where m != 0.

Any update on this, I couldn't find a PR?


[Create Event] Alphabetic characters in house numbers are not localised after publishing event

Environment: macOS Monterey 12.6, Safari 16.0.
Reproducible: sometimes.
Build found: 15/09/2022
Steps to reproduce

Go to https://www.testgreencity.ga/
Log in
Choose English language
Click on the "Events" tab
Click "Create" button
Choose event duration in the "Duration" dropdown (e.g. 1 day)
Tick the "Place" checkbox
Enter address with alphabetic character after house number (e.g. Ivana Mazepy St, 6b, Kyiv, Ukraine)
Fill all the other fields with valid data
Click on the "Publish" button
Click on the "More" button of the event you just created once the event details page is opened

Actual result
Alphabetic character in house number is not localised  (e.g. Ivana Mazepy St, 6Б, Kyiv, Ukraine).
When creating event:

When event is published:

Expected result
Alphabetic character in house number is localised  (e.g. Ivana Mazepy St, 6b, Kyiv, Ukraine).
User story and test case links
User story https://github.com/ita-social-projects/GreenCity/issues/3193
Labels to be added
"Bug", Pri: Low, Sev: Minor, L10n, Events

That's not a backend bug, we are using google Translate API on the front end for this translation. So it's impossible to fix this bug as we get already translated data from that API.


Speech recognition fails on Linux with SPXERR_AUDIO_SYS_LIBRARY_NOT_FOUND

Describe the bug
I have followed your examples closely and can successfully run speech to text (no translation, all in en-GB) running locally on my Windows dev machine (it's a great result by the way). When I deploy to Azure as a linux container, I get an exception thrown (see below) when I try to create a new SpeechRecogniser.
To Reproduce
Deploy an ASP.NET app to Azure Container Services using the mcr.microsoft.com/dotnet/aspnet:7.0 linux container.
Expected behaviour
No exception!
Version of the Cognitive Services Speech SDK
1.25.0
Platform, Operating System, and Programming Language

OS: <IP_ADDRESS>-1.cm1
Hardware - x64 I think
Programming language: C# / ASP.NET 7.0.2
Browser: Edge

Additional context
System.ApplicationException: Exception with an error code: 0x38 (SPXERR_AUDIO_SYS_LIBRARY_NOT_FOUND)
   at Microsoft.CognitiveServices.Speech.Internal.SpxExceptionThrower.ThrowIfFail(IntPtr hr)
   at Microsoft.CognitiveServices.Speech.Recognizer.FromConfig(GetRecognizerFromConfigDelegate fromConfig, SpeechConfig speechConfig)
   at Microsoft.CognitiveServices.Speech.SpeechRecognizer..ctor(SpeechConfig speechConfig)

I am unsure how to use your logging because I don't have good access to the deployed container file system.

Hi there! Thanks for asking about this.
Typically this is due to a dependency of the audio sys extension. Make sure you have installed on your container the libasound2 so it can access the microphone.
I've used this in my Dockerfile RUN apt-get update && apt-get install -y --no-install-recommends libasound2
Could you try that and see if it works?

@simonziegler Was the information helpful, do you need more support? Please update, otherwise we'll close this issue in a few days.

Closed as presumed resolved, please open a new issue if more support is needed.


[Question] management bond, vlans and Intel XL710

I have tried to use sr-iov with Intel XL710 for weeks now and I finally found what is the problem.
/oem/90_custom.yaml have lines like this
bridge vlan add vid 2-4094 dev mgmt-bo
This fills vlan filter tables in NIC (and gives a lot of errors while booting harvester as well). This also prevents using sr-iov (at least with vlans) as vlan filtering stops functioning.
I manually adjusted vlan interval to shorter one that fits hardware filter tables and after that error messages disappeared and sr-iov started working. Why is this interval defined and what are consequences if it is changed?

I have Qlogic FastLinQ 41000 QL41134HLRJ-CK 4x 10Gbe.
And wonder my SR-IOV Network Devices list is empty.
Can it be the same reason?
How did you manually adjusted it?

I changed all
bridge vlan add vid 2-4094 dev
to
bridge vlan add vid 2-20 dev
To see that errors went away and sr-iov started working.
I would assume that your problem is different...

@tahvane1
bridge vlan add vid 2-4094 dev mgmt-bo
The above represents vlans that are associated with mgmt interface.
/oem/90_custom.yaml defines the above so that by default mgmt interface will be part of all 2 to 4094 vlans.
This is required for mgmt interface to accept any tagged traffic with vlan id from 2 to 4094 received on it.
Without the above configuration or missing some vlan in the above configuration, mgmt interface will drop traffic for that particular tagged vlans.
Use case: creating vlan vm networks on top of default mgmt cluster.In this case various vlans are carried over mgmt-bo interface.
Can you give more details on the error you saw and also what was not working with sr-iov and its configuration ?


Added the find-ppr_ns.py script and updated the readme

Created find-ppr_ns.py as a new file just in case!

Thanks for this, excited to check it out! I'm on vacation and expect to get to it this weekend. Just wanted to let you know, thanks again!


[X] I have updated to the latest version of the packages.
[X] I have searched for both existing issues and closed issues and found none that matched my issue.

RetinaFace's Version
0.0.17
Python Version
3.12.3
Operating System
mac os
Dependencies
keras==3.3.3
retina-face==0.0.17
tensorboard==2.16.2
tensorboard-data-server==0.7.2
tensorflow==2.16.1
tf_keras==2.16.0

I'd need to find the correct orientation of the fake identity card I've posted, I'm trying to use the confidence index but for some reason it is higher when the image is rotated.
Ideally it should award the rotated image
Reproducible example

def find_faces(image=None):

  images = {}
  rotate_angles = [0, 90, 180, 270]

  img = cv2.imread(image)
  img_base = img.copy()

  for angle in rotate_angles:

      logging.debug(f"Computing object detections... {image}@{angle}")
      img = img_base.copy()

      img = Image.fromarray(img)
      img = np.array(img.rotate(angle, expand=True))

      plt.imshow(img)
      plt.show()

      try:
          detections = RetinaFace.detect_faces(img)
      except Exception as exc:
          logging.critical(exc)
          continue

      if not isinstance(detections, dict):
          continue

      # loop over the detections
      for i, detection in detections.items():

          # logging.debug(detection)
          im = Image.open(image)
          im = im.rotate(angle, expand=True)
          confidence = detection.get('score', 0)

          # filter out weak detections by ensuring the `confidence` is greater than the minimum confidence
          if confidence > args.confidence:

              (startX, startY, endX, endY) = detection.get('facial_area')
              startX -= args.padding
              startY -= args.padding
              endX += args.padding
              endY += args.padding

              try:
                  text = confidence*100
                  logging.debug(f"Confidence of: {text} at {angle}")
                  im1 = im.crop((startX, startY, endX, endY))
                  im1 = im1.convert('RGB')

                  buffered = BytesIO()
                  im1.save(buffered, format="JPEG")

                  plt.imshow(im1)
                  plt.show()

                  img_str = base64.b64encode(buffered.getvalue()).decode()
                  images.update({text: [img_str, angle]})

              except Exception as exc:
                  logging.debug(exc)
                  pass

Relevant Log Output
No response
Expected Result
confidence index should be higher when the image is rotated properly
What happened instead?
the 90 degrees image wins
Additional Info
No response

i would use nothing, retinaface is not for detecting face identities.


Potential null dereference at aead.c

In line 45, there is a possibility of dereferencing the ctx pointer if the OPENSSL_malloc function returns NULL. Therefore, before calling the EVP_AEAD_CTX_init function, it is necessary to ensure that the memory allocation for ctx was successful(for example: example 1, example 2)
Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE.
Author: Alexey Galkin.

A similar situation occurs in lines 355 and 440 at tls13_enc.cc


Do not skip character to right of type annotation when navigating with vscode vim extension.

When navigating the cursor through the type annotations with the vscode vim extension, it skips the character directly to the right of the type annotations:
https://user-images.githubusercontent.com/25965706/162586393-7f3a3d5f-5058-4349-908f-11397e617225.mov
Is this something that can be dealt with in rust-analyzer, or is it a problem for the vim extension?
rust-analyzer version: 0.2.1002
rustc version: rustc 1.60.0 (7737e0b5c 2022-04-04)

Does it still happen if you disable RA?

I think this is how the inlay hints work. Even without the Vim extension the cursor moves ina weird way around them, depending on the direction you're coming from.
You could also try with another implementation of the hints (the TS extension has them, disabled by default IIRC).

This isn't something we control but what VSCode does in regards to inlay hints.


Solving a tiny Accordion issue when using it on a Carrd website

Hello!
Please tread softly! I've installed the code for Accordion feature on a Carrd website I've built. It's for a puzzle project, so I want ot be able to reveal hints for the puzzles using Accordion.
How do I have it keep the top Hint closed by default? I've tinkered with true/false to no avail.
Here is the specific page link: https://atraso.carrd.co/#accordion
All help would be appreciated!
(I'm assuming that I can add the formatting of text/color afterwards or in the CSS).

I should also add, the arrow controls don't appear to collapse/expand. There is always one box open.

Open/close is toggled by a class name—replace the classes of accordion-collapse collapse show with collapsed to hide any accordion item's content.

Tried several adjustements, to no avail.
https://atraso.carrd.co/#accordion


Support and make use of function calling and other OpenAI updates on 2023-06-13

Feature request
OpenAI released several major updates today (2023-06-13) that likely have major implications for what is possible. At the very least, it will make things more reliable.
Here's a shortlist from the blog post:

Dramatically improved function calling support + JSON consistency
gpt-3.5-turbo with a 16K context window (🤯)
Token cost changes for completions and embeddings
Upcoming deprecation for March-versioned models

Motivation
The release of OpenAI's blog post found here:
https://openai.com/blog/function-calling-and-other-api-updates
I'm adding this issue mostly to flag and track this OpenAI release and kick off a forum for discussion.
Your contribution
Can potentially add PRs but haven't contributed here previously.

Looks like they added a new functions property to their API
Example from post:
curl https://api.openai.com/v1/chat/completions -u :$OPENAI_API_KEY -H 'Content-Type: application/json' -d '{
  "model": "gpt-3.5-turbo-0613",
  "messages": [
    {"role": "user", "content": "What is the weather like in Boston?"}
  ],
  "functions": [
    {
      "name": "get_current_weather",
      "description": "Get the current weather in a given location",
      "parameters": {
        "type": "object",
        "properties": {
          "location": {
            "type": "string",
            "description": "The city and state, e.g. San Francisco, CA"
          },
          "unit": {
            "type": "string",
            "enum": ["celsius", "fahrenheit"]
          }
        },
        "required": ["location"]
      }
    }
  ]
}'

Response
{
  "id": "chatcmpl-123",
  ...
  "choices": [{
    "index": 0,
    "message": {
      "role": "assistant",
      "content": null,
      "function_call": {
        "name": "get_current_weather",
        "arguments": "{ \"location\": \"Boston, MA\"}"
      }
    },
    "finish_reason": "function_call"
  }]
}

This looks like it could be game changing for agents!

I haven't contributed before but am happy to work on this if helpful!
Should this be a new agent type?
From the api docs it seems an agent should repeatedly call the openAI API until no more functions are returned.
Is there somewhere I should look for proper contribution etiquette?

Here's the contribution guidelines: https://github.com/hwchase17/langchain/blob/11ab0be11aff9128c12178b5ebf62071985fb823/.github/CONTRIBUTING.md
I'm also interested in contributing to this! :smiley:
I think this could be a new openAI agent, and there would have to be some way to add functions. I also think being able to connect functions to tools would help remove the need for the extra prompt engineering at the beginning of the agent.

Looks like @hwchase17 is already diving right in 😎
#6113

I did not see the funcion calling example like in openai site for custom function as below, how to integrate with it?
import openai
import json

# Example dummy function hard coded to return the same weather
# In production, this could be your backend API or an external API
def get_current_weather(location, unit="fahrenheit"):
    """Get the current weather in a given location"""
    weather_info = {
        "location": location,
        "temperature": "72",
        "unit": unit,
        "forecast": ["sunny", "windy"],
    }
    return json.dumps(weather_info)

# Step 1, send model the user query and what functions it has access to
def run_conversation():
    response = openai.ChatCompletion.create(
        model="gpt-3.5-turbo-0613",
        messages=[{"role": "user", "content": "What's the weather like in Boston?"}],
        functions=[
            {
                "name": "get_current_weather",
                "description": "Get the current weather in a given location",
                "parameters": {
                    "type": "object",
                    "properties": {
                        "location": {
                            "type": "string",
                            "description": "The city and state, e.g. San Francisco, CA",
                        },
                        "unit": {"type": "string", "enum": ["celsius", "fahrenheit"]},
                    },
                    "required": ["location"],
                },
            }
        ],
        function_call="auto",
    )

    message = response["choices"][0]["message"]

    # Step 2, check if the model wants to call a function
    if message.get("function_call"):
        function_name = message["function_call"]["name"]

        # Step 3, call the function
        # Note: the JSON response from the model may not be valid JSON
        function_response = get_current_weather(
            location=message.get("location"),
            unit=message.get("unit"),
        )

        # Step 4, send model the info on the function call and function response
        second_response = openai.ChatCompletion.create(
            model="gpt-3.5-turbo-0613",
            messages=[
                {"role": "user", "content": "What is the weather like in boston?"},
                message,
                {
                    "role": "function",
                    "name": function_name,
                    "content": function_response,
                },
            ],
        )
        return second_response

print(run_conversation())

Can we also add APIs to use the new function call feature directly without an agent?

See #6178, it explains how to use functions directly on an LLM. However, it looks like OpenAI just finetuned their models to spit out some JSON, and it doesn't work amazingly yet.
https://news.ycombinator.com/item?id=36313348


SELECT COALESCE() results are always assumed non-null

Version
1.13.0
What happened?
Possibly related to:

#937
#1096

SELECT COALESCE(x, y) results are always assumed non-null.
If all fields are nullable, result typing should not be string but NullString.
Database schema
CREATE TABLE examples(
  id BIGSERIAL PRIMARY KEY,
  nullable text,
  nonnull text NOT NULL
);

SQL queries
-- name: GetExample :one
SELECT
  nullable,
  nonnull,
  COALESCE(nonnull) AS coalesce_nonnull,
  COALESCE(nullable) AS coalesce_nullable,
  COALESCE(nonnull, nonnull) AS coalesce_nonnull_nonnull,
  COALESCE(nonnull, nullable) AS coalesce_nonnull_nullable,
  COALESCE(nullable, nonnull) AS coalesce_nullable_nonnull,
  COALESCE(nullable, nullable) AS coalesce_nullable_nullable
FROM examples WHERE id = $1 LIMIT 1;

Configuration
{
  "version": "1",
  "packages": [
    {
      "path": "db",
      "engine": "postgresql",
      "schema": "query.sql",
      "queries": "query.sql"
    }
  ]
}

Outputs
Expected:
type GetExampleRow struct {
	Nullable                 sql.NullString
	Nonnull                  string
	CoalesceNonnull          string
	CoalesceNullable         sql.NullString
	CoalesceNonnullNonnull   string
	CoalesceNonnullNullable  string
	CoalesceNullableNonnull  string
	CoalesceNullableNullable sql.NullString
}

Actual:
type GetExampleRow struct {
	Nullable                 sql.NullString
	Nonnull                  string
	CoalesceNonnull          string
	CoalesceNullable         string
	CoalesceNonnullNonnull   string
	CoalesceNonnullNullable  string
	CoalesceNullableNonnull  string
	CoalesceNullableNullable string
}

Playground URL
https://play.sqlc.dev/p/c9bba8ca287f65b7ce5f282bec5da570b0bd7693223e1d61e8b6619f4ba92a42
What operating system are you using?
macOS
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

https://github.com/kyleconroy/sqlc/blob/582ba6e79b354683c363da5f7c352fce50fd3fc7/internal/compiler/output_columns.go#L146-L171

@kyleconroy This fix is essential for my company's products, which make heavy use of COALESCE. And they don't willing to use forked packages. I would appreciate if you could review the PR if you have time.


Proposal: Make <|> right associative

Is there a practical reason for <|> being left associative? In general, it's a control structure, where right-associativity is desirable (eg, what if if/then/else was left associative? It just doesn't make sense). For example, in all the canonical instance for parsers or Maybe, or Lists, left associativity leads to terrible evaluation characteristics and almost always requires more work than right-associativity. I always have to define a new local alias when writing parsers because it's a significant improvement.

This sounds sensible to me. As far as I’m aware, it doesn’t matter as far as correctness goes whether it is a right or left associating operator. How do you see this change affecting users of those existing instances?

I'm curious about the original reasoning for it being left associative too, shame nobody has replied to your tweet about it.

How do you see this change affecting users of those existing instances?

It should be non-breaking for law-abiding implementations. There may be potential syntactic effects though? I don't remember the exact parser rules for precedence when faced with competing associativity at the same precedence level.

There may be potential syntactic effects though? I don't remember the exact parser rules for precedence when faced with competing associativity at the same precedence level.

Yeah, it comes out as a MixedAssociativityError.