Unable to Install sainsc on macOS using Mamba

Description:
I tried to create an environment with the sainsc package using mamba, but I received an error stating that the package does not exist, despite it being listed in Bioconda.
Steps to Reproduce:
I ran the following command to create a new environment with sainsc:
mamba create --name myenvname sainsc
The command resulted in the following output:

Looking for: ['sainsc']

conda-forge/osx-64                                          Using cache
conda-forge/noarch                                          Using cache
bioconda/osx-64                                             Using cache
bioconda/noarch                                             Using cache
pkgs/r/noarch                                                 No change
pkgs/r/osx-64                                                 No change
pkgs/main/osx-64                                              No change
pkgs/main/noarch                                              No change
Could not solve for environment specs
The following package could not be installed
└─ sainsc does not exist (perhaps a typo or a missing channel).

System Information:
sysctl -n machdep.cpu.brand_string Operating System: macOS (Apple M3 Pro)
Package Manager: Mamba
mamba 1.5.0
conda 22.11.1

Conda Channels Used: bioconda, conda-forge, defaults
Python Version: 3.9 (also tested with 3.10)
Additional Context:
The Bioconda recipe shows that sainsc should be available. However, it appears the package cannot be found for macOS, even after ensuring that Bioconda is correctly prioritized.
Could you please check if the package is available for macOS, or provide guidance on what might be missing?

