text:
Fork or not to fork

Hi @brandonkboswell , I was looking for a plugin for doing weekly/monthly reviews and this is the closest I've found. However, my approach to doing weekly/monthly reviews is quite different. I like to do process/digest daily notes into weekly notes, then from weekly notes to monthly notes, and then from monthly notes to yearly notes. I don't want to process each individual note based on its creation date.
I would like to have two commands 1. start review and 2. mark processed.
Instead of explaining the mechanics I will illustrate you how it should work:
￼Green means the processed note,
Start review command

Mark processed command

The processed state is stored in front matter field: processed: true/false both in daily notes, weekly notes, monthly notes and yearly notes.
Is it something you would like to see in your plugin or should I fork it to my own?

👋 Hey @stanbar. Your approach is still very much in the spirit of this plugin, and is very welcome here! I did the initial version based on dates only because it was the simplest solution that met my basic use case.  Let me know if you have any questions or need anything from me.

authors: brandonkboswell stanbar

repo: brandonkboswell/weekly-review


text:
Python Package

Hi there,
thank you for this cool project! Just a question: would you ever release a Python version of Qrank?
It would be very cool to have a simple package that one can install in order to automatically collect all statistics
for a bulk of wikidata entities :)
Thank you again.
Best,
Giorgio

For a Python example, have a look at the data pipeline for this map of castles in Switzerland; it uses QRank for choosing which castles get displayed at what zoom level. Specifically, check out fetch_wikidata_qrank() and read_wikidata_qrank(). Were you looking for something like this?

Dear Brawer,
first of all, thank you very much for your quick answer. I looked into the source code of the project that displays the Swiss castles according to their popularity on Wikipedia. It is interesting and close to what I meant, nonetheless it is not exactly what I would need.
I think it would be cool to extend the pageview wikipedia APIs in order to fetch data using the wikidata IDs regardeless of the language. This is more or less what already happens with this functionality, but no APIs are available for performing such request. Moreover, on that interface, the user needs to specify the language and the string associated to the page he or she is interested in.
What about a simple python module that automatically retrieves all the wikipedia statistics for a specific wikidata entity? For example, given the entity Q1234, a date range, and a granularity, I want to know the statistics for all the related wikipedia pages.
I think that your tool could be easily extended to do that, right?  I could help with the implementation :)
Best and thanks again,
Giorgio

source: gharchive/issue

authors: GiorgioBarnabo brawer

repo: brawer/wikidata-qrank

license: MIT

license_type: permissive

license_source: github-api


text:
PermissionError: [Errno 1] Operation not permitted

Hello,
When I try to connect the Bento client to the Bento server over Tor with the command torify ./test_hello_world.py, I get the following error:

Do you know what causes it? What can I do to fix it?
Thank you very much in advance.

Hello,
The tor network doesn't allow connections to and from your computer. Because of this, the Bento server and client cannot be run on the same computer while using torify. One solution is to run the Bento server on a different computer than the client. If that isn't possible, then you could try to use the third answer from this tor stack exchange post: https://tor.stackexchange.com/questions/11994/how-to-access-local-host-through-tor-browser

repo: breakerspace/bento


text:
Invalid configuration value provided for "token". Expected Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable, but got string

Error
Invalid configuration value provided for "token". Expected Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable, but got string(872)
This is similar to
https://github.com/aws/aws-sdk-php/issues/2567
https://github.com/brefphp/bref/issues/1330 (closed, tried the provided answer without success)
I'm using a serverless.yml SQS configuration similar to #103 and https://bref.sh/docs/laravel/queues.
provider:
    region: eu-central-1
    environment:
        QUEUE_CONNECTION: sqs
        SQS_QUEUE: ${construct:jobs.queueUrl}
        EVENT_PROJECTOR_QUEUE_NAME: sqs
        SQS_PREFIX: https://sqs.eu-central-1.amazonaws.com/704985899778
...
constructs:
  jobs:
    type: queue
    worker:
        handler: Bref\LaravelBridge\Queue\QueueHandler
        runtime: php-81
        timeout: 720 # seconds

I've also tried to use the version in getting-started/serverless.yml that uses iam and resources.Queue to build the infrastructure instead.
In both cases I see the queue created correctly in SQS but when I try to dispatch anything (events or jobs) I receive
Invalid configuration value provided for "token". Expected Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable, but got string(872)
I've tried to add this line in queue.sqs config to no avail.
'token' => new Aws\Token\Token(env('AWS_SESSION_TOKEN')),

My configuration
queue.php
'sqs' => [
            'driver' => 'sqs',
            'key' => env('AWS_ACCESS_KEY_ID'),
            'secret' => env('AWS_SECRET_ACCESS_KEY'),
            'prefix' => env('SQS_PREFIX', 'https://sqs.eu-central-1.amazonaws.com/704985899778'),
            'queue' => env('SQS_QUEUE', 'default'),
            'suffix' => env('SQS_SUFFIX'),
            'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
            'after_commit' => false,
],

composer installed packages
aws/aws-sdk-php                      3.296.6 #I also tried to downgrade to 3.237.1
bref/laravel-bridge                  2.2.1
laravel/framework                    v10.41.0

Full serverless.yml for reference
service: laravel

provider:
    name: aws
    region: eu-central-1
    environment:
        APP_NAME: Example
        APP_ENV: production # Or use ${sls:stage} if you want the environment to match the stage
        APP_URL: https://www.example.com
        APP_KEY: ${ssm:/example-app/app_key}
        DB_CONNECTION: planetscale
        DB_HOST: aws.connect.psdb.cloud
        DB_PORT: 3306
        DB_DATABASE: ${ssm:/example-app/db_planetscale_database}
        DB_USERNAME: ${ssm:/example-app/db_planetscale_username}
        DB_PASSWORD: ${ssm:/example-app/db_planetscale_password}
        MYSQL_ATTR_SSL_CA: /opt/bref/ssl/cert.pem
        LOG_CHANNEL: stderr
        FILESYSTEM_PUBLIC_DISK: s3
        FILESYSTEM_DISK: s3
        AWS_BUCKET: !Ref PublicS3
        AWS_USE_PATH_STYLE_ENDPOINT: false
        MAIL_FROM_ADDRESS: "hello@example.it"
        MAIL_FROM_NAME: "Example From"
        MAIL_DRIVER: postmark_transactional
        MAIL_MAILER: postmark_transactional
        POSTMARK_TOKEN: ${ssm:/example-app/postmark_token}
        POSTMARK_MESSAGE_STREAM_TRANSACTIONAL_ID: outbound
        QUEUE_CONNECTION: sqs
        SQS_QUEUE: ${construct:jobs.queueUrl}
        EVENT_PROJECTOR_QUEUE_NAME: sqs
        SQS_PREFIX: https://sqs.eu-central-1.amazonaws.com/my-id
    iam:
        role:
            statements:
                -   Effect: Allow
                    Action: s3:*
                    Resource:
                        - !Sub '${PublicS3.Arn}'
                        - !Sub '${PublicS3.Arn}/*'

resources:
    Resources:
        PublicS3:
            Type: AWS::S3::Bucket
            Properties:
                BucketName: my-bucket

package:
    # Files and directories to exclude from deployment
    patterns:
        - '!node_modules/**'
        - '!public/storage'
        - '!resources/assets/**'
        - '!storage/**'
        - '!tests/**'

functions:

    # This function runs the Laravel website/API
    web:
        handler: public/index.php
        runtime: php-82-fpm
        layers:
            - ${bref-extra:gd-php-82}
        timeout: 28 # in seconds (API Gateway has a timeout of 29 seconds)
        events:
            - httpApi: '*'

    # This function lets us run artisan commands in Lambda
    artisan:
        handler: artisan
        runtime: php-82-console
        timeout: 720 # in seconds
        # Uncomment to also run the scheduler every minute
        events:
           - schedule:
                 rate: rate(1 minute)
                 input: '"schedule:run"'

plugins:
    - ./vendor/bref/bref
    - serverless-lift
    - ./vendor/bref/extra-php-extensions

constructs:
  website:
    type: server-side-website
    domain: app.example.it
    certificate: cert-arn
    assets:
      '/build/assets/*': public/build/assets/
      '/favicon.ico': public/favicon.ico
      '/robots.txt': public/robots.txt
  jobs:
    type: queue
    worker:
        handler: Bref\LaravelBridge\Queue\QueueHandler
        runtime: php-81
        timeout: 720 # seconds

Hi, as far as I know, this is indeed a variant of this bug: https://github.com/laravel/framework/pull/44979
Everything looks ok in your config, except you don't need to define SQS_PREFIX (I'd remove it completely).
Also are you sure the error is related to SQS and not S3? (because in most reports people had problems with the S3 config).
Are you also 100% sure the Laravel-Bref bridge's service provider is correctly registered? It should automatically set up the token:
https://github.com/brefphp/laravel-bridge/blob/master/src/BrefServiceProvider.php#L48-L51
Maybe you have a specific config that is not the default (e.g. a SQS connection not called sqs, or a S3 driver not called s3?)

Found the issue. I had vapor in my packages due to a previous attempt on vapor. For some reason, it intercepts the SQS connection and does not indeed have the fix that removes token from the configuration used to build the SqsClient.
Closing this one. Thanks!

authors: giulioprinaricotti mnapoli

repo: brefphp/laravel-bridge


text:
No character constant output?

Hi,
When using FortranRecordWriter, I can't seem to find a way to include Character Constant Outputs.
Is this feature supported?

You can use the apotrophe edit descriptor, e.g.
(F8.2, ' Is greater than ', F8.2)

repo: brendanarnold/py-fortranformat


text:
Add repository.yaml

I suppose this fixes #8, but I haven't actually tested because I don't know how.

As https://github.com/brenner-tobias/addon-cloudflared/issues/8#issuecomment-1008364584 this should not be needed.

source: gharchive/pull-request

repo: brenner-tobias/addon-cloudflared


text:
Integrate with Spotlight Search

See this post: https://agostini.tech/2019/04/22/using-nsuseractivity-for-spotlight-search/

That is very cool. Let’s do it.

authors: brentsimmons vincode-io

repo: brentsimmons/NetNewsWire


text:
More of a question about multi-tenancy database

I noticed on https://stackoverflow.com/questions/43078796/connection-does-not-correctly-set-catalog-using-hikaricp you mentioned that setCatalog() didn't really work and causes mysql to dump the connections and to instead use a map of pools and that it could handle thousands of pools. I commented on the answer saying that setCatalog() worked for me in testing but I do prefer using a map of collections my only concern is that it could be quite expensive. I do remember reading the article you are referenced but I can't find it any more. Do you remember the link and/or details. Also I assume the default connection values have to be adjusted so that connections are not left idle after they timeout and so on. This article for example was interesting but didn't go into any performance issues and/or setting recommendations.
This Stackoverflow question also had some interesting discussions: https://stackoverflow.com/questions/52728639/connection-pooling-in-multi-tenant-app-shared-pool-vs-pool-per-tenant but kind of suggested not to do a map of connection pools.
Any help on this would be greatly appreciated.

Found this interesting data about setting up a mysql database with very high connection limits: https://www.percona.com/blog/mysql-challenge-100k-connections/

repo: brettwooldridge/HikariCP

license_source: bigquery


text:
BitSet.valueOf(), toByteArray() similar methods

Hi,
Would be great if we've something like BitSet.valueOf() & 'BitSet.toByteArray()' in SparseBitSet too. Currently it is not direct to initialise SparseBitSet from byte[]