Hi, first of all thanks for your interest in this package.
You will need at least python 3.10 to run sainsc.
Regarding macOS, this depends a bit on the actual hardware you are running. On bioconda sainsc is only available for ARM architecture of macOS, that means the newer Apple silicon (i.e. M1 processors and after if I am not mistaken) not the older Intel processors.
If you are running macOS with an Intel chip (which is likely the case if you couldn't install using conda) there are 2 options:

install via pip; on PyPI a compiled version of the package should be available for macOS with Intel Hardware (x86_64)
compile from source; for that you could follow the install guide in the documentation. (However I would recommend the first option)


Segmentation Fault

Dear Stephan ,
I was getting segmentation fault when I tried to run your BILBOWA code (from github) on OpenSuse.
The segmentation fault had happened when the program tried to join threads.
I checked and it seems the problem is caused due to this part of your code
for (a = 0; a < (NUM_LANG - 1) * num_threads; a++) {
if (debug_mode > 2) printf("Spawning parallel thread %ld\n", a);
pthread_create(&pt[a], NULL, BilbowaThread, (void *)a);
}
for (a = 0; a < (NUM_LANG + 1) * num_threads; a++) pthread_join(pt[a], NULL);
I changed +1 to -1 and everything is working fine. I'm not sure if my solution is correct or not

I have been having the same issue and I changed the code like this:
for (a = 0; a < (NUM_LANG - 1) * num_threads; a++) {
if (debug_mode > 2) printf("Spawning parallel thread %ld\n", a);
pthread_create(&pt[a + (NUM_LANG * num_threads)], NULL, BilbowaThread, (void *)a);
}
This way it also works but I was wondering if you could confirm the adaptation so we can use the code in our research.
Thanks!

I tried above two solutions, they did not work now.

Maybe we set too many threads.Because actually num_threads*3 threads will be created in general cases. I set threads=40 at first and Segmentation Fault occured. Then I set 10 and it seems running fine.

Our machine has 64 cores. I first run the code with threads=40 and the same issue happened. After reading the code I set the threads=10, and threads=5, the same issue still occur.
@gouwsmeister here is the log with threads=5:
Starting training.
Spawning mono thread 0
Spawning mono thread 1
Spawning mono thread 2
Spawning mono thread 3
Spawning mono thread 4
Spawning mono thread 5
Spawning mono thread 6
Spawning mono thread 7
Spawning mono thread 8
Spawning mono thread 9
Spawning parallel thread 0
Spawning parallel thread 1
Spawning parallel thread 2
Spawning parallel thread 3
Spawning parallel thread 4
Segmentation fault

MAX_STRING setting is too small, the best solution is to enlarge this variable in line 22.


Main args

Codecov Report

Merging #71 (acaddd9) into master (7a153e9) will decrease coverage by 5.92%.
The diff coverage is 26.31%.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
- Coverage   98.64%   92.71%   -5.93%
==========================================
  Files          40       40
  Lines        2359     2335      -24
==========================================
- Hits         2327     2165     -162
- Misses         32      170     +138

Flag
Coverage Δ

integration
?

network
?

unit
92.71% <26.31%> (+0.81%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.


"Setters" not doing anything

I'm trying to work with this repository. Using Ubuntu on my laptop. I have all the lights right around. I'm able to log in with my username and password and see my devices, then I'm even sometimes able to "connect" to the network calling devices.devices[0].network.connect() (it claims it works occasionally). But then when I go to interact with the devices, nothing ever happens. Sometimes it runs through the script, sometimes it just hangs at one of the "set" parts. Anyone have any suggestions?
The brightness and temperature components of "devices" are just the class defaults (i.e. 0). Nothing is being called to update those.
import laurel

with open('../login.txt') as f:
    login_data = f.read()
username = login_data.split(',')[0]
password = login_data.split(', ')[1]

print('Logging in...')
devices = laurel.laurel(username, password)
print('Successfully logged in!')
devices = devices.devices

idx = 5
print('Name: {}\nMAC: {}\nType: {}\nBrightness: {}\nTemperature: {}\n'.format(
    devices[idx].name,
    devices[idx].mac,
    devices[idx].type,
    devices[idx].brightness,
    devices[idx].temperature))

print('Connecting...')
devices[idx].network.connect(idx_start = idx)

print('Setting brightness')
devices[idx].set_brightness(10) # THIS DOES NOTHING OR HANGS SOMETIMES

print('Setting power')
devices[idx].set_power(False) # THIS DOES NOTHING OR HANGS SOMETIMES

@williamkennyAK I tried your code (from a separate issue) as well, and it partially ran through but never did anything to the lights and then would eventually hang

@williamkennyAK I tried your code (from a separate issue) as well, and it partially ran through but never did anything to the lights and then would eventually hang

@williamkennyAK I tried your code (from a separate issue) as well, and it partially ran through but never did anything to the lights and then would eventually hang

Unfortunately, I have no lights to test out.  I only have the smart plug.  I added a bunch of printf statements to find where exactly the code was hanging for me.
What version of python are you using?

@williamkennyAK I tried your code (from a separate issue) as well, and it partially ran through but never did anything to the lights and then would eventually hang

Unfortunately, I have no lights to test out.  I only have the smart plug.  I added a bunch of printf statements to find where exactly the code was hanging for me.
What version of python are you using?

Hi,
There's a bug in bluepy that means it'll tend to wedge when commands are sent. I have a workaround in a local branch until upstream merge it - can you please try upgrading to python-dimond 0.3 (you'll probably want to upgrade to python-laurel 0.5 as well) and see if that works any better?


Allow creation of Pattern from Symbol

A little addition to allow the creation of patterns from symbols, which allows you to write
@items[i]

where i is a Symbol instead of having to mess with #to_s() at the call site

I really don’t like this idea, because a symbol semantically isn’t the same as a symbol; generating a pattern from a symbol does not sound right to me. I prefer the #to_s because it’s more explicit.

because a symbol semantically isn't the same as a symbol

🤔

Whoops! I meant:

… because a symbol semantically isn't the same as a string

… because a symbol semantically isn't the same as a string

I'm not sure I understand what you mean. What prompted me to open this PR is that somewhere in a (partial) layout I'm using information that comes from item identifiers or config.
And because of __nanoc_symbolize_keys_recursively, data that started their life as strings in YAML metadata end up being symbols down the road.

Ah yes, I forgot that a config file like
/foo/**/*.md:
  whitelisted: true

/people/**/*.md:
  type: person

… would lead to patterns that are symbols.

OH! You merged fast.
I didn't have the impression I was pushing that hard 😅
Thank you!


Fix issue with documentation failing to display generated images

Summary
This adds the necessary Javascript files used to generate the documentation images. Instead of using a custom plugin to accomplish this we are extending the default theme and appending these Javascript sources to <head>. Gitbook works automagically to inspect the _layouts directory and applies contents to the appropriate parent files. Note that this restores functionality present in the previous documentation set.
Fixes #1092.
Open question

This only adds back in the Javascript files but does not republish the static site; I believe this is done with gitbook build . and then publishing those static files

Nice. Note that we normally rebuild the user guide as part of our release process


ROM valid for identification of fakes?

Thanks for sharing all this information with the web. I came across this after having bought 5 DS18B20 on ebay Germany, which I couldn't get to work in 1-Wire, i.e. bus-powered, mode. It took me some hours of debugging before looking for fake chips.
Afterwards, I got 2 DS18B20+ and 2 DS18B20+PAR directly from Maxim. They work smoothly in bus-powered mode with several meters of bell wire between all of them. So, I presume they are "good" and original.
However, I think they do not match the ROM pattern you found out. Having no Arduino available currently, I cannot run your software, but here is the info that I got from my Raspberry:
pi@raspberrypi:~ $ cat /sys/bus/w1/devices/
28-00000d1efbf6/ 28-00000d1efed4/ 28-00000d2b5549/ 28-00000d2b7e32/ w1_bus_master1/
pi@raspberrypi:~ $ cat /sys/bus/w1/devices/28-00000d1efbf6/w1_slave
f4 00 4b 46 7f ff 0c 10 fa : crc=fa YES
f4 00 4b 46 7f ff 0c 10 fa t=15250
pi@raspberrypi:~ $ cat /sys/bus/w1/devices/28-00000d1efed4/w1_slave
f3 00 4b 46 7f ff 0d 10 ee : crc=ee YES
f3 00 4b 46 7f ff 0d 10 ee t=15187
pi@raspberrypi:~ $ cat /sys/bus/w1/devices/28-00000d2b5549/w1_slave
f6 00 4b 46 7f ff 0a 10 d6 : crc=d6 YES
f6 00 4b 46 7f ff 0a 10 d6 t=15375
pi@raspberrypi:~ $ cat /sys/bus/w1/devices/28-00000d2b7e32/w1_slave
f6 00 4b 46 7f ff 0a 10 d6 : crc=d6 YES
f6 00 4b 46 7f ff 0a 10 d6 t=15375

You can see the "ID" as well as the scratchpad content. Both does not match exactly your findings.
Date code is 2041 and 2037, respectively. Origin is "PH" for the DS18B20+ and "TW" for the DS18B20+PAR. And indeed, the DS18B20+PAR do not have the P mark in the indent on the back.

DS18B20+ might be slightly different. I guess this project investigated only DS18B20 originals, without the "plus". Thus, the + version might follow a different ROM pattern even it's shares the same datasheet.

@etas-github-sb, 1. thank you for sharing your observations on the "new" TW-origin chips.
2. Your dumps are actually consistent with the description of Family A1.

The scratchpad register content is compatible with Family A after a temperature conversion at around 15 °C. What you show is not the content at power-up. However, you see how the byte following ff (<byte 6>) depends on the value of the first byte (<byte 0>), which is a distinguishing behavior of Family A (the lower nibble of <byte 0> and <byte 6> add up to 0x10, e.g. in your first example: 0x4 + 0x0c = 0x10).
It is unfortunate that there are two conventions in the wild on how to write the 1-wire ROMs. What you write as 28-00000d1efbf6 I write as 28-FB-1E-0D-00-00-F6. I.e. I write the ROM as a sequence of bytes the way they are reported by the chip itself while your way is based on an interpretation of the ROM and written as <Family Code>-<48-bit Serial Number><CRC>. Your ROMs are consistent with Family A1.

@N-Storm, the "+" indicates that the sensors are RoHS, and the DS18B20 have been RoHS for ages, certainly for all C4 dies, i.e. as far back as 2009. In other words, the analysis of the state as of 2019 is actually about DS18B20+. Will edit for clarity, thanks!

Thanks for this clarification. I didn't realize that the ROM content was just mangled around by the w1 module of Raspian. Then at least your investigation is confirmed by newer samples. :) The PAR models seem to follow the same rule then.
This "issue" can be closed then.


class-signature rule incorrectly forces removal of primary no-argument constructor

Expected Behavior
As a contrived example, but trimmed down from a real example, consider the file Foo.kt:
class Foo() {
    constructor(name: String) : this() {
    }
}

This should pass lint checks with no warnings.
Observed Behavior
ktlint reports a warning:
Foo.kt:1:10: No parenthesis expected (standard:class-signature)
12:30:54.868 [main] WARN com.pinterest.ktlint.cli.internal.KtlintCommandLine -- Lint has found errors than can be autocorrected using 'ktlint --format'

Summary error count (descending) by rule:
  standard:class-signature: 1

And if --format is enabled automatically removes the primary constructor for Foo:
class Foo {

however that constructor is actually being used by the other constructor, causing the following compilation error:
tmp/Foo.kt:8:13: error: supertype initialization is impossible without primary constructor
class Foo {
            ^
tmp/Foo.kt:9:37: error: no value passed for parameter 'name'
    constructor(name: String) : this() {
                                    ^Target //tmp:FooLib failed to build

Your Environment

Version of ktlint used: 1.3.0 (as provided by bazel rules_kotlin)
No .editorconfig settings
Name and version (or code for custom task) of integration used (bazel 7.2.1 with rules_kotlin 1.9.6):
Operating System and version: Linux vm-shared 6.5.0-1016-gcp #16~22.04.1-Ubuntu SMP Sat Mar  9 00:58:37 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

This has already been fixed by #2717 in version 1.3.1.

Thanks!


Adds compatibility with PHP 7

FG\ASN1\Universal\Null renamed into FG\ASN1\Universal\NullObject
Tests configuration updated
Documentation updated

It also includes minor coding standard modifications
Fixes #34.
Please note that this commit breaks compatibility and requires to bump to a major release

Could you please restart the test using PHP 7 on travis?
This test passed for me ; it seems it is due to a timeout and not to a bug frm this PR

For BC an empty Null class could be defined, which would extend the renamed NullObject.
Also, perhaps it would make more sense to split this into 2 - a CS PR and a fix for the reserved keyword. Would simplify reviewing a bit and keep things nice & tidy :)

PR updated

Looks good to me :+1:
There's a couple of files under lib/X509 that still use the old Null object. Perhaps these should also use NullObject, but this can easily be done in another PR as well I guess.

@kgilden I have just updated my PR. I missed these files because no tests are performed.

Hey thx @Spomky and @kgilden for the PR and first review. I will have time today after work to do the merge (meaning this evening)

I decided not to bump a major version for this since you still left the old but now deprecated Null class lying there which I find a good solution for now.
Many thanks for the contribution :)


Build docs updates

Update build docs to include details about more make targets, and details on how to run fast and single STs, start up consul and etcd, installing pycalico library etc.

Might be good for you to rebase in light of the libnetwork split

OK, done for now. Can I take another look at this when you've made the markups

LGTM


Remove some ESL-isms

Why was this closed?

Changing parameter order without any explanation or usefulness other than breaking code.


fix: Complete the provider-ui eslint rules

Refers #910

Restore all major rules for Provider-UI
Get rids of half of the warning (total more than 200)
Half of the work still remaining on UI part which will be done in subsequent PR.

@kushthedude I have made some comments. Everything except them looks good :+1:

thank you, @aayushdutt ✔

@kushthedude I think the better way to resolve commits is from the reviewer. This way we will be having a better, unbroken, continuous discussion about the fix/resolution.

@kushthedude I think the better way to resolve change requests is from the reviewer. This way we will be having a better, unbroken, continuous discussion about the fix/resolution since GitHub doesn't allow to re open resolved changes.

You can comment on any change you find absurd or can't understand, I will mark unresolved for you as I have done on the above changes wherever you were not satisfied with the change.

@kushthedude That's great. But, I still think it is a better practice to allow the reviewer to decide whether the change is resolved or not. We don't want unresolved changes to remain marked as resolved right?

@leecalcote Everything looks nice to me now, we are pretty much good to go. You might want to see the changes at your end.

@leecalcote  The changes look nice to me! You might want to go through the changes at your end.

Good to go! Just think of how much fewer check failures there will be after this merge. 😄


Project not found: 'name$stage'

Mutations are failing from the front end with the message
{
  "errors": [
    {
      "message": "Project not found: 'proj-name$stage'",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "createLetter"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "result": {
            "errors": [
              {
                "message": "Project not found: 'proj-name$stage'",
                "code": 3016,
                "requestId": "local:ckbi751gq002p0760xzbpndmn"
              }
            ],
            "status": 200
          }
        }
      }
    }
  ],
  "data": null
}

I expected the mutation to succeed.
The prisma server is a Heroku migration made using the gui available through app.prisma.io.

Closing this issue. If you're like me and found this same error multiple places with no good help associated with it I can answer the question of "what did they do to fix it?!"
You have a typo. Trust me, you do. I didn't think I did but I must have.
Remember the url to your database is 'host.tld/project/stage' Go copy and paste it. I hope that fixes it for you, like it did for me.


Docs

Improve system documentation.

[x] README
[ ] Book

https://github.com/naomijub/wooridb/pull/54

README https://github.com/naomijub/wooridb/pull/56


My first revup foo

Topic: foo

Reviews in this chain:
└https://github.com/yuwei-will-xia/revup_test/pull/1 My first revup foo

#
head
base
diff
date
summary

0
8b616245
37f685bd
diff
Sep 18 11:14 AM
1 file changed, 1 insertion(+)


Any interest in shared KTX 2.0 parser?

Discussed this briefly with @bghgary recently, but I think the current state of (non-WASM) KTX 2.0 parsers for web is:

three.js has a custom plain JS parser, THREE.KTX2Loader. Parses KTX2 wrapper and decodes using MSC Transcoder.
babylon.js has a TypeScript port KTX2 Decoder. Parses KTX2 wrapper using combination of MSC Transcoder and lightweight AssemblyScript transcoders.
(new) I've started a TypeScript KTX2 parser + serializer, ktx-parse. It's a standalone repository with an npm package, so that I can use it in other projects like glTF-Transform. My intention (open to discuss) was to keep it focused on parsing the container, not transcoding, so that it could be used with any of the various Basis transcoders or other GPU texture formats.

three.js does not bring in production dependencies from NPM, so my ability to package that code for reuse is a bit limited. If you're interested though, I'd be glad to collaborate on a repo/package for the other two, and for future users. Currently the code I've written in read.ts is very similar to your own ktx2FileReader.ts, and outputs a nearly-identical container interface. I've added support for key/value data, otherwise I think they're functionally equivalent. I intend to include serialization as well (not functional yet), which will be tree-shakeable if you don't need it:
import { read, write } from 'ktx-parse';

// Load.
const data = await fetch('./input.ktx2').then(r => r.arrayBuffer());

// Parse.
const container = read(new Uint8Array(data));

// Serialize.
write(container); // → Uint8Array

Open to ideas on how to structure this, or let me know if this doesn't make sense. :)

As we are also not having dependencies, I ll definitely let @bghgary and @Popov72 think about this one, but I truly enjoyed the shared aspect and community focus of the proposal !!!

Yeah, we don't bring in npm dependencies either. Would it be possible to create a standalone js file that we distribute? For example, Draco has the js file directly commited in their repo and we just copy it. Another example is glTF-Validator where we use browersify to build a standalone js.

Currently the code I've written in read.ts is very similar to your own ktx2FileReader.ts

That's expected as we heavily based this implementation on your own implementation from 3js KTX2Loader.js (this is our first reference in the header comment of ktx2Decoder.ts) ;)!

Would it be possible to create a standalone js file that we distribute?

That's easy if it's just a parser+serializer, yes. If scope includes transcoders, ZSTD or ZLIB decompression, and Web Worker management, then those could add several extra JS+WASM files that need to be copied around in the right directory paths, and things get more complicated.

I don't think we should include web worker management. I think this should be handled by the consuming code.
I also don't think we should include the transcoders or ZSTD directly. Instead, we can use configuration options to point to them or add them via some kind of extensibility mechanism. It will be up to the consuming code to determine where to host the additional assets (wasm, etc.).

I've finished up the reading/writing functionality of ktx-parse now, and this quick transcoding test works:
const fs = require('fs');
const savePixels = require('save-pixels');
const ndarray = require('ndarray');
const {read} = require('ktx-parse');

const decoderWASM = fs.readFileSync('./node_modules/universal-texture-transcoders/build/uastc_rgba32_srgb.wasm');
const ktxData = fs.readFileSync('./test_uastc.ktx2');

(async () => {
	const texture = read(ktxData);

	const {byteLength} = texture.levels[0].levelData;

	// Uncompressed texture padded to multiple-of-4 height
	const yBlocks = (texture.pixelHeight + 3) >> 2;
	const uncompressedByteLength = texture.pixelWidth * yBlocks * 4 * 4;

	const texMemoryPages = (65535 + byteLength + uncompressedByteLength) >> 16;
	const memory = new WebAssembly.Memory({ initial: texMemoryPages + 1 });

	const decoder = (
		await WebAssembly.instantiate(decoderWASM, {env: {memory}})
	)['instance'].exports;

	const compressedTextureView = new Uint8Array(memory.buffer, 65536, byteLength);
	compressedTextureView.set(texture.levels[0].levelData);

	const decodedTextureView = new Uint8Array(memory.buffer, 65536 + byteLength, uncompressedByteLength);
	const status = decoder.decodeRGBA32(texture.pixelWidth, texture.pixelHeight);

	if (status !== 0) throw new Error('Decoding failed.');

	saveTofile('output.png', decodedTextureView, texture);
})();

///////////////////////////////////////////////////////////////////////////////

async function saveTofile(path, view, texture) {
	const pixels = ndarray(view, [texture.pixelWidth, texture.pixelHeight, 4])
		.transpose(1, 0)
	const image = await new Promise((resolve, reject) => {
		const chunks = [];
		savePixels(pixels, 'png')
			.on('data', (d) => chunks.push(d))
			.on('end', () => resolve(Buffer.concat(chunks)))
			.on('error', (e) => reject(e));
	});
	fs.writeFileSync(path, image);
}

I didn't include ZSTD decompression in the test, but it should be minor to add:
import { ZSTDecoder } from 'zstddec';
const decoder = new ZSTDDecoder();
await decoder.init();

// ...

if (texture.supercompressionType === 2) {
	data = decoder.decode( data, texture.levels[i].uncompressedByteLength );
}

The build output is<EMAIL_ADDRESS>and would benefit from tree-shaking if you don't need to write KTX2 files. Does this fit what you had in mind? I

Does this fit what you had in mind?

Thanks, it seems good from a quick look! @Popov72 What do you think?

That seems fine to me!
I'm wondering however if we should not also provide (afterwards) another package like ktx-transcode (or ktx-decode) that would use ktx-parse to decode files (what the 3js KTX2Loader and Babylon ktx2Decoder do), because people needing ktx2 decoding will end up writing basically the same thing. That's something we thought about on our side when creating ktx2Decoder and that's why we did a separate package from Babylon.js itself with no dependency, in case we would create a standalone repo later on.
One small thing: why not ktx2-parse instead of ktx-parse? Do you support both ktx and ktx2 file formats?

One small thing: why not ktx2-parse instead of ktx-parse? Do you support both ktx and ktx2 file formats?

I went back and forth on that. Support for reading KTX 1 and writing KTX 2 might be nice (and relatively easy?), but isn't a high priority for me at the moment. I also didn't want to rule out supporting future versions of KTX, and to some extent I'm hoping that "KTX" will eventually be synonymous with "KTX 2", similar to glTF, even though there's a longer history there.

I'm wondering however if we should not also provide (afterwards) another package like ktx-transcode (or ktx-decode)

It feels more difficult to make that fully reusable, for a couple reasons:

KTX 2 does allow compressed texture formats other than Basis Universal – the parser works regardless, but a transcoder or decoder would need to decide how much is in scope.
Which transcoder(s) should be supported?
Support Node.js, or just Web? Support non-WASM browsers?
Use Web Workers, or leave that to the end user?

Not to say it wouldn't be useful, but there are more difficult decisions on the transcoding side.

I agree there would be some decisions to be made, that's why we decided to create ktx2Decoder inside Babylon.js and not as a standalone package for the community to use, to avoid delay in implementation as we needed it quickly. However, even if restricting the scope, I think it would still be useful for a number of people/projects. Also, we can always add new features as time goes as long as it does not break backward compatibility. So it could start relatively small in scope:

Web only for WASM browsers - I don't know what has to be done to support node.js, but if not too much a hassle the support could be added at start
Basis Universal
Use Universal Transcoders when possible and MSC Transcoder else (as the universal transcoders are much faster)
No web workers in this lib. The lib is only a step above ktx-parse and add the transcoding processing, it's up to the higher level to setup a pool of workers if necessary.

That's basically what we did in ktx2Decoder.

We've included ktx-parse in three.js as of r125, for reading .ktx2 textures. In theory writing is also fully supported but I haven't done as much testing on that yet. At least for now we are putting a custom wrapper around it, since we want to use abstractions like THREE.FileLoader to fetch WASM binaries and such.

Closing this, since it is more of an open-ended idea than an actual issue. The repo is currently at https://github.com/donmccurdy/KTX-Parse, if you would like to use it and are having any issues let me know!


Suppress exceptions in the error logging thread when program exits.

Note that this PR made runtest.py take about twice as long (roughly 40s to 80s). I think it only made it slower to start and stop ray (probably mostly to stop ray).


Issue when using Material Wizard with Material Kit

Hello, I noticed that some of CSS breaks if you simply use the wizard together with the kit. I downloaded both the wizard and the kit files, and simply added the kit css and js files to the wizard index file in correct order. Here's the whole file:
`
<!doctype html>

Material Bootstrap Wizard by Creative Tim
<meta content='width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0' name='viewport' />
<meta name="viewport" content="width=device-width" />

<link rel="apple-touch-icon" sizes="76x76" href="assets/img/apple-icon.png" />
<link rel="icon" type="image/png" href="assets/img/favicon.png" />

<link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Roboto:300,400,500,700|Roboto+Slab:400,700|Material+Icons" />
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/latest/css/font-awesome.min.css" />

<link href="assets/css/bootstrap.min.css" rel="stylesheet" />
<link href="assets/css/material-kit.css" rel="stylesheet" />
<link href="assets/css/material-bootstrap-wizard.css" rel="stylesheet" />

<link href="assets/css/demo.css" rel="stylesheet" />

	                Creative Tim

MK

Made with Material Kit

	                    <form action="" method="">

`
Note: I removed the Material Core functions from jquery.bootstrap.js since they get loaded with material.min.js. Look at the result in latest Chrome version:

Edit: I don't know why it doesn't parse the code correctly in here, but here is a pastebin: http://laravel.io/bin/aN8q8

This is caused by
@include shadow-big-color($brand-info);
inside _pills.scss.
It applies to the anchor tags inside of li items.

What do we need to fix it? comment the include?
Thanks

@minikN @rbarcelos can you please share with us a link with the problem? From Laravel viewer, I can see only the code, not the final result. In this way, I will check and give you a solution. Something on https://jsfiddle.net/ would help.
Best,
Alex

I am not at home at the Moment. Give me a couple oft hours and I will describe what's causing the issue and hownI fixed it.

@rbarcelos @alexandru-paduraru Alright so the problem is pretty simple to describe. It occurs if you use the Material Wizard and the Material Kit together. In my case, I use the Material Wizard as a modal inside my project, which also uses the Material Kit. So in this scenario, I use both the wizard's css and the kit's css files, and at at least one point, they collide.
In Material Kit, if you use nav pills, an anchor tag (Link) gets applied a box-shadow by default (official documentation):

		 **// <-- THIS TAG**
			dashboard
			Dashboard

This is defined in material-kit/_pills.scss in line 31, 44, 57, 70 and 83. It's a block of code that gets repeated for every color (primary, success, warning, ....)
Example:
    &.nav-pills-info{
        > li {
            &.active > a{
                &,
                &:focus,
                &:hover{
                    background-color: $brand-info;
                    @include shadow-big-color($brand-info); **// THIS LINE**
                }
            }
        }
    }

So moving on to the wizard now, because it uses nav pills as well to build up the navigation, the above described rules get applied as well.
If you inspect your official wizard demo with chrome dev tools, you can see how you build up the wizard navigation:

Account

Room Type

Extra Details

Account

As you can see it's the same setup: ul.nav-pills > li > &:active > a > &:hover. Because the material kit assets are being used as well, material kit is unintentionally applying the shadow.
I hope this explanation makes clear what's going on. I fixed this issue by applying a block of scss to counter the behaviour. I did not want to alter the source files, hence why I use my own scss file with all my alternations.
.wizard-navigation {
  >.nav-pills{
      > li {
          &.active > a{
              &,
              &:focus,
              &:hover{
                  box-shadow: none;
              }
          }

      }
  }
}

This block of scss ensures the applied shadow by material kit gets removed again, but only if the ul.nav-pills is inside a div.wizard-navigation to make sure I don't alter the intended nav-pills behaviour across all material kit.
I hope this helps.

@minikN wow! That makes sense.
Congrats for the deep investigation. We will think of a way to fix this, but from what I see now, the best option is the one described by you, in this way the Material Kit is not altered and the problem in the wizard is fixed. So in a future update, we will make sure this will be included :D
Best,
Alex

@alexandru-paduraru always happy to help. The stuff you are offering for free is great. Loving it.


Update shim to work around new Buffer usage

Fixes #7
Refs https://github.com/diegomura/react-pdf/issues/1317
Caused by new Buffer usage from https://github.com/diegomura/react-pdf/pull/1839
This starts occurring for @react-pdf/renderer >= 2.1.2, but the workaround should not hurt older versions either
Error which this change fixes:
Uncaught ReferenceError: Buffer is not defined
at<EMAIL_ADDRESS>(unicode-properties.es.js:268:31)
at __init (chunk-GVC7CBB2.js?v=33aefd43:15:56) at<EMAIL_ADDRESS>(fontkit.browser.es.js:10:1)
at __init (chunk-GVC7CBB2.js?v=33aefd43:15:56) at<EMAIL_ADDRESS>(fontkit.browser.es.js:40110:29)
at __require2 (chunk-GVC7CBB2.js?v=33aefd43:18:50) at asyncToGenerator.js:35:1

Thanks !
I just tested this, it's not working as intended (still getting Buffer is not defined error message

Can't hurt to have an additional file shimmed either way. I'll cut a release and we'll see how we go.

Can't hurt to have an additional file shimmed either way. I'll cut a release and we'll see how we go.
@thekevinbrown thanks for the release, it isn't published though :)

Yup, I'm aware, my OTP device was damaged, I'm working on restoring my access.


CI: add GCC 12

Coverage remained the same at 59.29% when pulling 8f92c3c0660f7907eb6be1765bb7f9b8abd5eec1 on feature/ci-add-gcc-12 into c769f32bce9c4ff1610c43a876b8e2022caa8e18 on master.


Add support for Catalyst

Any plans for adding support for Catalyst (i.e. UIKitForMac)?
It seems that UIKitForMac is not the same as x86_64, for example, it may require some extra flags to be passed when built.
This thread might provide some useful info: https://forums.developer.apple.com/thread/117229

This is a bit more involved. Catalyst adds a new target to LLVM (a so called target tripple). So adding support to lipo also requires support from the rust compiler for this new target. I recently opened a PR for this into the Rust compiler and it was already merged:
https://github.com/rust-lang/rust/pull/63467
This is not part of the default toolchains, however. So if you're interested in this, you have to build rustc from master yourself in order to have a working toolchain with this triple. Then, you can try it out via normal cargo:
cargo build --target x86_64-apple-ios-macabi
I'm not entirely sure if this really works correctly though. I'd love help. So if you're interested, feel free to give it a try and see if it works for you!

Thanks @terhechte! That looks promising, I will try to compile a toolchain for the triple and see if I can build a binary for x86_64-apple-ios-macabi.

I've tried to build a toolchain for x86_64-apple-ios-macabi, and linked it to rustup.
./x.py build --target=x86_64-apple-ios-macabi
rustup toolchain link mytoolchain build/x86_64-apple-darwin/stage2/

Then I tried to build and test a bare-bone crate:

cargo +mytoolchain build --target x86_64-apple-ios-macabi succeeded without error.
cargo +mytoolchain test --target x86_64-apple-ios-macabi failed with a few error[E0463]: can't find crate for 'std'.

I feel like somehow mytoolchain didn't include libstd (at least not for x86_64-apple-ios-macabi)? However there seems to be a few files with names like libstd-04c8f9b7a9a8c33a.dylib or libstd-89019129fe48e132.rlib in the toolchain's directory.
Appreciate any help :)

Appreciate any help :)

@eyeplum
Hey! Sorry for the late reply, but I finally had some time to look into it again. Forgot to reply here. I figured out how to do it and created a small sample project here:
https://github.com/terhechte/rust-catalyst-example
Ping me if you have any questions :)

Any update on this issue?
I saw https://github.com/rust-lang/rust/pull/63467/files has been merged a long time ago.

@imWildCat I'm currently using the approach outlined in rust-catalyst-example in almost-production (~1000 beta testers). I did not figure out a way to make this work with the default rust compiler because I found it tricky to build the standard library for a different platform. However, I also didn't invest a lot of time there. I think if you can get the standard library to build, building a custom Catalyst Rust toolchain should be easy. You can also tell Cargo to load a custom toolchain in addition to stable and nightly. I'd also be happy if somebody figures out how to do that and documents it. The current documentation for how to do this didn't work for me. I'm still stuck at the point outlined in the PR:

Supposedly I need to compile everything into a toolchain somehow that I can then test via rustup to make sure that a binary compiled against the toolchain also works with Catalyst. I read this article, but I'm still lost and would love pointers what to do next here.

@terhechte Thank you so much for your reply! It helps me a lot!

Are you planning to add catalyst support ? rust-catalyst-example was updated and doesn't seem to be working anymore

@Crash22191 rust-catalyst-example should still work. In fact, it should be easier. If you're not targeting Apple Silicon, then it should work out of the box with Rust nightly. If you want to support Apple Silicon, you need (for the time being) a custom Rust toolchain, until this is merged.