valueOf can be implemented like below: (byte[] to bit extraction logic taken from http://stackoverflow.com/a/1034513/340290)
public static SparseBitSet valueOf(byte[] bytes) {
	SparseBitSet sparseBitSet = new SparseBitSet();
	int j = 0;
	for (byte b : bytes) {
		for (int mask = 0x01; mask != 0x100; mask <<= 1) {
			if((b & mask) != 0) {
				sparseBitSet.set(j);
			}
			j++;
		}
	}

	return sparseBitSet;
}

I did a simple benchmark to see which faster among BitSet & SparseBitSet to create from byte[].
SparseBitSet is taking ~10 times more time than BitSet.valueOf(). I m not sure if this is due to the above implementation of SparseBitSet.valueOf().
Can we improve this? Below is the very rudementary main() for testing:
public static void main(String[] args) throws DecoderException {
	int[] intArray = new int[] {0,1,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,1,1,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,1,1,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,1,1,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0,0,0,0,0,1,1,1,0,0,1,1,1,1,1,0,0,1,0,1,0,1,0,0,0,1,1,0,1,1,1,0,1,0};

	BitSet bitSet = new BitSet();
	SparseBitSet sparseBitSet = new SparseBitSet();

	for(int i = 0; i < intArray.length; i++) {
		bitSet.set(i, intArray[i] == 1);
		sparseBitSet.set(i, intArray[i] == 1);
	}

	System.out.println("BitSet original      : " + bitSet);
	System.out.println("SparseBitSet original: " + sparseBitSet);

	String hexStr = Hex.encodeHexString(bitSet.toByteArray()); // BitSet --> Hex
	byte[] decodeHex = Hex.decodeHex(hexStr.toCharArray()); // Hex -> byte[]

	System.out.println("SparseBitSet decoded : " + sparseBitSetValueOf(decodeHex));

	// BitSet Hex
	long start1 = System.currentTimeMillis();
	for(int i = 0; i < 1000000; i++) {
		BitSet.valueOf(decodeHex);
	}
	long end1 = System.currentTimeMillis();
	System.out.println("BitSet Hex total time: " + (end1 - start1));

	// SparseBitSet Hex
	long start3 = System.currentTimeMillis();
	for(int i = 0; i < 1000000; i++) {
		sparseBitSetValueOf(decodeHex);
	}
	long end3 = System.currentTimeMillis();
	System.out.println("SparseBitSet Hex total time: " + (end3 - start3));

}

@manikantag
SparseBitSet is serializable. Why don't you serialize and deserialize it instead?

authors: lemire manikantag

repo: brettwooldridge/SparseBitSet


text:
Addressed several issues and refreshed code to work with Node 16 LTS

Updated travis to use Node 16 LTS
Fixed/updated tests throughout the project
Addressed current security vulnerabilities by updating all packages to latest
All tests are passing now - https://app.travis-ci.com/github/atul898/node-sql
Logo: https://app.travis-ci.com/atul898/node-sql.svg?branch=master

Going to close this pull request, since I published this change here - https://github.com/atul898/node-sql and we can use it from there for our project. If anyone else needs to address the current security vulnerabilities when using this package with node 16 and above, you are welcome to use my changes.

repo: brianc/node-sql

license: mit


text:
Update cents to_string to take negative values

Update cents.to_string to take negative values.
This allows us to have the app eventually allow users to cash out more than they bought in, which can happen when

Winners attempt to cash out before all users have bought in
There has been an user error in computing cash outs.

Hello @MatthewUng! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/game/route.py:

Line 336:80: E501 line too long (125 > 79 characters)

In the file src/game/validation.py:

Line 11:80: E501 line too long (135 > 79 characters)

In the file src/utils/cents.py:

Line 3:1: E302 expected 2 blank lines, found 1
Line 5:80: W291 trailing whitespace
Line 18:80: W291 trailing whitespace
Line 23:19: E701 multiple statements on one line (colon)
Line 28:80: W291 trailing whitespace
Line 39:23: E701 multiple statements on one line (colon)

repo: brianhang/pokerpals


text:
Make failed with exit code 2 (Windows XP, ruby 1.9.3)

Another failure to build the C extension
gem install charlock_holmes -- --with-icu-dir=C:/icu --with-icui18nlib=icuin --with-icudatalib=icudt   --with-opt-dir=C:/temp/zlib-1.2.3-lib --with-opt-lib=C:/temp/zlib-1.2.3-lib/lib --with-opt-include==C:/temp/zlib-1.2.3-lib/include
Temporarily enhancing PATH to include DevKit...
Building native extensions with: '--with-icu-dir=C:/icu --with-icui18nlib=icuin
--with-icudatalib=icudt --with-opt-dir=C:/temp/zlib-1.2.3-lib --with-opt-lib=C:/temp/zlib-1.2.3-lib/lib --with-opt-include==C:/temp/zlib-1.2.3-lib/include'
This could take a while...
ERROR:  Error installing charlock_holmes:
        ERROR: Failed to build gem native extension.

    C:/Ruby193/bin/ruby.exe extconf.rb --with-icu-dir=C:/icu --with-icui18nlib=icuin --with-icudatalib=icudt --with-opt-dir=C:/temp/zlib-1.2.3-lib --with-opt-lib=C:/temp/zlib-1.2.3-lib/lib --with-opt-include==C:/temp/zlib-1.2.3-lib/include
checking for main() in -licuin... yes
checking for main() in -licuin... yes
checking for unicode/ucnv.h... yes
checking for main() in -lz... yes
checking for main() in -licuuc... yes
checking for main() in -licudt... yes
creating Makefile

make  clean

make
generating charlock_holmes-i386-mingw32.def
compiling converter.c
common.h:23:14: warning: 'charlock_new_str' defined but not used
common.h:32:14: warning: 'charlock_new_str2' defined but not used
compiling encoding_detector.c
common.h:14:14: warning: 'charlock_new_enc_str' defined but not used
compiling ext.c
common.h:14:14: warning: 'charlock_new_enc_str' defined but not used
common.h:23:14: warning: 'charlock_new_str' defined but not used
common.h:32:14: warning: 'charlock_new_str2' defined but not used
compiling transliterator.cpp
cc1plus.exe: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus.exe: warning: command line option "-Wimplicit-function-declaration" is valid for C/ObjC but not for C++
common.h:14:14: warning: 'VALUE charlock_new_enc_str(const char*, size_t, void*)' defined but not used
common.h:32:14: warning: 'VALUE charlock_new_str2(const char*)' defined but not
used
linking shared-object charlock_holmes/charlock_holmes.so
transliterator.o: In function `rb_transliterator_id_list':
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:47: undefined reference to `icu_55::Transliterator::getAvailableIDs(UErrorCode&)'
transliterator.o: In function `rb_transliterator_transliterate':
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:101: undefined reference to `icu_55::UnicodeString::UnicodeString(char const*, int)'
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:101: undefined reference to `icu_55::Transliterator::createInstance(icu_55::UnicodeString const&, UTransDirection, UParseError&, UErrorCode&)'
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:101: undefined reference to `icu_55::UnicodeString::~UnicodeString()'
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:106: undefined reference to `icu_55::UMemory::operator new(unsigned int)'
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:106: undefined reference to `icu_55::UnicodeString::UnicodeString(char const*, int)'
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:109: undefined reference to `icu_55::UnicodeString::toUTF8(icu_55::ByteSink&) const'
transliterator.o: In function `~StringByteSink':
C:/icu/include/unicode/bytestream.h:231: undefined reference to `icu_55::ByteSink::~ByteSink()'
C:/icu/include/unicode/bytestream.h:231: undefined reference to `icu_55::ByteSink::~ByteSink()'
transliterator.o: In function `rb_transliterator_transliterate':
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:106: undefined reference to `icu_55::UMemory::operator delete(void*)'
C:\Ruby193\lib\ruby\gems\1.9.1\gems\charlock_holmes-0.7.3\ext\charlock_holmes/transliterator.cpp:101: undefined reference to `icu_55::UnicodeString::~UnicodeString()'
transliterator.o: In function `~StringByteSink':
C:/icu/include/unicode/bytestream.h:231: undefined reference to `icu_55::ByteSink::~ByteSink()'
C:/icu/include/unicode/bytestream.h:231: undefined reference to `icu_55::ByteSink::~ByteSink()'
C:/icu/include/unicode/bytestream.h:231: undefined reference to `icu_55::UMemory::operator delete(void*)'
transliterator.o:transliterator.cpp:(.rdata$_ZTVN6icu_5514StringByteSinkISsEE[vtable for icu_55::StringByteSink<std::basic_string<char, std::char_traits<char>,
std::allocator<char> > >]+0x14): undefined reference to `icu_55::ByteSink::GetAppendBuffer(int, int, char*, int, int*)'
transliterator.o:transliterator.cpp:(.rdata$_ZTVN6icu_5514StringByteSinkISsEE[vtable for icu_55::StringByteSink<std::basic_string<char, std::char_traits<char>,
std::allocator<char> > >]+0x18): undefined reference to `icu_55::ByteSink::Flush()'
collect2: ld returned 1 exit status
make: *** [charlock_holmes.so] Error 1

make failed, exit code 2

Gem files will remain installed in C:/Ruby193/lib/ruby/gems/1.9.1/gems/charlock_holmes-0.7.3 for inspection.
Results logged to C:/Ruby193/lib/ruby/gems/1.9.1/extensions/x86-mingw32/1.9.1/charlock_holmes-0.7.3/gem_make.out

Wish I knew C

I have pretty much the same error for Windows 8, ICU 4.2, Ruby 1.9.3, and charlock_holmes 0.7.3.

authors: cezarykluczynski xiconet


text:
"Value cannot be null. Parameter name: element" when reflecting attributes

The following code works fine on dotnetfiddle but throws in Bridge/Deck.net:
https://dotnetfiddle.net/YYkcrU
https://deck.net/0dfa5632c667489768865c1b6633ca71
using System;
using System.Linq;

public class Program
{
	public static void Main()
	{
		var a = Status.Item1.GetAttribute<DisplayAttribute>();
	}

	public enum Status
	{
		[Display]
		Item1
	}

	class DisplayAttribute : Attribute
	{
	}
}

public static class EnumExtensions
{
	public static T GetAttribute<T>(this Enum value)
	where T : Attribute
	{
		return value
		.GetType()
		.GetField(value.ToString())
		.GetCustomAttributes(typeof(T), false)
		.FirstOrDefault()
		as T;
	}
}

The error is:

bridge.min.js?15.7.0.1:8 Uncaught
ctor {message: "Value cannot be null.↵Parameter name: element", innerException: null, errorStack: Error at ctor (https://deck.net/resources/js/bridge/bridge.min.js?15.7.0.1:8:63274) at ctor …, data: ctor, $initialized: function…}

I've tried adding [Reflectable] to both the enum and the attribute, but that doesn't seem to make any difference.
Is this a bug or do I need to do something differently?

The same issue
https://github.com/bridgedotnet/Bridge/issues/2622

authors: DanTup vladsch

repo: bridgedotnet/Bridge


text:
haml-lint Ruby gem issue

This is partly referring to #134:
I mentioned on Twitter to you that probably yanking all of that wasn't a good idea. By reading RubyGems naming guidelines I can see why this change was made.
However, by yanking all previous versions, including those with version number higher than currently available 0.0.3, you broke integration with RubyGems, because when you try
gem install haml-lint

it will still try to fetch 0.13.0[1], because it's the latest version on record. RubyGems assumes you will update your gem's version incrementally.
Quick-fix for this would be to release 1.0.0 of haml-lint alias gem. So, although haml_lint is the recommended way of installing this gem, maybe haml-lint should not break current projects just because it has a hyphen in the name?

[1]

$ gem install haml-lint
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    bad response Not Found 404 (https://rubygems.global.ssl.fastly.net/quick/Marshal.4.8/haml-lint-0.13.0.gemspec.rz)

Thanks for your feedback, @Holek.
You're correct in that yanking the gem was probably not the best decision, though to be fair the behavior exhibited by RubyGems in this case is rather unexpected. If a gem is yanked one would hope it a client wouldn't attempt to install it (or would at least get a better error message saying said gem was yanked).
I've pushed a new version which should solve this issue. Thanks again!

authors: Holek sds

repo: brigade/haml-lint


text:
Overcommmit is confused when two versions of overcommit  is installed

When you have two versions of overcommit, it gets confused and issues #499 happens
Steps to reproduce:
Install overcommit-0.44.0 && overcommit-0.45.0
Go to any repo. with overcommit hooks and try doing any operations which has hook on it.
workaround
keep only one version of overcomit
what should happen
Instead of #499, we show a helpful warning that you have two version of overcommit and uninstall one of them.

This is not great since I use overcommit with multiple projects and the versions are not always the same in my Gemfile.lock

Closing due to age. If this is a still a problem, would appreciate a pull request fixing it!

authors: HarlemSquirrel electron0zero sds

repo: brigade/overcommit


text:
Update example for JSON formatter in the README

The JSON formatter examples does not have column, length and litner fields in the README. However, those fields are included actually.
For example:
$ scss-lint test.scss --format=JSON
{
  "test.scss": [
    {
      "line": 2,
      "column": 1,
      "length": 1,
      "severity": "warning",
      "reason": "Declaration should be terminated by a semicolon",
      "linter": "TrailingSemicolon"
    },
    {
      "line": 2,
      "column": 10,
      "length": 4,
      "severity": "warning",
      "reason": "Color literals like `#111` should only be used in variable declarations; they should be referred to via variable everywhere else.",
      "linter": "ColorVariable"
    }
  ]
}