Require sudo and curl

Hello,
the 2_prepare_tilemaker.sh script uses sudo and curl, both do not ship with default debian installations.
Including it in the setup script should solve the problem, but with sudo I don't know if that can have unpleasant side effects on systems used for other things as well.

I myself have used containers to test the previous scripts, so I see no problem putting the whole thing into them.
I don't know yet how I feel about the “instead”, I think the bash scripts should stay there. They show well that the system is actually relatively easy to use and allow self-explored testing.
Since those bash scripts will probably also run inside the containers, it should be possible to keep both without too much effort.


pantheon.switchboard-plug-security-privacy: 2.4.0 -> 2.4.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pantheon.switchboard-plug-security-privacy is: "Switchboard Security & Privacy Plug"
meta.homepage for pantheon.switchboard-plug-security-privacy is: "https://github.com/elementary/switchboard-plug-security-privacy"
meta.changelog for pantheon.switchboard-plug-security-privacy is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.1 with grep in /nix/store/gn2br0lsp9qy6mx47infmmcl258as3gk-switchboard-plug-security-privacy-2.4.1
found 2.4.1 in filename of file in /nix/store/gn2br0lsp9qy6mx47infmmcl258as3gk-switchboard-plug-security-privacy-2.4.1

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
pantheon.elementary-greeter
pantheon.switchboard-plug-security-privacy
pantheon.switchboard-with-plugs
pantheon.wingpanel-applications-menu
pantheon.wingpanel-with-indicators

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gn2br0lsp9qy6mx47infmmcl258as3gk-switchboard-plug-security-privacy-2.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pantheon.switchboard-plug-security-privacy https://github.com/r-ryantm/nixpkgs/archive/52e37aefdb90d2e623dcfa922cf82f5e112348bc.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gn2br0lsp9qy6mx47infmmcl258as3gk-switchboard-plug-security-privacy-2.4.1
ls -la /nix/store/gn2br0lsp9qy6mx47infmmcl258as3gk-switchboard-plug-security-privacy-2.4.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

pantheon.elementary-greeter
pantheon.switchboard-plug-security-privacy
pantheon.switchboard-with-plugs
pantheon.wingpanel-applications-menu
pantheon.wingpanel-with-indicators

Maintainer pings
cc @davidak @bobby285271 for testing.
cc https://github.com/NixOS/nixpkgs/issues/170361

Quite trivial change:

[x] AppChooser: cleanup (#139)
[x] Update io.elementary.switchboard.security-privacy.appdata.xml.in
[x] Release 2.4.1 (#140)


1.12.0: tail plugin crashes worker upon ENOENT (cannot stat() file)

Describe the bug
The in_tail plugin might discover a new log file, and then crash the worker upon the stat() system call due to ENOENT:
[info]: gem 'fluentd' version '1.12.0'

...

[error]: #0 /usr/local/bundle/gems/fluentd-1.12.0/lib/fluent/root_agent.rb:200:in `block in start'
[error]: #0 /usr/local/bundle/gems/fluentd-1.12.0/lib/fluent/plugin/in_tail.rb:234:in `start'
[error]: #0 /usr/local/bundle/gems/fluentd-1.12.0/lib/fluent/plugin/in_tail.rb:353:in `refresh_watchers'
[error]: #0 /usr/local/bundle/gems/fluentd-1.12.0/lib/fluent/plugin/in_tail.rb:390:in `start_watchers'
[error]: #0 /usr/local/bundle/gems/fluentd-1.12.0/lib/fluent/plugin/in_tail.rb:390:in `each_value'
[error]: #0 /usr/local/bundle/gems/fluentd-1.12.0/lib/fluent/plugin/in_tail.rb:409:in `block in start_watchers'
[error]: #0 /usr/local/bundle/gems/fluentd-1.12.0/lib/fluent/plugin/in_tail.rb:409:in `stat'
[error]: #0 unexpected error error_class=Errno::ENOENT error="No such file or directory @ rb_file_s_stat - /var/log/containers/foo-55fc795779-l66hb_foo_foo-ee7d580da4f6fac071b1e0fa8533fcada239a88404ed2fcde16480fbcd4a39fb.log"

I think this is a classical race condition. As this is part of the inotify-based watch system, of course there's the chance that between being delivered the signal that a new file is there and the code accessing it the file might already have disappeared again.
To Reproduce
Run in an environment that has log files popping up and quickly disappear thereafter (I guess, no clear repro on our side).
Expected behavior
At the system call boundary between application and OS the individual system calls like stat() / open() should always be wrapped with local error handling, expecting the system call to fail.
This can then be retried in graceful degradation fashion, w/o affecting the other operations performed by the worker process.
An appropriate action would be to log a warning/error showing how the system call failed.
Your Environment
Fluentd 1.12.0 on Linux
Not retried with 1.12.1 -- same problem seems to be there, based on commits and changelog.
Your Configuration
...
Your Error Log
see above
Additional context

This could be related to https://github.com/fluent/fluentd/issues/3224.
This might be a regression introduced via https://github.com/fluent/fluentd/pull/3155 / https://github.com/fluent/fluentd/pull/2992

The stat() call that crashes the worker is https://github.com/fluent/fluentd/blame/65a9edf4e05cf64c7ed0de56e12b3c9a0774e0d6/lib/fluent/plugin/in_tail.rb#L409
Looks like even before the last refactor this stat() wasn't protected:
https://github.com/fluent/fluentd/pull/3196/files#diff-456fdeb51bc472beb48891caac0d063e0073655dba7ac2b72e6fdc67dc6ac802R409
The worker subsequently restarts. As this affects the super early worker startup phase and results in an immediate crash, potentially a crash loop, I am not sure if this might result in data loss. https://github.com/fluent/fluentd/issues/3224 has more detail about that.

Attempt to fix: https://github.com/fluent/fluentd/pull/3275 -- quick review and feedback appreciated. Thanks!

Thanks for your work here @jgehrcke - we noticed lost logs after 1.12 upgrade due to issues with in_tail and immediately reverted. Didn't have time/depth to dig into what the problem was, but race conditions on log file create/delete seems possible.
We have a number of very short-lived cron jobs whose logs I imagine can be created and then disappear before fluentd has time to tail them.

Is there a timeline for when this bug fix will be released in a Fluentd Ruby Gem(https://rubygems.org/gems/fluentd)?
We're hitting this issue regularly and are eager to pick up the fix.
Also, since we're using https://github.com/fluent/fluentd-docker-image, we'd prefer a Fluentd Ruby Gem than simply applying a patch to our existing Fluentd instance.

We are planning to release 1.12.2 until end of this month.

We released v1.12.2.


[enhancement]: Merging Checkpoints!?

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
Greetings, as the number of models is increasing at a rapid pace. Merging models seems to be a no brainer.  Such a functionality would be very practical.
Thank you,
Alternatives
I heard AUTOMATIC1111  has a similar feature but I couldn't find the documentation yet.
Aditional Content
No response

I have automatic1111 running locally just for this feature. I then bring the resulting model back into Invoke and list it in the models yaml. Would love Invoke to have this ability natively.

@discordinated i assume you're running automatic1111 locally on PC/Windows or Linux ? I've been trying to find out if it can run on M1s, so far, all attempts have been unsuccessful. Invoke worked though and very happy!

@Humanoidme automatic1111 can run on my MBP, after modify some line, but it is too slow(although the usage of GPU is more higher than invokeai, but the speed is about 1/10 of invokeai), I am using an eGPU, I think it can run on M1 too, you can try

@discordinated i assume you're running automatic1111 locally on PC/Windows or Linux ? I've been trying to find out if it can run on M1s, so far, all attempts have been unsuccessful. Invoke worked though and very happy!

I'm running it on a M1 Max 32GB - To get it running I just followed their install guide, it was reasonably painless.
It's much slower than Invoke as FreeBlues has said, and many of the extra functions do not work on MPS. For example last I checked LDSR wasn't working and would crash due to hard coded Cuda calls. I'd LOVE To see Invoke add in LDSR - for now I fall back to doing that on Colab using this notebook.
I don't use automatic1111 day to day, mostly due to poor performance and the bugs on MPS. Certain things it does do great or I can't get elsewhere however, like merging. But I don't need to do that very often, so at most I check back in once a week or so. Invoke is just so much nicer to use - both visually as well as in terms of workflow and performance.

There are ambitions to serve the full set of usecases w.r.t. training (textual inversion overhaul, dreambooth, etc.) and managing models.
There's a significant architecture overhaul we're in the process of executing on, and after which I think will have time to dig into this space, but I think we'd also benefit from a contributor who is very knowledgeable about this domain to tackle it.

@discordinated @FreeBlues thanks to both for taking time to share your insights and knowledge

I've got two model feature enhancements in mind for the development branch. The first is to establish a folder in which you can place .bin files from textual inversions and have a searchable library of prompt keywords that you can use with them to add particular subjects and styles.
The second is model merging. This will probably be a script that runs outside of either the CLI or the GUI at first. The challenge for me is that I don't know how to do model merging just yet!
I'll start working on these things after the release, so sometime later this week or next.

You need help with model merging? I can help if you want

@lstein


Knives/Tomes Types, New Weapon Triangle

Consolidate Anima, Light, and Dark tomes into a single Tomes weapon type, and use one of the extra types for a new weapon type, Knives.
Knives are by default 1-2 range, but they have a brave 1 range subtype (Daggers).
Create Weapon Triangle with Tomes beating Bows, Bows beating Daggers, and Daggers beating Tomes (Fates but separate).

Implemented mechanically, still needs visuals to match


Remove empty table cell from edit user template

Changes

Removes empty, extra table cell from the edit user template

Before

After

Jira Ticket
https://jira.cms.gov/browse/MAT-1632
Pull requests into Bonnie require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] This PR is into the correct branch.
[ ] JIRA ticket for this PR:
[ ] JIRA ticket links to this PR
[ ] Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[ ] If UI changes have been made, google WAVE plug-in has been executed to ensure no 508 issues were introduced.
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass (remember to update Gemfile when applicable)
[ ] Test fixtures updated and documented as necessary ( see internal wiki )
[ ] Code coverage has not gone down and all code touched or added is covered.

In rare situations, this may not be possible or applicable to a PR. In those situations:

Note why this could not be done or is not applicable here:
Add TODOs in the code noting that it requires a test
Add a JIRA task to add the test and link it here:

[ ] Automated regression test(s) pass

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA test links:
[ ] Justification for using JIRA tests:
[ ] JIRA tests have been added to sprint

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA tests have been run and pass
[ ] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA tests have been run and pass
[ ] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Do you want similar fix for QDM bonnie as well?

@adongare I don't know. That's an awful lot of work. 😉
Yes, I'm going to do that, too.


ctl.sh: Switch between 'docker compose' and 'docker-compose' syntax autodetect

https://stackoverflow.com/questions/66514436/difference-between-docker-compose-and-docker-compose


[2.0-wip] Form input focus color - broken?

After one of the recent commits, form input focus color looks grayish - after seeing the blue outline for a split second. Is this broken by another change?
QUICK LOOK to the problem: http://i.imgur.com/jIZtC.png

Sorry about that, my bad :). All fixed!


Can use this with Websockets?

Hi, I'm looking for a way to serve both my built vite frontend as well as a websocket endpoint from the same project, like:
/ - dist/index.html
/ws - websocket
would mix be able to help with that? Im not sure how the ws node package would work in the handler.ts configuration. thanks!

I had this issue too. This is how I got mine working:
import express from 'express';
import { Server } from 'http';
import { parse } from 'url';
import { WebSocketServer } from 'ws';

const app = express();
const wss: WebSocketServer = new WebSocketServer({ noServer: true, path: '/ws' });

wss.on('connection', (socket, req) => {
	socket.send('hello');
});

app.get('/api/hello', (req, res) => {
	res.json({ hello: 'world' });
});

app.use((req, res, next) => {
	const server = req.connection.server as Server;

	if (!server.hooked) {
		server.hooked = true;

		server.on('upgrade', (request, socket, head) => {
			const { pathname } = parse(request.url || '');
			if (pathname === '/ws') {
				wss.handleUpgrade(request, socket, head, function done(ws) {
					wss.emit('connection', ws, request);
				});
			}
		});
	}
	next();
});

export const handler = app;

You can probably simplify out the express server quite easily if you don't need it.


Training Script

Hi @xadrianzetx, thanks again for this repository and supporting it. I am trying to create a custom model using the code in the Jupyter notebook: https://colab.research.google.com/drive/1eJFOg_1o5D-osHZseNlpE-WGR-p8jDqa?usp=sharing
It simply creates a CoralDeepLabV3 model and compiles it for the Edge TPU. However, when running it with the inference script the result is not as expected:

Any idea what I could be doing wrong? Is it required to use an older version of the edgetpu-compiler if the newest version has no errors?
Pasting the code here as well:
pip install git+https://github.com/xadrianzetx/coral-deeplab.git

! curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
! echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list
! sudo apt-get update
! sudo apt-get install edgetpu-compiler
! edgetpu_compiler -v

import os
import re
import sys
import uuid
import unittest
import subprocess

import numpy as np
import tensorflow as tf

import coral_deeplab as cdl

def fake_dataset_generator(shape, n_iter):
    def dataset():
        for _ in range(n_iter):
            data = np.random.randn(*shape)
            data *= (1 / 255)
            batch = np.expand_dims(data, axis=0)
            yield [batch.astype(np.float32)]
    return dataset

def quantize_and_compile(model, dataset):

    # setup tflite converter
    converter = tf.lite.TFLiteConverter.from_keras_model(model)
    converter.representative_dataset = dataset
    converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS_INT8]
    converter.inference_input_type = tf.uint8
    converter.inference_output_type = tf.uint8
    converter.optimizations = [tf.lite.Optimize.DEFAULT]

    # quantize
    quantized = converter.convert()
    model_name = f'{uuid.uuid4()}.tflite'
    model_path = os.path.join(os.getcwd(), model_name)
    open(model_path, 'wb').write(quantized)

    # compile
    cmd = ['edgetpu_compiler', '-a', '-s', model_path]
    p = subprocess.Popen(cmd, stdout=subprocess.PIPE)
    p.wait()
    stdout = p.stdout.read()

    return stdout.decode()

model = cdl.applications.CoralDeepLabV3(weights='pascal_voc')
datagen = fake_dataset_generator((513, 513, 3), 10)
stdout = quantize_and_compile(model, datagen)
print(stdout)

! cp /content/10582856-eda3-4088-bf25-1e6a7e5e75de_edgetpu.tflite /content/drive/MyDrive/

The problem seems to be in dataset generator you're using. It's just a dummy used in CI, where we do not care about model performance. Instead of using np.random.randn, how about feeding model actual samples from e.g. pascal voc test set?

Is it required to use an older version of the edgetpu-compiler if the newest version has no errors?

You can probably use any compiler version as long as it maps model fully to TPU. I haven't been checking for a while, but if I remember correctly, at some point google removed -a flag allowing for subgraphs, hence compiler in this repo is pinned to last known working version.


rav1e: fix strip option mangling on x86_64-darwin

rav1e-0.7.1 slightly changes strip option construction in
https://github.com/xiph/rav1e/commit/43fb165e5e07ac047dd59d9d2278bed5da95deb4
Update mangling part to restore stripping.
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 282849 run on x86_64-linux 1

substituteStream(): WARNING: '--replace' is deprecated, use --replace-{fail,warn,quiet}. (file 'build.rs')

So --replace-fail I guess?

substituteStream(): WARNING: '--replace' is deprecated, use --replace-{fail,warn,quiet}. (file 'build.rs')

So --replace-fail I guess?

Good point! Switched to --replace-fail.


Update backup-azure-security-feature-cloud.md

Update powershell code.
Changed vault to myVault.
Updated myVaultID to myVault.ID

#sign-off


Default Flake8 config ignored

I'm trying out the Python checks in beta and I noticed that it ignores the default Flake8 configuration files: http://flake8.pycqa.org/en/latest/user/configuration.html

In your project in one of setup.cfg, tox.ini, or .flake8.

Here is an example of pull request with violations. The one in surveys/models.py is rightfully spotted, but the one in docs/conf.py should be ignored as per the config in the setup.cfg.
I've tried to set config_file: setup.cfg but it looks like Hound doesn't like it, it apparently failed to run the check.
I appreciate Python is in beta, so I thought I'd report the issues I've spotted.
PS: I noticed that links to Flake8 in your docs are broken: https://houndci.com/configuration#python, but this doesn't look like it's part of this repo.

@browniebroke You should be able to specify the path to your config file in .hound.yml:
python:
  enabled: true
  config_file: .flake8.ini


Update BERT Pipeline for multi-class

...comment and clean code, push changes to GitHub, and update primary README; include setup of commuter server and classification API.

This is done, just need to clean up the code now, it has become a very long Jupyter notebook

Don't forget the README ;)

How we doing on this task? Will be able to compare single vs multiple #2?


Provide PHP 8.2

PHP 8.2 is scheduled for end of November
will need xdebug 3.2

Works already:
$ docker run -ti --name php --rm flownative/php:8.2.0RC1 bash

                    PHP
                    This Docker image was handcrafted for you
#standwithukraine   by Flownative.         www.flownative.com

[info] syslog-ng: Starting ...
[info] syslog-ng: Logging mode is text
[info] syslog-ng: Running as process #11
[info] PHP-FPM: Initializing configuration ...
[info] PHP-FPM: Xdebug is disabled
[info] PHP-FPM: igbinary is disabled
[info] Supervisor: Starting ...
[info] Supervisor: Running as process #35
I have no name!@0aa2995af040:/opt/flownative/php$ php -v
[05-Sep-2022 10:21:43 UTC] PHP Warning:  PHP Startup: Invalid date.timezone value '', using 'UTC' instead in Unknown on line 0
PHP 8.2.0RC1 (cli) (built: Sep  5 2022 10:11:01) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.0RC1, Copyright (c) Zend Technologies
    with Zend OPcache v8.2.0RC1, Copyright (c), by Zend Technologies

Eliminated the warning about the timezone:
$ docker run -ti --name php --rm flownative/php:8.2.0RC1 bash

                    PHP
                    This Docker image was handcrafted for you
#standwithukraine   by Flownative.         www.flownative.com

[info] syslog-ng: Starting ...
[info] syslog-ng: Logging mode is text
[info] syslog-ng: Running as process #11
[info] PHP-FPM: Initializing configuration ...
[info] PHP-FPM: Xdebug is disabled
[info] PHP-FPM: igbinary is disabled
[info] Supervisor: Starting ...
[info] Supervisor: Running as process #35
I have no name!@1497a3ef26dd:/opt/flownative/php$ php -v
PHP 8.2.0RC1 (cli) (built: Sep  5 2022 10:29:44) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.0RC1, Copyright (c) Zend Technologies
    with Zend OPcache v8.2.0RC1, Copyright (c), by Zend Technologies

See https://github.com/flownative/beach-controlpanel/pull/162

PHP baut schonmal, siehe https://github.com/flownative/docker-php/actions/runs/3687105458

Hm, hier fehlt es noch: https://github.com/flownative/docker-beach-php/actions/runs/3687996264

✅


Is there a way to make it work with a custom model from civitai? instead of stable diffusion v1.5

Ive tried, forcing this with:
!cd /content/gdrive/MyDrive/models; wget https://civitai.com/api/download/models/223670 --content-disposition
then on MODEL_PATH: "/content/gdrive/MyDrive/models"
and then have to force version detection with this line: Custom_Model_Version='1.5' ( if I dont force it the script is unable to detect version)
but get into a error loop of "Conversion error"

Can't simply drop the model in /content/gdrive/MyDrive/models via drive.google.com. Or is the goal to pull any model any time? I model swap often, so for me it's best to just have a bunch in the folder.

found the issue, I was pasting the route to the folder containing my model, but this colab needs the router directly to the mode:
MODEL_PATH: "/content/gdrive/MyDrive/models/epicphotogasm_lastUnicorn.safetensors"


Align error messages with APIcast

Just a small frontend improvement to have the same messages for APIcast and extension, there might still be a small differences (APIcast might filter some cases which I do not), but it is much closer than it was and overall it should be an improvement.

rebase when the clippy fix is merged and merge this PR


[HOTFIX] Set interpreter context in zeppelin context from SparkSqlInterpreter

What is this PR for?
When running %sql paragraphs sometimes a NullPointer is thrown instead of presenting the result.
This was traced back to sparkInterpreter.getZeppelinContext().setInterpreterContext(context); not being called as expected from SparkSqlInterpreter. Since the SparkInterpreter is used from the SparkSqlInterpreter, if a %spark paragraph is executed before a %sql paragraph it works as expected (as SparkInterpreter sets the interpreter context in the zeppelin context).
What type of PR is it?
[Hot Fix]
Todos
What is the Jira issue?
Hotfix
How should this be tested?
Start the spark context by executing
%sql
select 1

Expected result is a table with 1 in.
Before this patch a NullPointer will be thrown.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

LGTM, BTW for a long term solution, I think we should initialize ZeppelinContext properly (including set InterpreterContext) in some base class instead of initialize in each interpreter manually.

@zjffdu I agree. A also noticed there are plenty of sketchy synchrnoized-blocks that doesn't really work as intended. But that's a refactor for another PR

Right, we could do it in another PR.

@FireArrow Could you help check the failed test ?

I looked at the tests, and they fail at the same place even after re-running them, but it seems unrelated to my changes. Could someone else also take a look and see if I'm missing something?

Yeah, that's seem flaky test. Thanks @FireArrow I will merge it if no more comments.
Failed tests:
  NotebookSecurityRestApiTest.testThatOtherUserCannotAccessNoteIfPermissionSet:81->createNoteForUser:155 test note create method:
Expected: HTTP response <200> from /api/notebook/
     but: got <302> Found
  NotebookSecurityRestApiTest.testThatUserCanSearchNote:115->createNoteForUser:155 test note create method:
Expected: HTTP response <200> from /api/notebook/
     but: got <302> Found
  NotebookSecurityRestApiTest.testThatWriterCannotRemoveNote:98->createNoteForUser:155 test note create method:
Expected: HTTP response <200> from /api/notebook/
     but: got <302> Found
  NotebookSecurityRestApiTest.testThatOtherUserCanAccessNoteIfPermissionNotSet:72->createNoteForUser:155 test note create method:
Expected: HTTP response <200> from /api/notebook/
     but: got <302> Found
  NotebookSecurityRestApiTest.testThatUserCanCreateAndRemoveNote:63->createNoteForUser:155 test note create method:
Expected: HTTP response <200> from /api/notebook/
     but: got <302> Found
Tests in error:
  SecurityRestApiTest.testGetUserList:69 » JsonSyntax java.lang.IllegalStateExce...
  SecurityRestApiTest.testTicket:55 » JsonSyntax java.lang.IllegalStateException...


Starting to implement Event::to_ll for all event types.

So far only Quit, Window, KeyDown and KeyUp are implemented.

But if you approve of the general approach here and can verify better than I that it's correct, I'll keep adding more.
Starting to address issue #530

Good start! One issue blocking this

What issue is blocking this?  I might be able to gnaw on it myself, maybe.
Since you're in favor, I'll go through and get the rest of the event types.

It's all good now - cheers!


Faster short_hash implementation in type

This PR alters the short_hash function to reduce the amount of work done to mix the hash.
It doesn't replicate exactly the behaviour of hash (hash s, !h) instead it passes !h in as a seed value which is mixed with hash s. This may or may not be acceptable.
Benchmarking the change I see test/irmin-pack/bench.exe --clear -a 20 taking 1.61s with the change vs 1.85s baseline (after running a couple of times to burn in).

That looks great, thanks!


Adding nucleo f746zg support to microros setup for FreeRTOS

Adding support for nucleo f746zg

Hello @edesta-be , last commit implement the UROS_CUSTOM_APP_FOLDER feature. Check this: https://github.com/micro-ROS/micro_ros_setup/pull/197/commits/283bbedf2cc819df47d7eed02510eef6f650678c
The usage should be like:
mkdir my_apps_folder; cd my_apps_folder;
mkdir my_app; cd my_app;
# Create here app.c and app-colcon.meta

cd [micro_ros_workspace];
export UROS_CUSTOM_APP_FOLDER=path/to/my_apps_folder
ros2 run micro_ros_setup configure_firmware.sh
#Output should be:
#micro-ROS application name must be provided: ros2 run micro_ros_setup configure_firmware.sh [app name] [options]
#Available apps for FreeRTOS and nucleo_f746zg:
#+-- my_app

ros2 run micro_ros_setup build_firmware.sh

Can you try it? If you are ok with this feature and CI is ok I will merge this PR.
BTW, I have added this board to the Readme and I have set you as code owner, please check:

https://github.com/micro-ROS/micro_ros_setup/pull/197/commits/e71b5ab126e63ce093753ef3c6727e08afc99ff1
https://github.com/micro-ROS/micro_ros_setup/pull/197/commits/2a399ac1a1c2691fb525f9b9db2798a1272bc743

@pablogs9 looks to good to merge on my end! Thank you!


lower bound overhead

Computes the lower bound overhead metric from "Distilling the Real Cost of Production Garbage Collectors" by Cai et al.
Example of usage:
$JULIA_BIN run_benchmarks.jl serial linked tree -n1 --json > out1
$JULIA_BIN run_benchmarks.jl serial linked tree -n1 --json > out2
$JULIA_BIN run_benchmarks.jl serial linked tree -n1 --json > out3
$JULIA_BIN lower_bound_overhead.jl out1 out2 out3

Example of output:
┌───────────────────────────┬──────┬──────┬──────┐
│                           │ out1 │ out2 │ out3 │
├───────────────────────────┼──────┼──────┼──────┤
│ lower bound overhead [ms] │  341 │  814 │  344 │
└───────────────────────────┴──────┴──────┴──────┘

I find it more convenient to connect everything through a shell script, but could be done on a single julia file.
The metric computed by the functionality in this PR is wall clock time. Not sure how to parse cache misses/cycles from perf, but could be done in the future as well.

Superseded by https://github.com/JuliaCI/GCBenchmarks/pull/48.


Create catalog.yaml

Adding simple Catalog.yaml file

Thanks for contribution. We already have a catalog file in the accelerator branch. The main branch is the original fork from the Spring Project, so we can't add anything there.


PHANTOM_WORKER_ITERATIONS affect the frequency of collapse

Now,I kown the number of iterations is how long before we forcibly shut down PhantomJS to prevent the memory leak issue. when I visit the frequency of five times per second, all phantomjs will collapse together, and then restart together, which leads to the CPU occupancy rate is very high.
.Another question, what I use is inMemoryHtmlCache, process not Shared cache? How to weigh the performance and stability?

5 URLs per second sounds like a little too much for PhantomJS to handle in our experience. If each URL takes 5 seconds to load then that means you would have an average of 25 pages loading at any given moment. We like to load balance across many machines to prevent those issues. The tree-kill module that we use kills phantomjs based on the worker pid. Are you seeing it kill all phantomjs instances at the same time?
If you need a cache across more than 1 worker, you shouldn't use the inMemoryHtmlCache. You should use a distributed cache like the S3 cache.

This should be fixed in the latest version of Prerender (4.0.3)

ok,I will have a try,thanks!


arangorestore terminates arangod for good

May be related to #12896.
My Environment

ArangoDB Version: 3.9.2 on server and local
Deployment Mode: Single Server
Deployment Strategy: Default ArangoDB Oasis
Configuration: Default
Infrastructure: Azure
Operating System: server - whatever Oasis uses by default; local - MacOS Monterey 12.6
Total RAM in your machine: 8 GiB on server, 16GiB local
Disks in use: local SSD
Used Package: local homebrew

Component, Query & Data
Affected feature:

arangodump and arangorestore
AQL query (if applicable):
AQL explain and/or profile (if applicable):

Dataset:

Sent to<EMAIL_ADDRESS>referencing issue number (please remind me if I forgot 😊).
Size of your Dataset on disk:

Less than 1 MB.
Replication Factor & Number of Shards (Cluster only):

Steps to reproduce

Dump the server data by running arangodump --server.endpoint <endpoint> --server.database <database> --server.authentication true. The resulting data is provided in "Dataset".
Restore the data on local by running arangorestore --server.database <database> --server.authentication true --input-directory "dump" --create-database.