This change adds those fields to the example.

Thanks for helping keep our documentation up to date, @pocke!

authors: pocke sds

repo: brigade/scss-lint


text:
Wrap nested elements

Changes proposed in this Pull Request:

Revisit Threeliner and wrap nested elements with styled

Can you use the Box component in place of div for the styled components.

do we have to do anything with all this webkit stuff that's not being used?

I don't think so; all those crossed-off styles seem to have duplicated equivalents applied already.

repo: brightlayer-ui/react-component-library


text:
Rain duration stuck

Home Assistant Version?
Home Assistant 2023.6.3
Add-On or Self Hosted?
HA Supervised (Add-On)
Weatherflow2MQTT version?
3.1.6
What happened?

As you can see from the pictures there is a discrepancy between the output of the Weatherflow App and the weather flow integration.
I have restarted bits the integration as well as the HA entirely without succes.
Relevant log output
No response

This issue solved itself after 0000 hours or so it seems. I do remember having an sql database update and maybe that caused I glitch in the days performance. It does make my data incorrect though.


text:
Can't see blog posts

Hi,
I downloaded the theme, installed pygments, added jekyll-paginate plugin and served without errors, but I don't see any posts.. I see everything else, but the posts in _posts aren't loading.
Any tips?

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

authors: earlyraven hgaronfolo


text:
compiler.Colset can't distinguish .a.b from .["a.b"]

@mccanne pointed out to me that I broke compiler.Colset's ability to distinguish .a.b (a top-level record named a with a field named b) from .["a.b"] (a top-level field named a.b) in #1845.

Maybe we can just get rid of compiler.Colset... it seems to have been added prematurely.

If Colset is used only by computeColumns, maybe we can just get rid of both as they're unused (looks like they were introduced prematurely).

In discussing this one with @mccanne he indicated the code related to this gone and so this issue is no longer relevant. He intends to add a final comment here and close it.

#1916 removed compiler.Colset.

authors: henridf nwt philrz

repo: brimsec/zq


text:
test script fails because ShiftFasta command is missing

I'm trying to run the short reads MicrobialGenomePipeline wdl with the supplied inputs.json file with the command:
miniwdl run -i GATK-for-Microbes/wdl/shortReads/inputs.json GATK-for-Microbes/wdl/shortReads/MicrobialGenomePipeline.wdl
but I get an error on the shift fasta step. I tried using the inputs.json file exactly as provided in this repo and also with the two lines that override the default GATK jar file removed and the error I get is the same. In both cases, the error I get is "A USER ERROR has occurred: 'ShiftFasta' is not a valid command".
I've attached the stderr.txt file that's output by call-ShiftReference when I run the script using the inputs.json exactly as provided - stderr.txt
Do I need to update the docker image provided here or the version of GATK that's being pointed to by the inputs.json? Thanks for your help!

I'm having what might be another versioning issue. The --microbial-mode option used for filtering in the shortReads/MicrobialGenomePipeline.wdl doesn't exist in the version of GATK included in the default docker, in the version of GATK selected in the example inputs.json file, or in the latest docker image at us.gcr.io/broad-gatk/gatk:4.2.1.0 (although documentation here suggests that is should). Is there a different version of GATK that I should be using in order to have access to this option? Thanks!

repo: broadinstitute/GATK-for-Microbes


text:
Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Stack trace:
Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at hu (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:365287)
    at gl (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:378458)
    at t.unstable_runWithPriority (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:479427)
    at Vo (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:323755)
    at yl (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:376318)
    at rl (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:372472)
    at https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:324046
    at t.unstable_runWithPriority (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:479427)
    at Vo (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:323755)
    at Ko (https://gnomad.broadinstitute.org/js/bundle-7af6653ae8e1da79ae84.js:2:323991)

Route: /gene/ENSG00000113140?dataset=gnomad_r2_1
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 Edg/107.0.1418.35

I'm currently unable to replicate this when I go to
https://gnomad.broadinstitute.org/gene/ENSG00000113140?dataset=gnomad_r2_1
Is this a recurring problem for you @MED-P0520, and/or did you do anything in particular when on that Gene page that gave this error/issue?

This issue is unable to be replicated, and appears to not be an ongoing thing. As such, this issue is being closed.

repo: broadinstitute/gnomad-browser


text:
Evaluate approaches for testing individual components headlessly

Enzyme?

@mattsolo1 @rileyhgrant I've been looking into this, and based largely on the recommendations in the React docs, I'd suggest that we stick to the simpler functionality of jest and jsdom when possible. We'll want to test more complex interactions as well, and where formerly we might have used Enzyme, the tool now favored for that is React Testing Library (where do they get these crazy names), see https://testing-library.com/docs/react-testing-library/intro. There is a lot of worthwhile stuff on that page and also https://reactjs.org/docs/testing.html.
Side note on end-to-end tests: contrary to my understanding of best practices, these docs also do recommend end-to-end tests against live hosts, as opposed to my preferred method of stubbing out e.g. the gnomAD API in our case. This made me think about whether my own position here was sound, and the conclusion I came to is that there's a time and place for both kinds of end-to-end test.
The chief advantage of stubbed end-to-end tests is that they're more reliable: they will throw fewer spurious test failures due to network glitches and other random factors that don't really have anything to do with the test. I've mentioned this before, but I really cannot overstate the pernicious effects of getting too comfortable with tests that sometimes pass and sometimes fail for no important reason.
The chief advantage of live end-to-end tests are that they are more realistic. No piece of software anywhere runs in isolation, and despite any efforts to the contrary, a prod environment in its full complexity can have significant differences from a dev or test environment, certainly enough to lead to nasty surprises at deploy time.
So my suggestion is this: for the purposes of our main test suite, the one that we run over and over again on our local machines, the one that gatekeeps PR approval, we stick to stubbed end-to-end tests. It would also be smart to develop some live ones, to come in somewhere later in the process, but here my thoughts are less fully formed. I'll mull that over some more over the weekend and perhaps we can all brainstorm a bit together next week, assuming that fits Matt's baby's plans.


text:
Unable to reach higher latency network servers after 2.5.0

Is this a bug or a feature request?
Bug
What did you expect?
I have deployed an infrastructure on AWS with a single lora-app-server in Europe and multiple lora-server all over the world configured for different LoRaWAN regions
What happened?
Starting version 2.5.0 all lora-server located in Asia Pacific are unreachable by lora-app-server.
If I go back to 2.4.1 everything works as expected
What version are your using?
2.5.0+
How can your issue be reproduced?
lora-app-server deployed on AWS Frankfurt datacenter
lora-server deployed on AWS Seoul datacenter
Could you share your log output?
time="2019-04-25T06:20:06Z" level=debug msg="sql query executed" args="[me 161]" duration=3.993231ms query="select count() from (\n\tselect 1\n\tfrom "user" u\n\tleft join organization_user ou\n\t\ton u.id = ou.user_id\n\tleft join organization o\n\t\ton o.id = ou.organization_id\n\tleft join gateway g\n\t\ton o.id = g.organization_id\n\tleft join application a\n\t\ton a.organization_id = o.id\n\tleft join service_profile sp\n\t\ton sp.organization_id = o.id\n\tleft join device_profile dp\n\t\ton dp.organization_id = o.id\n\tleft join network_server ns\n\t\ton ns.id = sp.network_server_id or ns.id = dp.network_server_id\n\tleft join device d\n\t\ton a.id = d.application_id\n\tleft join multicast_group mg\n\t\ton sp.service_profile_id = mg.service_profile_id\n where ((u.username = $1) and (u.is_active = true) and (u.is_admin = true)) or ((u.username = $1) and (u.is_active = true) and (ou.is_admin = true) and (ns.id = $2)) limit 1) count_only"
time="2019-04-25T06:20:06Z" level=debug msg="sql query executed" args="[161]" duration=1.003638ms query="select * from network_server where id = $1"
time="2019-04-25T06:20:06Z" level=warning msg="creating insecure network-server client" server="lora-cn1.xxx:xxx"
time="2019-04-25T06:20:06Z" level=debug msg="parsed scheme: """
time="2019-04-25T06:20:06Z" level=debug msg="scheme "" not registered, fallback to default scheme"
time="2019-04-25T06:20:06Z" level=debug msg="ccResolverWrapper: sending new addresses to cc: [{lora-cn1.xxx:xxx 0  }]"
time="2019-04-25T06:20:06Z" level=debug msg="ClientConn switching balancer to "pick_first""
time="2019-04-25T06:20:06Z" level=debug msg="Subchannel Connectivity change to CONNECTING"
time="2019-04-25T06:20:06Z" level=debug msg="pickfirstBalancer: HandleSubConnStateChange: 0xc0007ee690, CONNECTING"
time="2019-04-25T06:20:06Z" level=debug msg="sql query executed" args="[]" duration="727.798µs" query="\n\t\tselect\n\t\t\tg.\n\t\tfrom gateway g\n\t\tinner join network_server ns\n\t\t\ton ns.id = g.network_server_id\n\t\twhere\n\t\t\tns.gateway_discovery_enabled = true\n\t\t\tand g.ping = true\n\t\t\tand (g.last_ping_sent_at is null or g.last_ping_sent_at <= (now() - (interval '24 hours' / ns.gateway_discovery_interval)))\n\t\torder by last_ping_sent_at\n\t\tlimit 1\n\t\tfor update"
time="2019-04-25T06:20:07Z" level=debug msg="Subchannel Connectivity change to SHUTDOWN"
time="2019-04-25T06:20:07Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.NetworkServerService grpc.start_time="2019-04-25T06:20:06Z" grpc.time_ms=505.681 peer.address="127.0.0.1:43246" span.kind=server system=grpc
Version 2.4.1 will easily get:
time="2019-04-25T06:27:14Z" level=debug msg="pickfirstBalancer: HandleSubConnStateChange: 0xc0004a5f70, READY"
Version 2.5.0+ will fall to shutdown:
time="2019-04-25T06:20:07Z" level=debug msg="Subchannel Connectivity change to SHUTDOWN"

The above logs only contain info and debug logs. Could you provide the exact error?

I actually didn't manage to get much more, the only thing I could add is that I get a popup context deadline exceeded (code: 2) when I try to go on the Network Server page

Is this issue still relevant?

authors: Will-tm brocaar

repo: brocaar/lora-app-server


text:
serve configurability, or serve plug-ins, or watch, needed

I am using the broccoli to build a website where the production deployment files have names like /something.html, but things are configured such that they are served in production with URLs like /something.
I'm looking for any way to accomplish the same thing during development with broccoli.
As far as I can tell:

The plug-in orientation of broccoli does not extend to "serve", I cannot find any way to interpose my own code there to map URLs for example.
There are no settings to control how serve maps URLs/files works.
There is no "watch" feature, by which I could write the files as they need to change, then serve them with some other development HTTP server.

I think the combination of all these limitations blocks the thing I am hoping to do. My feature request is that any one of these three things be changed; I do not yet have enough of a sense of the ethos of broccoli to say which one is most reasonable.

You could use broccoli-timepiece to do the watch thing, for now.
In general, to achieve these sorts of things I'd expect people to use the Broccoli middleware programmatically, but I'm not sure if it's actually flexible enough at the moment to cleanly allow for the kind of URL mapping you want.

This has bothered me for a long time too, I'd rather see the serve stuff handled in a modular way with me being able to choose whatever serve plugin I want, or even choosing no serve plugin. Convention over configuration can still apply if you make the current behaviour a default with an easy way to disable/override. Having to use tools like broccoli a timepiece to remove the serving part doesn't sit well with me.

authors: joliss kylecordes ohjames

repo: broccolijs/broccoli


text:
Fix performance

Fix discogssyncer and MasterMote-pass

Don't care about discogsyncer any more

repo: brotherlogic/discogssyncer


text:
LAST_INSERT_ID Problem on FiveM Server vRP Framework

Hellp, I have a really big problem with mysql-async for FiveM with vRP framework, when someone connects to the server the LAST_INSERT_ID doesn't work it gives nil value and it says this error
[ERROR] [MySQL] [vrp] An error happens on MySQL for query "INSERT INTO vrp_user_ids(identifier,user_id) VALUES('steam:11000010856762b',@user_id)": ER_BAD_NULL_ERROR: Column 'user_id' cannot be null
how can I fix LAST_INSERT_ID ? please help !

You're not providing the user_id to the mysql statement.

Can you please show me how to provide the user_id to the mysql statement? Please i have searched for ages to fix it

repo: brouznouf/fivem-mysql-async


text:
Pass in default functions

Describe the solution you'd like
The current default components just print to console. This could be changed to allow users to pass in their desired functions, and these are routed down to the components. The component interfaces would need to be updated to accommodate this change,. This would allow some users to use the component OOTB with zero customization if they don't want to create their own components.
This also provides a uniform way to deal with behavior for people who do want to create custom components.

Additional parameters have been added to easily override the default functions when clicking on events or the more events indicator


text:
Book

As funções estão prontas de acordo com o Livro.h

Código revisado e adicionado a branch principal para melhorias e continuação da implementação.


text:
Help! Exception while running as Jar

Exception sending context initialized event to listener instance of class org.brutusin.rpc.RpcInitListener
java.lang.NullPointerException
at org.brutusin.rpc.RpcInitListener.initWebsocketRpcRuntime(RpcInitListener.java:75)
at org.brutusin.rpc.RpcInitListener.contextInitialized(RpcInitListener.java:44)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4738)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5181)