Problem:
The moment arangorestore finishes, the arangod process terminates.
Restarting arangod results in the same error (see below for error messages).
The only way I could get arangod back up is by executing rm -r /usr/local/var/lib/arangodb3* - effectively wiping all local data. For context: Reinstalling with homebrew didn't solve the error.
Error outputs:
These two types of errors occurred:
2022-09-23T15:55:00Z [16483] INFO [cf3f4] {general} ArangoDB (version 3.9.2 [darwin]) is ready for business. Have fun!
2022-09-23T15:55:22Z [16483] FATAL [a7902] {crash} 💥 ArangoDB 3.9.2 [darwin], thread 10 caught unexpected signal 4 (SIGILL): signal handler invoked
2022-09-23T15:55:22Z [16483] INFO [ded81] {crash} available physical memory:<PHONE_NUMBER>4, rss usage: 203505664, vsz usage:<PHONE_NUMBER>8, threads: 47
[1]    16483 illegal hardware instruction  arangod

2022-09-23T15:26:24Z [15807] INFO [6ea38] {general} using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2022-09-23T15:26:26Z [15807] FATAL [a7902] {crash} 💥 ArangoDB 3.9.2 [darwin], thread 10 caught unexpected signal 4 (SIGILL): signal handler invoked
2022-09-23T15:26:26Z [15807] INFO [ded81] {crash} available physical memory:<PHONE_NUMBER>4, rss usage: 204435456, vsz usage:<PHONE_NUMBER>2, threads: 46
[1]    15807 abort      arangod

Expected result:
Restore works without errors...
Further thoughts:
Would it help to use arangoexport and arangoimport when doing backups cross-OS? :thinking:

Hi,
you're using ArangoDB or its tools on a machine that doesn't have the required instruction sets.
Rosetta (if you're on M1? ) doesn't support AVX and SSE2 which we require with the 3.9 binaries.
you either need to use the docker containers tagged with arangodb/arangodb:3.9.4noavx or use devel / 3.10 nightly native ARM binaries.

Thank you 🙏 I'll just try 3.10 on my machine.

Rosetta (if you're on M1? )

That's right.

Works with 3.10 👌

thanks for confirming.


Unable to get steam3 credentials.

I'm getting the above error on Mac terminal.. I'm sure my credentials are ok (username from steam account + password).
I also tried with 2FA turned off.

Is it possible you're running into this issue: Connection to Steam failed? The logs look similar at least.
If that's the case the script as it stands will probably not work, however there may be ways to manually obtain the game files, provided Steam generally works.

Turning off VPN (Proton) helped. Thanks!


[top_earlgrey,ast] Add CSRs to control muxes on IOB[0:3] and expose them as outputs

https://github.com/lowRISC/opentitan/pull/23201 will add muxes on IOB[0:3]. The selectors of those muxes are currently tied off (there are TODOs referencing this issue in the code). Those selectors instead need to be driven based on CSR bits in AST. So the following changes are required:

[ ] Add CSR bits in AST.
[ ] Expose the values of those bits as outputs of AST.
[ ] Connect these AST outputs to the mux selectors.

@meisnere if you can implement the first two items, I can do the third one afterwards (as discussed yesterday)


Toggle switches for server-side flags are slow and can feel sticky

From @gnprice's comment at #3944:

I suspect what's happening is that when you touch it, we make a request to the server to update your status, but keep the switch at the last value we had from the server. Then a bit later we get an event from the server reflecting the update we requested.

While the problem in #3944 is a bit more involved, this is a component of it; and it's often visible without the confounding factors in other cases. The result then is that the user taps the switch, and either...

it doesn't react at first, then flips after a delay; or
nothing happens at all (because the network request failed, and we don't report it).

There's no perfect solution here, given the reality that the request may fail, e.g. because the network connection is flaky. But it's definitely possible to do better than the current behavior.

An outline (with much handwaving) of one possible replacement behavior:

The user taps a switch with server-backed state.
The switch:

visibly disables itself;
brings up a spinner; and
makes its API request.

When the API request concludes, the switch reenables itself, and:

on failure, shows a toast or dialog-box reporting the error;
on success, shows the (presumed) new value.

An alternative option to the final parenthetical presumption would be to remain in the disabled-spinning state until the server actually reports that the state has changed; this is plausible (and arguably more accurate, from some points of view), but may be susceptible to a race near event-queue death time.

(Note that for some switches -- and it's not clear what variables are involved here -- there's a further issue that sort of masks this one. In those cases, the switch immediately responds, jumping straight to the other value with no animation; then jumps back; then when/if the request succeeds, jumps once more to the new state. See #3944 for details.)


[Bug] Parens around single import/export are not removed

Describe the bug
In from vyper.interfaces import (ERC20), the parens around ERC20 should be removed but they are not

Same for exports currently

Fixed by #41


fix key error

fix faucet get contract address key error

fix faucet get contract address key error

Thanks for your contribution, please add WeChat yanyanho666 to join our group.


[Question] Streaming output from push

Hi,
First of all thanks for the amazing package.
Is there a way to stream output for the push command?
Indeed, for example, the build command as a stream_logs argument that allows this behavior

I'm glad this package is useful to you! And thanks for the issue. This is not possible right now, but I'll keep it somewhere on the back of my mind, I might allow it in the future. For the moment, you can only see the logs directly in python's stdout, but I suppose that if you opened the issue, it's not enough to satisfy your use case.
By the way I'd be interested to know why you want to do that. This might help me provide a better api for the users long-term :)

I am currently building a CLI that uses the docker client under the hood. Thus, I need to parse the output of docker commands in order to get information from them. For example, for the push command, I want to parse to output to give an eta on the duration of the push.
However, right now it seems not possible to capture the output of the python-on-whales methods. https://github.com/gabrieldemarmiesse/python-on-whales/issues/292#issuecomment-1809738612

Indeed, i'm currently working on capturing the logs of compose commands, I guess we could do something similar for push.
Concerning the default behaviour, the only way I found to avoid messing up the TTY output was to not capture anything. But maybe there is a better way by going through the python process, but I'm not aware of it.


fix grading comment

Description
related to #2263, please help to check if this is okay.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test

Checklist

[ ] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 34.439%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
4582

Relevant Lines:
12377

💛  - Coveralls


Add a VSCode extension

We could have a Visual Studio Code extension version of this tool.
Some examples : https://code.visualstudio.com/Docs/extensions/example-hello-world

finished with --tsconfig (Project based)
btw. could you although generate md file. or let me contribute you to add these 5 lines.
now i stuck while Publishing the Extension. ;(

@web-dave can you clarify your thoughts please ?

This were two topics in one sentence. Sorry.

Generate although md files. (*.md). I'll make a pullrequest.
I get an error while publishing to vscode ext store. So this is no topic for you, just info.

Got a answer from vscode team. The package is to big. Max size is 20mb. Shop I have to refactor the plugin.

may be we could move some deps to devDependencies in package.json. For instance: conventional-changelog-cli and typings don't have to be installed in prod mode.

Another idea is to hold ago the code in the plugin.
Now I set this module as adepedency.
Some dependencies are now duplicated.
I try this weekend.

published right now
https://marketplace.visualstudio.com/items?itemName=web-dave.ng2-dg

Many thanks for this. Is there a way to change the settings somehow? All my components are beneath each other. The only dependencies shown in the svg are from a component to its .html file.


Add more metrics

Right now just basic prom metrics are implemented. Add more metrics like cache hits, pulls from bitwarden, resets, etc

Satisfied by #10


ci: add self-hosted runners

We are at capacity with the GHA concurrent jobs limits, and this slows down development quite a lot.
Let's try to configure AWS spot instances, e.g. by following among the lines of https://github.com/philips-labs/terraform-aws-github-runner

A self-hosted runner is ready. I just need to boot it.

This issue is about having more than one. We run quite some jobs in parallel, and it would quickly become another bottleneck

@Itxaka I'll take care of the single node only setup then :+1:

I will have a look at some heat templates to easily add/remove ecp self-hosted runners

@Itxaka added a sample k8s deployment of gh runner here: https://github.com/rancher-sandbox/cOS-toolkit/wiki/Github-runner-on-k8s

This is a POC of a script to deploy github runners in ECP: https://github.com/rancher-sandbox/cOS-toolkit/pull/304
Tested and working, see readme for details
Works...ok-ish. Workflows would need some adaptations to fully work, user-data migth need also adaptations if we want to use this, but it makes no sense to develop it further.

Need to remove the build dir on each job as it can be left over from a previous job
No vagrant/qemu/packer installed by default, so not all jobs can run.
We can add those packages and run everything in the same base, no more osX required for qemu builds
We could have workers based on size and OS and then use the labels to run the jobs on them, still requires more config and work to the deployment scripts and workflows.
We could have a "master " node that receives one job, creates an on demand instance with this scripts and uses it for one job, deleting it afterwards.

Makes it behave more like github runners.
Requires 1 "master" machine to sync everything
Should be easy to automate the creation, deletion, token adquisition, etc...
Requires investing in automation
Requires creating custom images with software preinstalled to avoid 5/10 minute machine boot and configuration per job

We could also have a big node that spawns several docker containers with the workers.

Allows us more flexibility
Supports wide range of base os
REALLY easy to grow or decrease
If managed via this scripts, its really easy to duplicate/delete/recreate

#319  should fix the problem for the time being.
The templating mechanism support to switch to local-runners - I've added ~8 of them without noticing notable peformance gains except the increase parallelism. Although that wouldn't last long as we run many more parallel jobs than 8 for each run.
Pipeline has been reworked and build times have been shrinked - the template supports using the local-runner only as build node and not as test-node (as requires virtualization and such).
To bring up the workers, I've created a cOS VM with the following cloud-init config:
name: "Default user"
stages:
   boot:
     - name: "Hostname and setup"
       hostname: "cos-node-1"
       commands:
       - echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
       dns:
        nameservers:
        - X
#       commands:
#       - passwd -d root
   network:
     - name: "Setup SSH keys"
       authorized_keys:
         admincos:
         - github:mudler
         root:
         - github:mudler
     - if: '[ -z "$(blkid -L COS_SYSTEM || true)" ]'
       name: "Load persisted ssh fingerprint"
       commands:
       - |
            # load ssh fingerprint
            if [ ! -d /usr/local/etc/ssh ]; then
            systemctl start sshd
            mkdir /usr/local/etc/ssh || true
            for i in /etc/ssh/*.pub; do cp -rf $i /usr/local/etc/ssh; done
            fi
     - name: "Setup k3s"
       if: '[ -z "$(blkid -L COS_SYSTEM || true)" ]'
       directories:
       - path: "/usr/local/bin"
         permissions: 0755
         owner: 0
         group: 0
       commands:
       - |
            curl -sfL https://get.k3s.io | \
            INSTALL_K3S_VERSION="v1.20.4+k3s1" \
            INSTALL_K3S_EXEC="--tls-san additional-outside-ip" \
            INSTALL_K3S_SELINUX_WARN="true" \
            sh -
   initramfs:
     - if: '[ -z "$(blkid -L COS_SYSTEM || true)" ]'
       name: "Persist"
       commands:
       - |
            target=/usr/local/.cos-state

            # Always want the latest update of systemd conf from the image
            mkdir -p ${target}/etc/systemd/
            rsync -av /etc/systemd/ ${target}/etc/systemd/
            # Only populate ssh conf once
            if [ ! -e ${target}/etc/ssh ]; then
            mkdir -p ${target}/etc/ssh/
            rsync -av /etc/ssh/ ${target}/etc/ssh/
            fi
            # make /tmp tmpfs
            cp -f /usr/share/systemd/tmp.mount ${target}/etc/systemd/system/
            # undo /home /opt mount from cos immutable-rootfs module
            sed -i '/overlay \/home /d' /etc/fstab
            sed -i '/overlay \/opt /d' /etc/fstab
            umount /home
            umount /opt
            # setup directories as persistent
            for i in root opt home var/lib/rancher var/lib/kubelet etc/systemd etc/rancher etc/ssh usr/libexec; do
            mkdir -p ${target}/$i /$i
            mount ${target}/$i /$i -t none -o bind
            done
            # This is hidden so that if you run some selinux label checking or relabeling the bind
            # mount won't screw up things.  If you have two files at different paths they will get
            # labeled with two different labels.
            mkdir -p ${target}/empty
            mount ${target}/empty ${target} -o bind,ro
            # persist machine-id
            if [ -s /usr/local/etc/machine-id ]; then
            cat /usr/local/etc/machine-id > /etc/machine-id
            else
            mkdir -p /usr/local/etc
            cp /etc/machine-id /usr/local/etc
            fi
            # ensure /var/log/journal exists so it's labeled correctly
            mkdir -p /var/log/journal
     - name: "Setup users"
       users:
          admincos:
            homedir: "/home/admincos"
     - name: "groups"
       ensure_entities:
       - entity: |
                 kind: "group"
                 group_name: "wheel"
                 password: "x"
                 gid: 1020
                 users: "admincos"
       files:
       - path: "/etc/sudoers.d/wheel"
         owner: 0
         group: 0
         permission: 0600
         content: |
                   %wheel ALL=(ALL) NOPASSWD: ALL
       - path: "/etc/modprobe.d/ipv6.conf"
         owner: 0
         group: 0
         permission: 0664
         content: |
                    alias net-pf-10 off
                    alias ipv6 off
                    options ipv6 disable_ipv6=1

For the GH deployment, I've followed https://github.com/rancher-sandbox/cOS-toolkit/wiki/Github-runner-on-k8s


Feature/93 ide docs examples

Incorporated the endaq.ide README into the docs, and created a page for endaq.ide.measurement. Some minor formatting changes.
This PR is specifically focused on endaq.ide documentation; while other sections also need expansion, those should probably be their own PRs.
See issue #93

docs rendered here: https://docs.endaq.com/en/feature-93_ide_docs_examples/


sequencer-client: replace type wrapper by extension trait

This commit replaces the newtype wrapper around tendermint_rpc::HttpClient with an extension trait SequencerClientExt: tendermint_rpc::client::Client that is implemented for both HttpClient and WebsocketClient. The actual impls are behind http and websocket feature gates, respectively.
In addition, this commit removes the dynamic errors in favor of typed errors that report on which underlying RPC failed, if deserialization of the abci query response payload failed, or if a sequencer query response other than the expected one was received.
To leave deserialization logic as an implementatian detail, the underlying error in case of failure is not accessible (outside of type erased calls to std::error::Error::source).

Changes since the PR was approved:

added a crate level doc comment with a code example
added a job running doc tests


Handle edge case when method agrument is Stripe::Token.

Stripe API allows to create customer via passing in source Stripe::Token, not just token id. For example,
token = Stripe::Token.create(
        card: { number: card_number, exp_month: exp_month, exp_year:  exp_year, cvc: cvc }
      )
Stripe::Customer.create(
      source: token,
      email<EMAIL_ADDRESS>      plan:   'stripe_plan_id'
    )

In that case, will be raised Stripe::InvalidRequestError from stripe_ruby_mock gem.

looks good. Please, add a live test for that https://github.com/rebelidealist/stripe-ruby-mock#live-testing

@alexmamonchik, I can't configure rspec in live mode and reproduce build from Travis on local environments. The same result bundle exec rspec -t live command, independently my changes accepted or didn't. Tried for 2.0.0 and 2.3.0 rubies. Could you to advise something?
Finished in 4 minutes 36.8 seconds (files took 0.34832 seconds to load)
61 examples, 9 failures, 1 pending

Failed examples:

rspec ./spec/shared_stripe_examples/validation_examples.rb:16 # StripeMock::Instance behaves like Card API retrieval and deletion with recipients runs a luhn check for charges
rspec ./spec/shared_stripe_examples/card_examples.rb:182 # StripeMock::Instance behaves like Card API retrieval and deletion with recipients can retrieve all recipient's cards
rspec ./spec/shared_stripe_examples/card_examples.rb:187 # StripeMock::Instance behaves like Card API retrieval and deletion with recipients deletes a recipient card
rspec ./spec/shared_stripe_examples/card_examples.rb:193 # StripeMock::Instance behaves like Card API retrieval and deletion with recipients deletes a recipient card then set the default_card to nil
rspec ./spec/shared_stripe_examples/card_examples.rb:203 # StripeMock::Instance behaves like Card API retrieval and deletion with recipients deletion when the recipient has two cards has just one card anymore
rspec ./spec/shared_stripe_examples/card_examples.rb:210 # StripeMock::Instance behaves like Card API retrieval and deletion with recipients deletion when the recipient has two cards sets the default_card id to the last card remaining id
rspec ./spec/shared_stripe_examples/recipient_examples.rb:97 # StripeMock::Instance behaves like Recipient API Errors throws an error when the customer does not have the retrieving card id
rspec ./spec/shared_stripe_examples/transfer_examples.rb:67 # StripeMock::Instance behaves like Transfer API when amount is not integer
rspec ./spec/shared_stripe_examples/country_specs_examples.rb:12 # StripeMock::Instance behaves like Country Spec API retrieve country cannot retrieve a stripe country that doesn't exist

please, get last commits from master


Rendering issue

I push the LocationPicker into a NavigationController

same problem here, just copied and pasted the sample from README.md inside the button event
my deployment target is 9.0

If you really want to have the searchBar inside the navigationBar on iOS 11 you could fix the issue like this:
extendedLayoutIncludesOpaqueBars = true

However, I'd suggest to do it iOS 11 style, so here's a PR fixing the issue: #46


vercel deployment

Is your feature request related to a problem?
add vercel deployment button and feature
Describe the solution you'd like
add vercel deployment button and feature
Additional context
No response

The vercel deployment button is on the readme page


Safari - "Paste as plain text" command is not in the context menu (right button click)

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to a chat app that supports Markdown (For example: Slack)
Copy the text with markdown and navigate back to NewDot
Paste this text without any markdown by right clicking and selecting "Paste as plain text"
Comment: For Safari only. Chrome and Desktop App have such a command.

Expected Result:
Copied text can be pasted into the compose box using "Paste as plain text" from the context menu (right button click)
Actual Result:
"Paste as plain text" command is not in the context menu (right button click)
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/196770913-6ac59248-ef33-461e-99a2-7cc5c1ada7ac.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

@kbecciv Are you saying that "Paste as plain text" used to be an option but no longer appears?

Bump @kbecciv

Double checking..

@deetergp
See the difference. on Safari you can only PASTE. There is no other option

@mvtglobally I guess what I am trying to figure out is, did we have this in Safari at one point but lost it because a bug was introduced, or did we never have it and are just noticing it now?

I'm closing this as not valuable. Nobody can say that it was a thing that existed then went away, so it isn't really a bug.


Combine evolution families logically

Reported by Eevee on 2010/07/18 18:23:21 +0000 · Migrated from Redmine issue 293

Phione and Manaphy should be baseform siblings, with some note that only Phione actually comes from breeding.
Both Nidoran families should be parallel and together, with a note that either Nidoran can result.
Volbeat and Illumise should be siblings, similar to Nidoran.
Unfortunately! Volbeat and Illumise have opposite EXP growth. This requires moving the growth rate into pokemon.
Somewhat related, I believe Shedinja should actually evolve from Ninjask. The game clones after Ninjask evolves, so Shedinja can actually learn moves only Ninjask can.
Redmine metadata:
Updated on: 2011/04/29 15:10:50 +0000
Start date: 2010/07/18
Relations:
    relates #579

Comment by Zhorken from 2010/10/08 20:11:44 +0000
Possibly the Latis, too?

Somewhat related, I believe Shedinja should actually evolve from Ninjask. The game clones after Ninjask evolves, so Shedinja can actually learn moves only Ninjask can.

Only levelup moves, though, and only from one level. It’s more like it evolves into both at once, and anything it learns in the process, it learns both ways.

Comment by En-Cu-Kou from 2011/04/27 15:00:19 +0000
I want to find Ninjask when looking for final evolutions.

Comment by Eevee from 2011/04/28 06:44:54 +0000
Target version: — ⇨ 2011 Q2
Assignee ⇨ Eevee

Comment by En-Cu-Kou from 2011/04/29 15:10:50 +0000
I’m moving exp_growth to Pokemon as part of #579 (http://bugs.veekun.com/issues/579)

Possibly the Latis, too?

There data gives no reason for that. Why the Latis, and not also the legendary trios?

Now all that's left is adding the notes. And updating the UI accordingly. (The section in spline-pokedex should probably be named Family instead of Evolution.)


Some typo and a little improvement

The content is very good. Thanks for make the hard work.

Your right with generates word  :-)
I hope is right now.

Thanks!


Implement mapOr()

This is a useful composition mechanism when we want to both provide a
default value or map an existing value in the same operation.

I'll actually add some README content for this as well


termui.Close doesn't clean up everything and cause issue to re-init again after two or three times

I noticed after two or three times try init and close then the init doesn't work properly! looks close doesn't revert everything as expected. I tried termbox-go directly (init and close sequentially) and it worked properly!
If you want to duplicate this issue try /_example/dashboard.go as below:
change main func to test func
create new main func with multiple test function:
func main() {      for i := 0; i < 10; i++ {          test()      } }
Once you press "q" to see the next dashboard, you can see less than three instead of 10 as the rest will be gone!

I have same issue when I move all termui code to separate package.

So I've created a pull request that solves this. It's not the cleanest but hey, it does the job.

Closed with merge of #147