Please, attach your pom file

4.0.0
com.navinfo.had
rpc
0.0.1
jar
convesion-service
http://maven.apache.org

UTF-8

junit
junit
3.8.1
test

org.brutusin
rpc
1.1.0

com.navinfo.had
mif-engine
0.0.1

org.apache.maven.plugins
maven-shade-plugin
1.2.1

package

shade

org.brutusin.rpc.Main

`
4.0.0
com.navinfo.had
rpc
0.0.1
jar
convesion-service
http://maven.apache.org

UTF-8

junit
junit
3.8.1
test

org.brutusin
rpc
1.1.0

com.navinfo.had
mif-engine
0.0.1

org.apache.maven.plugins
maven-shade-plugin
1.2.1

package

shade

org.brutusin.rpc.Main

`

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
 <modelVersion>4.0.0</modelVersion>
<groupId>com.navinfo.had</groupId>
<artifactId>rpc</artifactId>
<version>0.0.1</version>
 <packaging>jar</packaging>
<name>convesion-service</name>
 <url>http://maven.apache.org</url>
 <properties>
 <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
 </properties>
 <dependencies>
 <dependency>
 <groupId>junit</groupId>
 <artifactId>junit</artifactId>
  <version>3.8.1</version>
  <scope>test</scope>
 </dependency>
 <dependency>
<groupId>org.brutusin</groupId>
<artifactId>rpc</artifactId>
<version>1.1.0</version>
</dependency>
 <dependency>
<groupId>com.navinfo.had</groupId>
<artifactId>mif-engine</artifactId>
<version>0.0.1</version>
</dependency>
 </dependencies>
 <build>
 <plugins>
 <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
 <version>1.2.1</version>
<executions>
<execution>
 <phase>package</phase>
<goals>
 <goal>shade</goal>
</goals>
<configuration>
 <transformers>
<transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
 <mainClass>org.brutusin.rpc.Main</mainClass>
</transformer>
 </transformers>
</configuration>
 </execution>
</executions>
</plugin>
</plugins>
</build>
</project>

Hi, there were several issues with your project:

Your where using a decontinued artifact id (org.brutusin:rpc)
When shading, you need to transform service provider manifests in order to not lose information (there is a name collision)

Try this out:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>com.navinfo.had</groupId>
    <artifactId>rpc</artifactId>
    <version>0.0.1</version>
    <packaging>jar</packaging>

    <name>convesion-service</name>
    <url>http://maven.apache.org</url>

    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <brutusin-rpc.version>1.2.6</brutusin-rpc.version>
        <json-provider-version>2.4.0</json-provider-version>
    </properties>

    <dependencies>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>3.8.1</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.brutusin</groupId>
            <artifactId>rpc-tomcat</artifactId>
            <version>${brutusin-rpc.version}</version>
            <scope>runtime</scope>
        </dependency>
        <dependency>
            <groupId>org.brutusin</groupId>
            <artifactId>rpc-impl</artifactId>
            <version>${brutusin-rpc.version}</version>
            <scope>runtime</scope>
        </dependency>
        <dependency>
            <groupId>org.brutusin</groupId>
            <artifactId>rpc-repo</artifactId>
            <version>${brutusin-rpc.version}</version>
            <scope>runtime</scope>
        </dependency>
        <dependency>
            <groupId>org.brutusin</groupId>
            <artifactId>json-provider</artifactId>
            <version>${json-provider-version}</version>
            <scope>runtime</scope>
        </dependency>

    </dependencies>

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-shade-plugin</artifactId>
                <version>2.4.3</version>
                <executions>
                    <execution>
                        <phase>package</phase>
                        <goals>
                            <goal>shade</goal>
                        </goals>
                        <configuration>
                            <transformers>
                                <transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
                                <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
                                    <mainClass>org.brutusin.rpc.Main</mainClass>
                                </transformer>
                            </transformers>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
</project>

One request:  if you like the project, please star it and share it.
Thanks!

Note: Just updated the pom to add dependency to org.brutusin:rpc-api

authors: doonewei idelvall

repo: brutusin/Brutusin-RPC


text:
hrecipe not being recognized

Google's rich snippet tool shows the hrecipe data: http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fwww.justapinch.com%2Frecipe%2Flovelucy%2Fmango-cobbler%2Ffruit-dessert&view=
but when going to http://www.justapinch.com/recipe/lovelucy/mango-cobbler/fruit-dessert  this extension doesn't show the hrecipe data.
This might be related to issue #5.

This seems to be working fine with the last version of the extension....

Yes it is working now. Thanks for the fix.

authors: gallotor toneplex

repo: bryckbost/michromeformats


text:
chore: rename Address Count to Host Addresses

What

Renamed Address Count: in the explain output to Host Addresses.

Why

To avoid any misunderstandings, the number indicates the count of host addresses as we subtract 2 to account for the base address and the broadcast address.

References

Closes #90

@mmourick what are your thoughts on this change?

I'm in favour of this change!

authors: TajangSec bschaatsbergen

repo: bschaatsbergen/cidr


text:
TravisCI: Update to latest configurations.

This updates the Go versions using when running the TravisCI integration tests to reflect the latest supported Go versions.
Also, the vet tool moved into the Go source tree as of Go 1.5.  Its previous location in the x/tools repo was deprecated at that time and has now been removed.
Finally, old tool path is no longer needed, so it has been removed.

OK

authors: davecgh jcvernaleo

repo: btcsuite/btcrpcclient

license: isc


text:
/opt/scripts/iobroker_startup.sh: Zeile 197: [: !=: Einstelliger (unärer) Operator erwartet.

get Error Message  "/opt/scripts/iobroker_startup.sh: Zeile 197: [: !=: Einstelliger (unärer) Operator erwartet." don't know what's going wrong. First time building the Container it runs without Error. On every build after the first build this Error occurs

Before I ask you questions about your setup and where the log is, please check this as written in readme.md:
"Important: If the folder you mount to /opt/iobroker in your container is placed on a mounted device, partition or other storage, the mountpoint on your host should NOT have the "noexec" flag activated. Otherwise you may get problems executing ioBroker inside the container!"
Regards,
André

noexec problem, thank you

authors: JoergKimmich buanet

repo: buanet/docker-iobroker


text:
How to stop iobroker

I have some troubles with your backup-script.
Sometimes it fails. That means that my Diskstation stucks in making a backup of the iobroker-container... and nothing helps: I have to restart my Diskstation by pressing on the on/off-button. And this hurts.
Suprisly the backup doesnt fail every day... only one or two times a week.
Anyway: I read that you suggest to stop iobroker before the backup start.
How can I do this.
You write:

Einfaches Script zum Stoppen von ioBroker.
Kann zum Beispiel aus ioBroker heraus aufgerufen werden um ioBroker zu stoppen.

Where do I have to put the script and how can I execute the script in iobroker??

Hi,
you can simply put the stop-script into your iobroker-folder (opt/iobroker) and call it with javascript from inside iobroker by using exec command:
   exec('/opt/iobroker/iobroker_stop.sh', function(err, stdout, stderr) {
    if (err) {
       log(stderr,'error');
       return;
        }
    });

BUT
I think stopping iobroker inside your container is not your problem.
Maybe there is a Problem with Docker on your DS. If you use my backup-script, the script does a simple
docker stop [yourcontainername]
Make sure this command works by using the comandline in your DSM.
You can also activate e-mail notifications in your synology taskplaner to see if the task gets some errors during execution.

If there are still any questions please visit us at iobroker forum thread.
Regards,
André


text:
[Problem]: Container startet nicht

Description / Beschreibung
nach einem neu aufsetzen meines Containers kommt folgender Fehler im Container Log und der Container startet nicht.
neues Volumen habe ich angelegt.
Image version
latest
Docker logs / Docker Protokoll
--------------------------------------------------------------------------------

-------------------------     2023-11-12 15:35:11      -------------------------

--------------------------------------------------------------------------------

-----                                                                      -----

----- ██╗  ██████╗  ██████╗  ██████╗   ██████╗  ██╗  ██╗ ███████╗ ██████╗  -----

----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ -----

----- ██║ ██║   ██║ ██████╔╝ ██████╔╝ ██║   ██║ █████╔╝  █████╗   ██████╔╝ -----

----- ██║ ██║   ██║ ██╔══██╗ ██╔══██╗ ██║   ██║ ██╔═██╗  ██╔══╝   ██╔══██╗ -----

----- ██║ ╚██████╔╝ ██████╔╝ ██║  ██║ ╚██████╔╝ ██║  ██╗ ███████╗ ██║  ██║ -----

----- ╚═╝  ╚═════╝  ╚═════╝  ╚═╝  ╚═╝  ╚═════╝  ╚═╝  ╚═╝ ╚══════╝ ╚═╝  ╚═╝ -----

-----                                                                      -----

-----              Welcome to your ioBroker Docker container!              -----

-----                    Startupscript is now running!                     -----

-----                          Please be patient!                          -----

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

-----                          System Information                          -----

-----                    arch:                x86_64                       -----

-----                    hostname:            ioBrokerTWS                  -----

-----                                                                      -----

-----                          Version Information                         -----

-----                    image:               v9.0.1                       -----

-----                    build:               2023-11-11T23:44:48+00:00    -----

-----                    node:                v18.18.2                     -----

-----                    node[22]: ../src/node_platform.cc:68:std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion `(0) == (uv_thread_create(t.get(), start_thread, this))' failed.

 1: 0xb85bc0 node::Abort() [node]

 2: 0xb85c3e  [node]

 3: 0xbf30fe  [node]

 4: 0xbf31e1 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]

 5: 0xb438f3 node::InitializeOncePerProcess(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, node::ProcessFlags::Flags) [node]

 6: 0xb43f4b node::Start(int, char**) [node]

 7: 0x7f489d0e71ca  [/lib/x86_64-linux-gnu/libc.so.6]

 8: 0x7f489d0e7285 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]

 9: 0xac1f4e _start [node]

npm:                                              -----

-----                                                                      -----

-----                        Environment Variables                         -----

-----                    SETGID:              1000                         -----

-----                    SETUID:              1000                         -----

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

-----                   Step 1 of 5: Preparing container                   -----

--------------------------------------------------------------------------------

Updating Linux packages on first run... Error: Updating failed.

Registering maintenance script as command... Done.

--------------------------------------------------------------------------------

-----             Step 2 of 5: Detecting ioBroker installation             -----

--------------------------------------------------------------------------------

Existing installation of ioBroker detected in "/opt/iobroker".

--------------------------------------------------------------------------------

-----             Step 3 of 5: Checking ioBroker installation              -----

--------------------------------------------------------------------------------

(Re)setting permissions (This might take a while! Please be patient!)... Done.

Checking Database connection... Failed.

Please check your configuration and try again.

For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).

This Script will exit now.

Ich habe das aktuelle Image gerade getestet. Scheint mir kein Problem mit dem Image zu sein.
Allerdings bist du aber auch sehr sparsam mit Informationen zu deinem Setup...
Bitte fülle das nächste Mal deinen Issue vollständig aus. Damit meine ich einen aussagekräftigen Titel, eine Beschreibung mit so vielen Infos zu deinem Setup wie möglich und der korrekten Image Version (siehe Log). Sonst wird es schwer dir zu helfen...
latest ist übrigens keine Version, sondern ein Docker Tag...
Im Log ist zu sehen dass irgendwas mit node/ npm nicht funktioniert. Ich habe aber so spontan keine Idee was da sein könnte.
Mit den Meldungen aus dem Log mal Google gefüttert?
Das ist übrigens mein erster Treffer dazu: https://github.com/nodejs/node/issues/43064
Da du dir nicht die Zeit genommen hast, deinen Issue ordentlich zu füllen, habe ich das jetzt auch nur überflogen. Scheint mir was mit Docker Ressourcen oder eine alten Docker Version zu sein.... Vielleicht setzt du da mal an.
Sehe hier kein Problem mit dem Image selbst und verschiebe das Issue deshalb in die Discussions.
MfG,
André


text:
Error when license contains comma

The following exception is thrown when a license contains a comma, e.g. Apache License, Version 2.0:
/Users/peter/work/license-reporter/lib/unifiedlist.js:103
  throw Error(`No URL was found for [${name}]`);
  ^

Error: No URL was found for [UNKNOWN, UNKNOWN]

It can be reproduced by running the license reporter on a project that has a dependency to rx-lite.
It looks like the license-reporter tries to handle multiple comma separated licenses here: https://github.com/bucharest-gold/license-reporter/blob/master/lib/canonical-name.js#L6
However https://github.com/bucharest-gold/license-reporter/blob/master/lib/unifiedlist.js#L97 doesn't take this into account. It only checks for a single UNKNOWN.
Should multiple comma separated licenses be supported? If not, maybe we can remove https://github.com/bucharest-gold/license-reporter/blob/master/lib/canonical-name.js#L6 and just return get(name) here?

@pb82 thanks for bug report !
reproduced here:
[hf@localhost project-foo]$ npm install rx-lite -S
npm WARN project-foo@1.0.0 No description
npm WARN project-foo@1.0.0 No repository field.

+ rx-lite@4.0.8
added 1 package in 2.168s
[hf@localhost project-foo]$ license-reporter
/home/hf/d/license-reporter/lib/unifiedlist.js:103
  throw Error(`No URL was found for [${name}]`);
  ^

Error: No URL was found for [UNKNOWN, UNKNOWN]
    at Object.urlForName (/home/hf/d/license-reporter/lib/unifiedlist.js:103:9)
    at entry (/home/hf/d/license-reporter/bin/cli.js:53:27)
    at addLicenseEntry (/home/hf/d/license-reporter/bin/cli.js:76:45)
    at xmlObjectData (/home/hf/d/license-reporter/bin/cli.js:128:9)
    at checker.init (/home/hf/d/license-reporter/bin/cli.js:160:17)
    at /home/hf/d/license-reporter/node_modules/license-checker/lib/index.js:373:9
    at /home/hf/d/license-reporter/node_modules/read-installed/read-installed.js:142:5
    at /home/hf/d/license-reporter/node_modules/read-installed/read-installed.js:263:14
    at cb (/home/hf/d/license-reporter/node_modules/slide/lib/async-map.js:47:24)
    at /home/hf/d/license-reporter/node_modules/read-installed/read-installed.js:263:14

@danbev @helio-frota Thank you!

repo: bucharest-gold/license-reporter


text:
Support generating single file for all nodes

Currently, IP address of controlplane node is being appended to the generated talosconfig file.
And hostname of each node is being used to set the machine.network.hostname in the generated node config file.
There's a use case where you want to have one config file for all your nodes. I.e you're using DHCP server to manage the hostname of your nodes, and using PXE boot to load Talos into your nodes.
With combination of all your nodes being identical hardware wise, this is something that has been done by @onedr0p (https://github.com/onedr0p/home-ops/tree/cd103c4543cd177ca6e0d6ba06d4a420cef42834/kubernetes/main/bootstrap)
To support this use case, I'm thinking about adding overrideClientEndpoints (default to empty slice to not break current behavior) so you can provide your own endpoints in the generated talosconfig.
And then also adding per node ignoreHostname (default to false to not break current behavior) so there's no node specific key in the generated config file.
This will allow you to do something like this:

You want to create config file for a 6 nodes (3 controlplane nodes with IP of 1.1.1.1-1.1.1.3 and 3 worker nodes with IP of 1.1.1.4-1.1.1.6).
All of the nodes are of the same hardware specs.
The endpoint is a VIP of 1.1.1.10.

Your talconfig.yaml file should looks something like this:
---
clusterName: main
endpoint: https://1.1.1.10:6443
overrideClientEndpoints:
  - 1.1.1.1
  - 1.1.1.2
  - 1.1.1.3
nodes:
  - hostname: controlplane
    ipAddress: 1.1.1.1 # this is needed although not being used. you'll still use this to do other `talhelper` commands like `gencommand`
    controlPlane: true
    ignoreHostname: true
    ...
  - hostname: worker
    ipAddress: 1.1.1.4 # not needed like above
    controlPlane: false
    ignoreHostname: true

This will create a structure like this in the current working directory:
clusterconfig/
  - main-controlplane.yaml
  - main-worker.yaml
  - talosconfig

The talosconfig will look something like this:
context: main
contexts:
  main:
    endpoints:
      - 1.1.1.1
      - 1.1.1.2
      - 1.1.1.3
...

And there will be no machine.network.hostname field in the generated main-controlplane.yaml and main-worker.yaml.
You can then do talosctl apply-config command to all your nodes.

Thanks to the suggestion from @onedr0p, the linked PR should fix this problem more beautifully.
You can now have something like this instead:
---
clusterName: main
endpoint: https://1.1.1.10:6443
nodes:
  - hostname: controlplane
    ipAddress: 1.1.1.1, 1.1.1.2, 1.1.1.3
    controlPlane: true
    ignoreHostname: true
    ...
  - hostname: worker
    ipAddress: 1.1.1.4, 1.1.1.5, 1.1.1.6
    controlPlane: false
    ignoreHostname: true

All the other talhelper subcommands are also updated to support this behavior, i.e:
talhelper gencommand apply -n controlplane will gives you all the commands like so:
talosctl apply-config --talosconfig=./clusterconfig/talosconfig --nodes=1.1.1.1 --file=./clusterconfig/main-controlplane.yaml
talosctl apply-config --talosconfig=./clusterconfig/talosconfig --nodes=1.1.1.2 --file=./clusterconfig/main-controlplane.yaml
talosctl apply-config --talosconfig=./clusterconfig/talosconfig --nodes=1.1.1.3 --file=./clusterconfig/main-controlplane.yaml

To get only the the specific command for the IP, use -n <IP> instead of -n <hostname>.

One additional thing that would be nice is when generating the talosconfig file it puts the nodes in the file like this:
context: main
contexts:
    main:
        endpoints:
            - 192.168.42.10
            - 192.168.42.11
            - 192.168.42.12
        nodes:
            - 192.168.42.10
            - 192.168.42.11
            - 192.168.42.12
            - 192.168.42.13
            - 192.168.42.14
            - 192.168.42.15

@onedr0p That seems to be unrelated to this issue, so I'll open another issue (or you want to open it instead?).
But, adding nodes to the talosconfig has been something I considered doing before but decided not to. Not sure what made me decided that but I did had a reason,
And funnily enough my own talosconfig has them configured too.
Also, why should the controlplane nodes be listed first?

Also, why should the controlplane nodes be listed first?

Probably for predictability, you'll always know the first node in the list is a controller.

The order should be the same as the order of the nodes slice in talconfig.yaml. So you can basically order it as you want.

repo: budimanjojo/talhelper


text:
TypeError: '<' not supported between instances of 'BeamSearchNode' and 'BeamSearchNode'

I had this problem. I found out that this happens when in the PriorityQueue(PQ) two elements have the same value then, the algorithm moves to the element itself. Because the element in the PQ is an object it generates this Error.
The solution was that I add in the class a special function to handle this by choosing the element with the highest probability., as follows. If this seems ok to you, you can add this lines in your code. Or I can make a pull request.
#function in the class BeamSearchNode
def lt(self, other):
return self.prob < other.prob

@gionanide Hey bro，I think this is the property of the class "PriorityQueue". If you want to use it with the class you define by yourself, you may want to override the it method. Anyway, just some supplement~

Thanks, I was getting this issue too. On python 3.7 and the current version of the code I had to change this method to:
def __lt__(self, other):
        return self.logp < other.logp

authors: RunxinXu gionanide kennethjmyers


text:
Add grpc/go v1.3.0 plugin

The patch to generate to a separate package needed to be updated, so this wasn't automated via the 'Fetch' job.

Here are the changes to the generated code:
diff -ru --exclude plugin.sum --exclude protoc-gen-plugin tests/testdata/buf.build/grpc/go/v1.2.0/eliza/gen/buf/connect/demo/eliza/v1/elizav1grpc/eliza_grpc.pb.go tests/testdata/buf.build/grpc/go/v1.3.0/eliza/gen/buf/connect/demo/eliza/v1/elizav1grpc/eliza_grpc.pb.go
--- tests/testdata/buf.build/grpc/go/v1.2.0/eliza/gen/buf/connect/demo/eliza/v1/elizav1grpc/eliza_grpc.pb.go	2023-03-03 15:42:14.483399320 -0600
+++ tests/testdata/buf.build/grpc/go/v1.3.0/eliza/gen/buf/connect/demo/eliza/v1/elizav1grpc/eliza_grpc.pb.go	2023-03-03 15:42:14.766996955 -0600
@@ -1,6 +1,20 @@
+// Copyright 2022 Buf Technologies, Inc.
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+//      http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+
 // Code generated by protoc-gen-go-grpc. DO NOT EDIT.
 // versions:
-// - protoc-gen-go-grpc v1.2.0
+// - protoc-gen-go-grpc v1.3.0
 // - protoc             (unknown)
 // source: buf/connect/demo/eliza/v1/eliza.proto

@@ -19,6 +33,12 @@
 // Requires gRPC-Go v1.32.0 or later.
 const _ = grpc.SupportPackageIsVersion7

+const (
+	ElizaService_Say_FullMethodName       = "/buf.connect.demo.eliza.v1.ElizaService/Say"
+	ElizaService_Converse_FullMethodName  = "/buf.connect.demo.eliza.v1.ElizaService/Converse"
+	ElizaService_Introduce_FullMethodName = "/buf.connect.demo.eliza.v1.ElizaService/Introduce"
+)
+
 // ElizaServiceClient is the client API for ElizaService service.
 //
 // For semantics around ctx use and closing/ending streaming RPCs, please refer to https://pkg.go.dev/google.golang.org/grpc/?tab=doc#ClientConn.NewStream.
@@ -44,7 +64,7 @@

 func (c *elizaServiceClient) Say(ctx context.Context, in *v1.SayRequest, opts ...grpc.CallOption) (*v1.SayResponse, error) {
 	out := new(v1.SayResponse)
-	err := c.cc.Invoke(ctx, "/buf.connect.demo.eliza.v1.ElizaService/Say", in, out, opts...)
+	err := c.cc.Invoke(ctx, ElizaService_Say_FullMethodName, in, out, opts...)
 	if err != nil {
 		return nil, err
 	}
@@ -52,7 +72,7 @@
 }

 func (c *elizaServiceClient) Converse(ctx context.Context, opts ...grpc.CallOption) (ElizaService_ConverseClient, error) {
-	stream, err := c.cc.NewStream(ctx, &ElizaService_ServiceDesc.Streams[0], "/buf.connect.demo.eliza.v1.ElizaService/Converse", opts...)
+	stream, err := c.cc.NewStream(ctx, &ElizaService_ServiceDesc.Streams[0], ElizaService_Converse_FullMethodName, opts...)
 	if err != nil {
 		return nil, err
 	}
@@ -83,7 +103,7 @@
 }

 func (c *elizaServiceClient) Introduce(ctx context.Context, in *v1.IntroduceRequest, opts ...grpc.CallOption) (ElizaService_IntroduceClient, error) {
-	stream, err := c.cc.NewStream(ctx, &ElizaService_ServiceDesc.Streams[1], "/buf.connect.demo.eliza.v1.ElizaService/Introduce", opts...)
+	stream, err := c.cc.NewStream(ctx, &ElizaService_ServiceDesc.Streams[1], ElizaService_Introduce_FullMethodName, opts...)
 	if err != nil {
 		return nil, err
 	}
@@ -164,7 +184,7 @@
 	}
 	info := &grpc.UnaryServerInfo{
 		Server:     srv,
-		FullMethod: "/buf.connect.demo.eliza.v1.ElizaService/Say",
+		FullMethod: ElizaService_Say_FullMethodName,
 	}
 	handler := func(ctx context.Context, req interface{}) (interface{}, error) {
 		return srv.(ElizaServiceServer).Say(ctx, req.(*v1.SayRequest))
diff -ru --exclude plugin.sum --exclude protoc-gen-plugin tests/testdata/buf.build/grpc/go/v1.2.0/petapis/gen/pet/v1/petv1grpc/pet_grpc.pb.go tests/testdata/buf.build/grpc/go/v1.3.0/petapis/gen/pet/v1/petv1grpc/pet_grpc.pb.go
--- tests/testdata/buf.build/grpc/go/v1.2.0/petapis/gen/pet/v1/petv1grpc/pet_grpc.pb.go	2023-03-03 15:42:14.619819078 -0600
+++ tests/testdata/buf.build/grpc/go/v1.3.0/petapis/gen/pet/v1/petv1grpc/pet_grpc.pb.go	2023-03-03 15:42:14.813849113 -0600
@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-go-grpc. DO NOT EDIT.
 // versions:
-// - protoc-gen-go-grpc v1.2.0
+// - protoc-gen-go-grpc v1.3.0
 // - protoc             (unknown)
 // source: pet/v1/pet.proto

@@ -19,6 +19,13 @@
 // Requires gRPC-Go v1.32.0 or later.
 const _ = grpc.SupportPackageIsVersion7

+const (
+	PetStoreService_GetPet_FullMethodName      = "/pet.v1.PetStoreService/GetPet"
+	PetStoreService_PutPet_FullMethodName      = "/pet.v1.PetStoreService/PutPet"
+	PetStoreService_DeletePet_FullMethodName   = "/pet.v1.PetStoreService/DeletePet"
+	PetStoreService_PurchasePet_FullMethodName = "/pet.v1.PetStoreService/PurchasePet"
+)
+
 // PetStoreServiceClient is the client API for PetStoreService service.
 //
 // For semantics around ctx use and closing/ending streaming RPCs, please refer to https://pkg.go.dev/google.golang.org/grpc/?tab=doc#ClientConn.NewStream.
@@ -39,7 +46,7 @@

 func (c *petStoreServiceClient) GetPet(ctx context.Context, in *v1.GetPetRequest, opts ...grpc.CallOption) (*v1.GetPetResponse, error) {
 	out := new(v1.GetPetResponse)
-	err := c.cc.Invoke(ctx, "/pet.v1.PetStoreService/GetPet", in, out, opts...)
+	err := c.cc.Invoke(ctx, PetStoreService_GetPet_FullMethodName, in, out, opts...)
 	if err != nil {
 		return nil, err
 	}
@@ -48,7 +55,7 @@

 func (c *petStoreServiceClient) PutPet(ctx context.Context, in *v1.PutPetRequest, opts ...grpc.CallOption) (*v1.PutPetResponse, error) {
 	out := new(v1.PutPetResponse)
-	err := c.cc.Invoke(ctx, "/pet.v1.PetStoreService/PutPet", in, out, opts...)
+	err := c.cc.Invoke(ctx, PetStoreService_PutPet_FullMethodName, in, out, opts...)
 	if err != nil {
 		return nil, err
 	}
@@ -57,7 +64,7 @@

 func (c *petStoreServiceClient) DeletePet(ctx context.Context, in *v1.DeletePetRequest, opts ...grpc.CallOption) (*v1.DeletePetResponse, error) {
 	out := new(v1.DeletePetResponse)
-	err := c.cc.Invoke(ctx, "/pet.v1.PetStoreService/DeletePet", in, out, opts...)
+	err := c.cc.Invoke(ctx, PetStoreService_DeletePet_FullMethodName, in, out, opts...)
 	if err != nil {
 		return nil, err
 	}
@@ -66,7 +73,7 @@

 func (c *petStoreServiceClient) PurchasePet(ctx context.Context, in *v1.PurchasePetRequest, opts ...grpc.CallOption) (*v1.PurchasePetResponse, error) {
 	out := new(v1.PurchasePetResponse)
-	err := c.cc.Invoke(ctx, "/pet.v1.PetStoreService/PurchasePet", in, out, opts...)
+	err := c.cc.Invoke(ctx, PetStoreService_PurchasePet_FullMethodName, in, out, opts...)
 	if err != nil {
 		return nil, err
 	}
@@ -121,7 +128,7 @@
 	}
 	info := &grpc.UnaryServerInfo{
 		Server:     srv,
-		FullMethod: "/pet.v1.PetStoreService/GetPet",
+		FullMethod: PetStoreService_GetPet_FullMethodName,
 	}
 	handler := func(ctx context.Context, req interface{}) (interface{}, error) {
 		return srv.(PetStoreServiceServer).GetPet(ctx, req.(*v1.GetPetRequest))
@@ -139,7 +146,7 @@
 	}
 	info := &grpc.UnaryServerInfo{
 		Server:     srv,
-		FullMethod: "/pet.v1.PetStoreService/PutPet",
+		FullMethod: PetStoreService_PutPet_FullMethodName,
 	}
 	handler := func(ctx context.Context, req interface{}) (interface{}, error) {
 		return srv.(PetStoreServiceServer).PutPet(ctx, req.(*v1.PutPetRequest))
@@ -157,7 +164,7 @@
 	}
 	info := &grpc.UnaryServerInfo{
 		Server:     srv,
-		FullMethod: "/pet.v1.PetStoreService/DeletePet",
+		FullMethod: PetStoreService_DeletePet_FullMethodName,
 	}
 	handler := func(ctx context.Context, req interface{}) (interface{}, error) {
 		return srv.(PetStoreServiceServer).DeletePet(ctx, req.(*v1.DeletePetRequest))
@@ -175,7 +182,7 @@
 	}
 	info := &grpc.UnaryServerInfo{
 		Server:     srv,
-		FullMethod: "/pet.v1.PetStoreService/PurchasePet",
+		FullMethod: PetStoreService_PurchasePet_FullMethodName,
 	}
 	handler := func(ctx context.Context, req interface{}) (interface{}, error) {
 		return srv.(PetStoreServiceServer).PurchasePet(ctx, req.(*v1.PurchasePetRequest))

repo: bufbuild/plugins


text:
Differences between agabani/tor-operator

I think it could be useful to have some comparision.
First result I found wasn't this controller, but rather https://github.com/agabani/tor-operator

Hi @samip5, thanks for letting me know. I wasn't aware of this project; I guess it is shown as first result because it has been more recently updated. Not sure what's the motivation other than using rust; I would have prefer to agree on a common Tor spec and then have operators implementing it. I must say there are some nice features there like HPA and OpenTelemetry.
What kind of comparison are you looking for?

Something like feature parity, but it seems that the other one for one runs tor as root..

repo: bugfest/tor-controller


text:
When the humbug_reports drone fails to write a report into the database, it starts losing all subsequent reports

The report is getting correctly added to the failure queue, but all subsequent reports fail to be added to the database and fail to be added to the failure queue with this error message:
Jul 30 02:08:05 ip-17-29-3-64 droneshumbugreports[1460]: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "uc_journal_entry_tags_journal_entry_id_tag"
Jul 30 02:08:05 ip-17-29-3-64 droneshumbugreports[1460]: DETAIL:  Key (journal_entry_id, tag)=(<redacted>, <redacted>) already exists.
Jul 30 02:08:05 ip-17-29-3-64 droneshumbugreports[1460]: [SQL: INSERT INTO journal_entry_tags (id, journal_entry_id, tag) VALUES (%(id)s, %(journal_entry_id)s, %(tag)s)]
Jul 30 02:08:05 ip-17-29-3-64 droneshumbugreports[1460]: [parameters: {'id': UUID('80a44aa5-5a81-4380-b769-bae741d5bb24'), 'journal_entry_id': UUID('<redacted>'), 'tag': '<redacted>'}]
Jul 30 02:08:05 ip-17-29-3-64 droneshumbugreports[1460]: (Background on this error at: http://sqlalche.me/e/13/gkpj) (Background on this error at: http://sqlalche.me/e/13/7s2a)

The first problem is that we are lacking a db_session.rollback() on the error condition: https://github.com/bugout-dev/drones/blob/c09297902e30f1751b83973c668d41f71df0f451/drones/humbug_reports.py#L133

The second problem is that there is no transaction boundary spanning the queue pop and the database write.

We need to understand where the SQLAlchemy error was being raised, because it isn't being raised in the try block linked above.

I understand the second issue now. The problem is that process_humbug_tasks_queue splits the reading of reports from redis and writing of reports to postgres into two separate functions.
Between reading and writing, it attempts to do something with the database (get_humbug_integrations).
That is the database operation that is failing, and the except block in process_humbug_tasks_queue does not save failed reports to the failed reports queue. It just prints the error and exits.
This error handling needs to be improved!

Added rollback in PR https://github.com/bugout-dev/drones/pull/14

authors: kompotkot zomglings

repo: bugout-dev/drones


text:
Send device time with all error reports

Previously, this would only happen for auto-notified error reports. This allows us to send it every time we send an error report to bugsnag.

Looks good 👍 🍰

authors: eanakashima wordofchristian

repo: bugsnag/bugsnag-js


text:
Secure authentication with bugsnag-sourcemaps

It's my understanding that anything distributed as part of my app's binary cannot be considered "secret". This includes values (such as API keys) stored in an iOS app's Info.plist file.
As such, the Bugsnag project API Key is, for all intents and purposes, a public token. This is fine in the context of reporting bugs from my app since a malicious actor would only be able to use that API Key to submit data to the server (rather than retrieve data).
However, it looks like the bugsnag-sourcemaps tool currently uses that same (public) API Key for authentication, meaning that anyone who has access to my app binary (the public) can presumably upload (and overwrite) sourcemaps to the Bugsnag servers for my app. While this may not represent  any (direct) potential for unauthorized disclosure of private information, it does present the possibility for sourcemaps/stacktraces to be manipulated by malicious parties as part of a more elaborate attack.
Would it be possible for future versions of bugsnag-sourcemaps to employ the same API authentication mechanism used by the Data access API?

Thank you for the detailed report and the suggestion, @bencollab. Its certainly possible that there may be other supported means of authentication in the future, and I'll raise it with the product team. However, similar to how a malicious actor could send error reports using the API key but never know if it had any effect, the same is true for uploading source maps. Would the ability to delete uploaded source maps be a good workaround in the meantime?

Thanks for looking into it. The ability to delete source maps would be a nice addition, but it wouldn't really do anything to resolve the core issue.
I do agree that the potential for harm in this case is (as far as I can tell) relatively minimal, so probably not a super high priority. The main concern for me is just the idea that someone could be messing with my sourcemaps. To fully resolve the issue, I believe it would require not only added support for different authentication methods in the client, but also the ability to enforce only a certain kind of authentication at the account level.

authors: bencollab kattrali

repo: bugsnag/bugsnag-react-native


text:
Write a curl | sh script to install precompiled ockam binaries

We release precompiled binaries in every release. We want to have a curl | sh script to make it easy for people to install these binaries.
https://github.com/build-trust/ockam/releases/tag/ockam_v0.75.0

Hey @mrinalwadhwa , I'd like to work on this, can I get this issue assigned?

Hey @mrinalwadhwa , I'd like to work on this, can I get this issue assigned?

Done! Thanks 🚀

Forgot to ask before: got any preferences on where the new script should be located and what its name should be?

Forgot to ask before: got any preferences on where the new script should be located and what its name should be?

We can have the script here. I think release-installer.sh sounds cool 😎but it’s left to you if you have a better name 😎.

Probably a very dumb question, but what implementation scope would you guys like to see in the commit message for this? 😃

😄 we can scope it under ci. ci: add ockam release installer script will be pretty neat 🥶

Added in https://github.com/build-trust/ockam/pull/3488
Thank you @danieled-it 🥳 🎈

authors: danieled-it metaclips mrinalwadhwa

repo: build-trust/ockam


text:
fix(rust): named identities allowed on lease command, add test cases

named identites are now supported on message send and lease * commands. A proper credential is requested and used in these cases.  New test cases added.
Left some FIXME and TODO for things that are workarounds,   or that need to be fixed.

Thanks for adding the FIXME comments to the with_embedded_node method.
I don't see any urgent issues with this PR; If you're okay with it, I'd like to just fix that method up, so that order doesn't matter.
But other than that LGTM.

@CAOakleyII  :+1:  lets say we want this merged tomorrow to think about doing another release with the fix.     So not merging for now,  if you can fix that ordering issue lets merge once that's incorporated.   If we didn't finish that for tomorrow,  lets merge this as-is  and fix the ordering on a separate PR  (that is less urgent,  but still needed as otherwise we will  shot ourselves on foot sooner or latter)

@Mergifyio rebase

@Mergifyio rebase

authors: CAOakleyII polvorin


text:
[charts/buildbuddy-executor] Only set SYS_* environment variables if they are not in the config

This PR prevents adding SYS_MEMORY_BYTES and SYS_MILLICPUS environment variables to the executor pod, if those values are set in the executor config. As documented in the executor config here, these values should only be set either by the environment variables or the config, but not both. This PR reflects those requirements in the helm chart.

Thanks for all of these thoughtful / clean / useful PRs @JamesMBartlett - we'll get these all merged tomorrow if that works for you!

Thanks for all of these thoughtful / clean / useful PRs @JamesMBartlett - we'll get these all merged tomorrow if that works for you!

Sounds great

authors: JamesMBartlett siggisim

repo: buildbuddy-io/buildbuddy-helm


text:
Update go-buildkite to v4.0.0

This PR updates go-buildkite to v4! It deals with the major breaking changes:

strips out the many pointer derefs we had, because they're no longer needed!
passes contexts to all of the calls to go-buildkite calls

there's a couple in the builds resolver that i've just plugged context.TODO() into, because the build resolver scares me and i'm afraid to touch it

This looks pretty fine to me, but looks like a red build at the moment :eyes:

repo: buildkite/cli


text:
Saving caches between builds

Don't know if this is the right place to ask, but is there a way to store caches between builds like heroku or circleci does, i.e. Rails precompiled assets. I know that docker has its own caching, but this layer's cache is always busted because of the app code change

We use buildkite artifact uploading/downloading to share built assets between jobs within the same build, but unfortunately global artifacts between builds aren't yet supported.
Until then, I think you should be able to use S3 to share assets between builds. Something like this might work for you:
aws configure set default.s3.max_concurrent_requests 20
aws s3 sync s3://ci-app-assets ./public

docker-compose run \
  -e RAILS_ENV=production \
  -e RAILS_GROUPS=assets \
  -ASSET_HOST \
  --rm \
  --volume /tmp:/tmp \
  --volume "$PWD/public/assets":/app/public/assets \
  app bundle exec rake \
    assets:precompile \
    assets:clean

aws s3 sync --delete ./public s3://ci-app-assets

thanks. I think the tmp/cache/assets folder needs to be synced too, but I get the idea

Closing this in favour of a caching plugin.

Anyone here tried this? https://github.com/danthorpe/cache-buildkite-plugin

@edify42 bit late, but adding in case still relevant for you or others. I have had more success with this plugin, specifically using the rsync method. It has been more recently updated and is actually based on that one you mention: https://github.com/gencer/cache-buildkite-plugin

repo: buildkite/elastic-ci-stack-for-aws


text:
Chore - Update flying-saucer version

Context
The latest flying-saucer library is available, which fixes issues with broken links to older bouncycastle dependencies.

Definition of Done
Update flying-saucer to version9.1.6 on both modules (Play 2.4 and 2.5).

Addressed in PR #14 .


text:
Panduan Pengaturan Profil Masjid

Goal
Pada task ini, kita ingin membuat panduan untuk pengaturan data profil masjid.

Task ini sudah selesai, hasilnya:
https://bukumasjid.com/tutorial/settings/masjid-profile/

repo: buku-masjid/docs


text:
Property '$vm2' does not exist on type

Hi
Thanks for your component.
I'm using it successfully in debug mode.  While in debug mode I do get an error though:
Property '$vm2' does not exist on type 'CombinedVueInstance<Vue, PageState....
While in debug mode this still runs correctly, but if I try and do yarn build, it fails with the same error.
Any ideas?
Thanks

which version are you using?

v1.1.8 should be fine.
Tested it using debug mode and build mode no error prompted in console.

Hmmm... I was using v1.1.6.  upgraded to 1.1.8, still getting the same error...  Must be something else about my config...?

authors: avpavp burhanahmeed


text:
Created simple .editorconfig

For contributors who's editors/IDE support it, this will save us from having to push back on some style issues in PR's (primarily spaces => tabs). Check out http://editorconfig.org/ for more information.
I'll leave this open for a week or so for anyone to push back and/or add rules to the file as you see fit.

Here are a few other examples from PHP projects.

CakePHP - https://github.com/cakephp/cakephp/blob/master/.editorconfig
Drupal - http://cgit.drupalcode.org/drupal/tree/.editorconfig
Symfony2 - https://github.com/symfony/symfony/blob/2.7/.editorconfig

Here's the full list: https://github.com/editorconfig/editorconfig/wiki/Projects-Using-EditorConfig

Nice. Looks like a good initiative to get behind.
Any talk of this in SilverStripe community already?

I've not seen it showing up on any other Silverstripe projects, no. I suppose one step beyond this is getting Scrutinizer to also check for style issues (where braces are placed, etc). The nice thing about this is that it's proactive if your editor supports it. So I could use PSR-2 on the rest of a project but any file in the shop folder will automatically use tabs, etc.
I'd love to see it adopted more widely within the SS ecosystem. I wonder if it's worth raising on the dev list?
Note to self: before merging this we should also update the contributors doc asking them to install editor/ide plugins as needed.

@jedateach are you happy with the state of this? If so I'll go ahead and squash these commits and merge.

Yep, great. Go for it!

authors: jedateach markguinn

repo: burnbright/silverstripe-shop


text:
Use CocoaPods in example project

Switching the example project from Carthage to CocoaPods. Reasons:

Despite its initial promise, Carthage adoption is low — and now looks like it will remain permanently low with SwiftPM coming. Far more users interesting in trying an example project will have CocoaPods installed.
Carthage has proven inflexible, slow, difficult for new users to set up, and reluctant to adapt to user needs. CocoaPods is a terrifying behemoth, but one that works well.
CocoaPods makes it easy to test Siesta changes locally in the example project, because it supports local file system dependencies. Carthage does not, and thus requires a push or hackery to test changes. (This shortcoming also forces a redundant checkout with Carthage.)
This should make pod try work properly.

This is for the GithubBrowser example project only. The core Siesta project will continue to use Carthage for the time being.
Objections? Speak now!

I had so many nightmares with the Behemoth, as you say, I still prefer the simplicity and distributed philosophy of Carthage. But to give a try, CocoaPods has certainly a larger userbase.

authors: onekiloparsec pcantrell

repo: bustoutsolutions/siesta


text:
Fix no-ex-assign rule on non-assignment ops

Moves the isAssignmentToken function into a support folder for code reuse.
Closes https://github.com/buzinas/tslint-eslint-rules/issues/118.

Thanks for the PR.

v1.6.1 released.

I just want to thank you for having a simple and awesome test suite set up 😄 It took me all of 10 minutes to quickly add the test case and patch as a result!

Thanks for the compliment!
And yeah, it really comes in handy. Every time someone opens an issue, my first step is to create a test case for the bug and try to make it passes somehow! 😸

authors: blakeembrey buzinas

repo: buzinas/tslint-eslint-rules


text:
🛑 Sunshine Silicon Citi is down

In 61ff936, Sunshine Silicon Citi (https://cloud.tymly.in/status/1021) was down:

HTTP code: 521
Response time: 20237 ms

Resolved: Sunshine Silicon Citi is back up in 1faa981.

repo: bvenkysubbu/tymlymonitor


text:
🛑 Trifecta Esplanade Security is down

In 6a22a9b, Trifecta Esplanade Security (https://cloud.tymly.in/status/1168) was down:

HTTP code: 521
Response time: 20247 ms

Resolved: Trifecta Esplanade Security is back up in c5546b5.


text:
🛑 Casa Gopalan Block A Lift is down

In b309a40, Casa Gopalan Block A Lift (https://cloud.tymly.in/status/1006) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Casa Gopalan Block A Lift is back up in 51eb0bf.


text:
🛑 Trifecta Esplanade B Block is down

In 1074b0f, Trifecta Esplanade B Block (https://cloud.tymly.in/status/1154) was down:

HTTP code: 521
Response time: 242 ms

Resolved: Trifecta Esplanade B Block is back up in 3551ca2.


text:
🛑 Sterling Shalom E Block is down

In 3561fd3, Sterling Shalom E Block (https://cloud.tymly.in/status/1070) was down:

HTTP code: 521
Response time: 231 ms

Resolved: Sterling Shalom E Block is back up in 0318167.


text:
🛑 SMD Altezz Block A is down

In 146749a, SMD Altezz Block A (https://cloud.tymly.in/status/1175) was down:

HTTP code: 521
Response time: 20972 ms

Resolved: SMD Altezz Block A is back up in efdad95.


text:
🛑 Dasta Concerto Entrance is down

In 4265458, Dasta Concerto Entrance (https://cloud.tymly.in/status/1137) was down:

HTTP code: 521
Response time: 229 ms

Resolved: Dasta Concerto Entrance is back up in e5fe402.


text:
🛑 Dasta Concerto Basement is down

In 2a36289, Dasta Concerto Basement (https://cloud.tymly.in/status/1138) was down:

HTTP code: 521
Response time: 20245 ms

Resolved: Dasta Concerto Basement is back up in 5082660.


text:
🛑 SNR Silver Ripples is down

In a53d9db, SNR Silver Ripples (https://cloud.tymly.in/status/1039) was down:

HTTP code: 521
Response time: 250 ms

Resolved: SNR Silver Ripples is back up in 0d2b731.


text:
🛑 PSR Aster 1 is down

In ea5d6d9, PSR Aster 1 (https://cloud.tymly.in/status/1059) was down:

HTTP code: 521
Response time: 234 ms

Resolved: PSR Aster 1 is back up in e4a3a0a.


text:
🛑 White Breeze 1 is down

In b8382b1, White Breeze 1 (https://cloud.tymly.in/status/1096) was down:

HTTP code: 521
Response time: 20244 ms

Resolved: White Breeze 1 is back up in 1c270a3.


text:
🛑 Sai Raghavendras Bloomfields is down

In 955098f, Sai Raghavendras Bloomfields (https://cloud.tymly.in/status/1014) was down:

HTTP code: 521
Response time: 20228 ms

Resolved: Sai Raghavendras Bloomfields is back up in d695bb4.


text:
🛑 Mahaveer Varna B3 is down

In fb509d6, Mahaveer Varna B3 (https://cloud.tymly.in/status/1086) was down:

HTTP code: 521
Response time: 20230 ms

Resolved: Mahaveer Varna B3 is back up in 0be5fb6.


text:
🛑 SMD Altezz Block B Basement is down

In f20c6c7, SMD Altezz Block B Basement (https://cloud.tymly.in/status/1204) was down:

HTTP code: 521
Response time: 228 ms

Resolved: SMD Altezz Block B Basement is back up in a5a6bb5.


text:
🛑 SMD Altezz Block B Basement is down

In a58f585, SMD Altezz Block B Basement (https://cloud.tymly.in/status/1204) was down:

HTTP code: 521
Response time: 20223 ms

Resolved: SMD Altezz Block B Basement is back up in a59d295.


text:
🛑 Adarsh Vihar is down

In 43a83cb, Adarsh Vihar (https://cloud.tymly.in/status/1041) was down:

HTTP code: 521
Response time: 220 ms

Resolved: Adarsh Vihar is back up in 391ce6d.


text:
🛑 Trifecta Esplanade P Block is down

In df350e8, Trifecta Esplanade P Block (https://cloud.tymly.in/status/1017) was down:

HTTP code: 521
Response time: 20219 ms

Resolved: Trifecta Esplanade P Block is back up in af3d328.


text:
🛑 Dasta Concerto Clubhouse Gym is down

In be57702, Dasta Concerto Clubhouse Gym (https://cloud.tymly.in/status/1189) was down:

HTTP code: 521
Response time: 214 ms

Resolved: Dasta Concerto Clubhouse Gym is back up in 1ce71d0.


text:
🛑 DSR Sunrise Towers 2 is down

In 89fbac0, DSR Sunrise Towers 2 (https://cloud.tymly.in/status/1027) was down:

HTTP code: 521
Response time: 20245 ms

Resolved: DSR Sunrise Towers 2 is back up in 34d62fe.


text:
🛑 Sterling Shalom E Block is down

In 076abd1, Sterling Shalom E Block (https://cloud.tymly.in/status/1070) was down:

HTTP code: 521
Response time: 20241 ms

Resolved: Sterling Shalom E Block is back up in f3e561d.


text:
🛑 SMD Altezz Block B is down

In 3c978ef, SMD Altezz Block B (https://cloud.tymly.in/status/1176) was down:

HTTP code: 521
Response time: 20244 ms

Resolved: SMD Altezz Block B is back up in a180062.


text:
🛑 Prakruthi Villas Sarjapura is down

In 269346f, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 20246 ms

Resolved: Prakruthi Villas Sarjapura is back up in 04a2761.


text:
🛑 Dasta Concerto Basement 2 is down

In 0d673bf, Dasta Concerto Basement 2 (https://cloud.tymly.in/status/1188) was down:

HTTP code: 521
Response time: 20245 ms

Resolved: Dasta Concerto Basement 2 is back up in 4d551da.


text:
🛑 Nitesh Flushing Meadows Block D is down

In 75ca115, Nitesh Flushing Meadows Block D (https://cloud.tymly.in/status/1049) was down:

HTTP code: 521
Response time: 20221 ms

Resolved: Nitesh Flushing Meadows Block D is back up in 61676f2 after 893 days, 23 hours, 3 minutes.


text:
🛑 Sowparnika Ananda is down

In e2c0a0c, Sowparnika Ananda (https://cloud.tymly.in/status/1036) was down:

HTTP code: 521
Response time: 215 ms

Resolved: Sowparnika Ananda is back up in 33e82a3 after 898 days, 4 hours, 42 minutes.


text:
🛑 SMD Altezz Block B is down

In ccd4831, SMD Altezz Block B (https://cloud.tymly.in/status/1176) was down:

HTTP code: 521
Response time: 20245 ms

Resolved: SMD Altezz Block B is back up in d37f64d after 10 minutes.


text:
🛑 SMR Vinay Cascade B Block is down

In 420e4b9, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 521
Response time: 20973 ms

Resolved: SMR Vinay Cascade B Block is back up in b4dad1e.


text:
🛑 SMR Vinay Cascade B Block is down

In 1450629, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 521
Response time: 204 ms

Resolved: SMR Vinay Cascade B Block is back up in 6448a36.


text:
🛑 Trifecta Esplanade L Block is down

In a6e3309, Trifecta Esplanade L Block (https://cloud.tymly.in/status/1164) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Trifecta Esplanade L Block is back up in 037894f.


text:
Installation 404 Not found

While installing the plugin I got the error „install response status 404 Not found ..“ (see attached picture)
This was the only problem while installing the plugin.

I use the Homebridge UI.
Version 4.50.2 is installed.
It is installed on Raspberry Pi.
Govee version 7.9.0 is installed.
Node version 18.13.0
Npm version 9.3.1

please use the homebridge terminal to run these commands:
cd /usr/local/lib/node_modules/homebridge-govee

sudo npm install @abandonware/bluetooth-hci-socket

sudo npm install @abandonware/noble

restart homebridge and see if this has worked 🤔

This worked for me. But after making an update to the plugin I recieved the same error. Do you think this will cause any problems?
I also struggle to connect the hygrometer H 5075 to my homebridge.
thanks for help in advance

I used sudo hcitool inq and sudo hcitool scan but without any result. Thats why I can‘t pair the hygrometer with the homebridge.
With command hcitool dev I see hci0 I guess this is the bluetooth MAC from the raspberry


text:
Fix long wave labels

MMDataState and DataGeneratorWaves used the full function names as wave label to find its
entries. This can lead to bugs when the full function name becomes
larger than the supported wave label size. This is fixed using a second
text wave to store the function names at the same index as the entries
in MMDataState or DataGeneratorWaves.
This is the same fix as in 0309a67 (Function Tags: Fix long function
name bug, 2023-01-18).
Close #390

@t-b @MichaelHuth Ready for review.

repo: byte-physics/igortest