Implement HealthWorker display logic

[ Functionality Issue ]

By milestone v1.3, the app needs to display the health worker upon a successful add command execution, with the appropriate details shown. :stuck_out_tongue_winking_eye:

Completed in one of the PRs.


Plywood detail panel

Implements asset detail panel where plywood details (individual tree trunks) are shown.
User can view the tree trunks by clicking a plywood row in the building table.
User can return to:

building asset table by pressing a back button in the detail panel
to the browse buildings map by pressing back button in the building table

Building view dispatches a custom event with coordinates when a tree trunk row is clicked in the detail panel.
Todo:

Currently the coordinates are placeholders for real values
Map does not act on the event yet

This was open for 4 days and was co-created with A-P => enough confidence to merge


Sema: Track writes through WritableKeyPaths for mutation warnings.

Previously we would erroneously flag a var as not being mutated if the only mutations were through WritableKeyPaths. Fixes SR-5214 | rdar://problem/32599483.

@swift-ci Please smoke test


Using custom bucket configuration, the event handler doesn't match the bucket name

Hi - me again. I  might be able to workaround this one by having a simpler config but it may be worth looking into.
With s3 events you can either have the bucket created by the event config for the triggered lambda or you can use custom bucket configuration.
I'm using the latter, like this.
functions:
  uploaded:
    handler: fotos/uploaded.uploadedItem
    events:
      - s3: fotos

Then I add my custom bucket config in the resources section, changing the name to something a bit more realistic for an s3 bucket name (fotopia-web-app-prod):
    S3BucketFotos:
      Type: AWS::S3::Bucket
      DeletionPolicy: Delete
      Properties:
        BucketName: ${self:provider.environment.S3_BUCKET}
        AccessControl: PublicRead

My lambda wasnt firing when I PUT images into the bucket so I added some logging into serverless-s3-local like so:

Which revealed the problem - the event handler has the short (alias?) bucket name:

I'll have a dig around perhaps theres a way via the sls plugin API to get the connection between the shorthand name and the longer name specified in resources.

@mbudm
Thanks for your comment and PR.
I reviewed some codes in #22 .
Please check this review.

@ar90n - I don't think you saved the PR review? I can't see anything over at #22

@mbudm
I'm so sorry.
I fixed the status of my comment.
Please check it.

Close this issue.
Because  #22 was merged.


Have it return the replicated movement speed

Are you not sending the WalkSpeed to the server when it's in the air state? If you are, then this shouldn't cause any errors and would be preferred instead of a flat float value. Let me know if that's okay or what needs to be implemented to fix this, I wanna implement this for bhopping!

This won't be merged as I would want it to use MaxAirSpeed or something other than max ground speed

Could be edited though


Not using the Codec?

So I am trying to write the snappy compressed Avro to a file. I am giving the write from the given example the Snappy codec.
let mut writer = Writer::with_codec(&schema, Vec::new(), Codec::Snappy);
When I print what into_inner(); returns I see a vector printed with integers in it. I can only assume that is the avro encoded or something. However when I change the codec to Codec::Null the vector is no different. I am a little confused on how the codec is used and how I can get the compressed avro written to a file?
I should also note that I check the vector and its not valid Snappy.

Just to make sure everything is in order, did you turn the snappy feature on in your Cargo.toml?

@poros I did, I ended up just manually compressing it with a different Snappy library on top of the avro encoding. That worked but before my cargo had.
[dependencies.avro-rs]
version = "0.6"
features = ["snappy"]

@sdrafahl I tried to reproduce what you described above about Codec:Null and Codec:Snappy giving back the same vector as result of Writer::into_inner, but they are different in my experiment:
#[cfg(feature = "snappy")]
    #[test]
    fn test_writer_with_codec_difference() {
        let schema = Schema::parse_str(SCHEMA).unwrap();

        let mut writer = Writer::with_codec(&schema, Vec::new(), Codec::Null);
        let mut record = Record::new(&schema).unwrap();
        record.put("a", 27i64);
        record.put("b", "foo");
        let n1 = writer.append(record.clone()).unwrap();
        let n2 = writer.append(record.clone()).unwrap();
        let n3 = writer.flush().unwrap();
        let result = writer.into_inner();

        let mut other_writer = Writer::with_codec(&schema, Vec::new(), Codec::Snappy);
        let mut other_record = Record::new(&schema).unwrap();
        other_record.put("a", 27i64);
        other_record.put("b", "foo");
        let other_n1 = other_writer.append(other_record.clone()).unwrap();
        let other_n2 = other_writer.append(other_record.clone()).unwrap();
        let other_n3 = other_writer.flush().unwrap();
        let other_result = other_writer.into_inner();

        println!("null {:?}", result);
        println!("snappy {:?}", other_result);

        assert_ne!(other_result, result);

test writer::tests::test_writer_with_codec_difference ... ok
null [79, 98, 106, 1, 4, 20, 97, 118, 114, 111, 46, 99, 111, 100, 101, 99, 8, 110, 117, 108, 108, 22, 97, 118, 114, 111, 46, 115, 99, 104, 101, 109, 97, 222, 1, 123, 34, 116, 121, 112, 101, 34, 58, 34, 114, 101, 99, 111, 114, 100, 34, 44, 34, 110, 97, 109, 101, 34, 58, 34, 116, 101, 115, 116, 34, 44, 34, 102, 105, 101, 108, 100, 115, 34, 58, 91, 123, 34, 110, 97, 109, 101, 34, 58, 34, 97, 34, 44, 34, 116, 121, 112, 101, 34, 58, 34, 108, 111, 110, 103, 34, 44, 34, 100, 101, 102, 97, 117, 108, 116, 34, 58, 52, 50, 125, 44, 123, 34, 110, 97, 109, 101, 34, 58, 34, 98, 34, 44, 34, 116, 121, 112, 101, 34, 58, 34, 115, 116, 114, 105, 110, 103, 34, 125, 93, 125, 0, 115, 214, 5, 31, 39, 212, 38, 28, 214, 77, 126, 43, 33, 1, 8, 225, 4, 20, 54, 6, 102, 111, 111, 54, 6, 102, 111, 111, 115, 214, 5, 31, 39, 212, 38, 28, 214, 77, 126, 43, 33, 1, 8, 225]
snappy [79, 98, 106, 1, 4, 20, 97, 118, 114, 111, 46, 99, 111, 100, 101, 99, 12, 115, 110, 97, 112, 112, 121, 22, 97, 118, 114, 111, 46, 115, 99, 104, 101, 109, 97, 222, 1, 123, 34, 116, 121, 112, 101, 34, 58, 34, 114, 101, 99, 111, 114, 100, 34, 44, 34, 110, 97, 109, 101, 34, 58, 34, 116, 101, 115, 116, 34, 44, 34, 102, 105, 101, 108, 100, 115, 34, 58, 91, 123, 34, 110, 97, 109, 101, 34, 58, 34, 97, 34, 44, 34, 116, 121, 112, 101, 34, 58, 34, 108, 111, 110, 103, 34, 44, 34, 100, 101, 102, 97, 117, 108, 116, 34, 58, 52, 50, 125, 44, 123, 34, 110, 97, 109, 101, 34, 58, 34, 98, 34, 44, 34, 116, 121, 112, 101, 34, 58, 34, 115, 116, 114, 105, 110, 103, 34, 125, 93, 125, 0, 43, 86, 32, 150, 161, 129, 104, 9, 168, 37, 54, 125, 177, 8, 146, 36, 4, 32, 10, 36, 54, 6, 102, 111, 111, 54, 6, 102, 111, 111, 31, 157, 101, 245, 43, 86, 32, 150, 161, 129, 104, 9, 168, 37, 54, 125, 177, 8, 146, 36]

Is it similar to what you were trying? Can you show me what you did?
In addition, the end result won't be valid snappy because of the avro magic bytes and headers, but the payload should be snappy encoded.


Update to Rails 5.2.2

The biggest change aside from Rails is probably moving simple_form from 3.5.0 to 4.0.0. However, we don't have any forms in our app, so it can't affect us.
@edwardloveall

What do you think about removing simple form?

I agree, let's remove simple_form. Please hold.

@edwardloveall I opened a new PR to remove simple_form in #100

simple_form has been removed, and I force-pushed this branch.


Update basic.ipynb docs to reference PyLabRobot instead of PyHamilton

Seems like this should reference PyLabRobot instead of PyHamilton, but I could be wrong?

Oops, a rare relic from the time PLR was a pyhamilton fork. Thanks for fixing!


Dev branch

Hello!
The changes requested should be a separate plugin for Slack and not part of the custom_alerter.py file.

Moved all slack alert logic out to slack_alerter.py

Made requested changes according to example in security_monkey/misc.md

Created init, moved variable declarations into init method, and swapped print statement out for logger.


Add support for rendering un-tented vias (fusion/eagle)

Addresses #416
New 'drillsize' parameter added to tracks, only included for un-tented vias.
This PR includes changes for Fusion/Eagle workflow only.

'drillsize' parameter is now included on tracks representing un-tented vias only, from fusion/eagle workflow only.  Still need to make changes in JS so they render differently.

Okay, I took a stab at the rendering changes.  Seems to work, including highlighting, at least for my simple test case.  More testing is certainly warranted.

One change that gave me pause was swapping the order of rendering tracks and zones.  Vias inside of, and same net as, a zone weren't visible because the zone was drawn on top of them.  Vias that weren't the same net as the zone were already OK, because the zone has cutouts for them (#415 notwithstanding).  I can't immediately think of a reason that rendering zones first would have unintended consequences, but I'm not certain.

One change that gave me pause was swapping the order of rendering tracks and zones

That's fine, previously order didn't matter because same net vias were blending into zones either way.

Okay, done.   I took a cue from your suggestion and used copper (track) color, rather than pad color, for the annular ring of the via.  Seems like either way would be reasonable, but the former makes the vias a little less visually distracting on a board that has a lot of them.

Looks good, can you squash your commits?

Squashed

Thanks for the contribution, I'll add kicad support shortly.


Integrate TF Connect in TFGrid Database

See important discussion in older tickets:
https://github.com/threefoldtech/home/issues/859
https://github.com/threefoldtech/home/issues/884
And tfgrid db ticket here : https://github.com/threefoldtech/home/issues/1083
All data should be unified in one database

[ ] Get all TF Connect data in TFGrid database
[ ] Get all OpenKYC data in TFGrid database
[ ] Change ThreeFold Connect to connect to this database

This issue has not been update for a long time.  Please reconsider if this is part if this release or the next.  I'll remove it if not update and considered part of this release.  Bump it up to in progress is this needs to be done in this release or push it to the next one.

we prob need to take other approach to do with cosmos, lets postpone now


Discord Service Download Failed at Start

Error occured when service try to resolve and download last discord version:
Resolving discord.com (discord.com)... failed: Temporary failure >
wget: unable to resolve host address ‘discord.com’
[ERROR] Failed to download discord.

Issue fixed in the latest release.


SessionError

Hello!
I have a Win7 x64 Machine, when im running the code and targeting it, i get this error:
Traceback (most recent call last):
  File "exploit.py", line 93, in <module>
    main(sys.argv[1:])
  File "exploit.py", line 35, in main
    tid = s.tree_connect_andx(r"\\*SMBSERVER\C")
  File "/home/xazker/.local/lib/python2.7/site-packages/impacket/smb.py", line 2764, in tree_connect_andx
    if smb.isValidAnswer(SMB.SMB_COM_TREE_CONNECT_ANDX):
  File "/home/xazker/.local/lib/python2.7/site-packages/impacket/smb.py", line 718, in isValidAnswer
    raise SessionError("SMB Library Error", self['ErrorClass'] + (self['_reserved'] << 8), self['ErrorCode'], self['Flags2'] & SMB.FLAGS2_NT_STATUS, self)
impacket.smb.SessionError: SMB SessionError: STATUS_BAD_NETWORK_NAME({Network Name Not Found} The specified share name cannot be found on the remote server.)

Can you help me?

The POC required that the target is sharing its C:\ driver for remote connection.
For this you can right click on C: drive and in Properties there will be one option for sharing the drive, just select that.


MAINT: Use new conda envs w/ travis

Coverage remained the same at 100.0% when pulling 967c661f495695d4b71ed0145ee6788d1e2bc657 on jarvis into 9bfca99c3efc6fd59a373127860af0121196208e on master.


About visualizing the results according to log file

Hi Huang,
I want to ask about how to extract the training acc_avg and eval_avg of the log file and drow the line plot. I would really appreciate it if you could provide me with the code.

Hi,
You can consider using the dictionary saved with the model.
https://github.com/HanxunH/Unlearnable-Examples/blob/28e1e417259ce5baf0d3e68d3408d9f8ecc3024f/main.py#L84
https://github.com/HanxunH/Unlearnable-Examples/blob/28e1e417259ce5baf0d3e68d3408d9f8ecc3024f/main.py#L94
https://github.com/HanxunH/Unlearnable-Examples/blob/28e1e417259ce5baf0d3e68d3408d9f8ecc3024f/main.py#L120


adding update method for Groups

Thanks! From what I remember, the endpoint didn't exist in Gitlab at the time!


GEODE-7319:Replace mock EntryEventImpl.class in problematic TCs

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

[*] Is your initial contribution a single, squashed commit?

[*] Does gradlew build run cleanly?

[*] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Hey @mivanac, jus a friendly reminder: everyone, even committers, should wait for at least one positive review (aka approval) before merging PRs into develop, even when those PR are only related to changes in test classes.
And congratulations for becoming for a Geode committer, BTW!.


Dark mode background color not applying when body styles are extracted using @apply

I have this in my globals.css:
body {   @apply font-body antialiased max-w-xl mx-auto text-gray-900 bg-white dark:bg-gray-800 dark:text-white transition-colors; }
And it works in the old way, but with JIT, it doesn't apply the dark:bg-gray-800, while the dark:text-white works fine.
The result is white text on a white background in dark mode.
Background colour changes to other elements apply fine, only body is unaffected.

Hey! Can you provide an actual reproduction repository I can test locally so I can more easily troubleshoot?

I tried to create a clean example but in either case (Normal or JIT) I get a warning like this.
The dark:bg-gray-800 class does not exist,... on all dark: classes in the @apply
Which is a shame as this works fine in my existing project.

You have no darkMode setting in your config file. Set that to "media" or "class" and you should be good to go.

It doesn't make any difference, but if this operator error in some other way, I'll live with that.

I have the same issue. I've created a reproduction: https://github.com/alizahid/tailwind-jit-dark-bug
Also something to note, while I was creating the repo, it worked as intended once, and then on restart, it broke again. Tried deleting .next but that had no effect.

@alizahid thanks for the reproduction! It looks like if I change scss to css it works, but I really can't for the life of me trace it down to something simple.
Another thing that fixes it is using a single CSS file instead of important tailwindcss/tailwind.css and globals.scss separately:
// globals.scss
// fonts

@import url('https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@400;500;600&family=IBM+Plex+Mono:wght@400;500&display=swap');

@tailwind base;
@tailwind components;
@tailwind utilities;

// global

::selection {
  @apply bg-emerald-100 dark:bg-emerald-900 text-black dark:text-white;
}

body {
  @apply cursor-default antialiased bg-white dark:bg-black text-black dark:text-white;
}

a {
  @apply transition-colors text-emerald-600 dark:text-emerald-500 hover:text-emerald-500 dark:hover:text-emerald-400;
}

Honestly at a loss here, really can't boil this down to a small reproduction.
@david-buck can you provide a reproduction for your original issue so I have something to compare it to?

@david-buck For what it's worth using the code you provided, I get the expected output:

@adamwathan I can live with tailwind directives in my global.scss if that fixes the issue.

I migrated an existing Rails 6 app to Webpacker 6 and am noticing this same behavior with SCSS.  Anything declared in a body CSS selector was getting removed.  If I put text-gray-800 dark:text-gray-200 on the body element's class it was working.  But not with...
body {
  @apply text-gray-800 dark:text-gray-200;
}

I fixed SCSS issues with moving my postcss configuration out of webpack and into postcss.config.js.
The other thing that's been tripping me up on one of my projects is that there must be a recent update where you need to be explicit for dark values. For example bg-white bg-opacity-50 dark:bg-blue-500 used to make the dark background also have 50% opacity... but now I need to be explicit: bg-white bg-opacity-50 dark:bg-blue-500 dark:bg-opacity-50. The old version was intuitive to me because of the nature of native css fallbacks, but the new explicit method makes perfect sense for a utility-based css framework.
All is good now (at least in my case)!

I've noticed another behavior; if I have any colors defined in tailwind.config.js and I change them (change values, add, remove), the changes aren't reflected in styles defined in my .scss files but work in my React components. I need to restart Next.js server for my stylesheets to update.


Not compatible with 10.11.1

Won't work for me withe the error above

Same here
I was available to install, but not to play them

after a reboot and a second install as single user, it works

It works for me, installed for all users, 10.11.1 (15B42)

Works for me too on 10.11.1.

I ran re-installed, and it worked on the 2nd try

Closing as working for @Scirocco3


fix many bugs found by me, and reports by others in official repo.

fix many bugs found by me, and reports by others in official repo.

I can't find an implementation for DetourUpdateAllOtherThreads
Please keep the source files in ASCII only
Your code should support VC6 (sadly)
Some of the issues already have pending PRs, for example #81
It was decided to prefer using CMake over VS as build system, so it would probably be best to remove your VS solution in favor of #48
Also nitpick: your memory allocation code invokes UB, you should use placement new.

It is is great to see this submissioj, thanks!
It is better to have separate commits for separate bugs. This makes it easier to test the changes and debug them later, if something breaks. I noticed that you are fixing some uninitialized variables, for example. Could you break this up into a commit per bug? Things like fixing uninitialized variables can all be part of one commit.

I have been maintaining my own modified version of Detours for many years, but it has not been open source for a long time. Today I just released the code repo open source, so it may not be good to submit it step by step now, but I am sure there is no problem with this latest modified version. Since I've been using this latest code in my products for a while now, a lot of my software use my modified version of Detours. Including https://github.com/sonyps5201314/SocksCapEx2.

I can't find an implementation for DetourUpdateAllOtherThreads
Please keep the source files in ASCII only
Your code should support VC6 (sadly)
Some of the issues already have pending PRs, for example #81
It was decided to prefer using CMake over VS as build system, so it would probably be best to remove your VS solution in favor of #48
Also nitpick: your memory allocation code invokes UB, you should use placement new.

The VS solution is designed to make it easier for me and other users to see, modify, and debug the code.You can merge the changes, remove them and commit the result.
Use own memory allocation management functions rather than the CRT is for the sake of compatible DetourUpdateAllOtherThreads function, because the CRT lock memory allocation function, using DetourUpdateAllOtherThreads, if the current process exists the other thread, the thread will suspend operation, if the suspended thread at the moment have the CRT memory allocation locks, we continue call the CRT functions like 'new/malloc' will lead to a deadlock problem.
This is a fix for #70

Placement new does not involve a CRT-lock, it just makes the code well defined by calling the T constructor.

your meaning is add a new/new[] operator overloading for some class? If this is your meaning, but there are many code use new/delete to  manage BYTES memory:
rlpDlls = new NOTHROW LPCSTR [s_pHelper->nDlls]; in DetourFinishHelperProcess
Helper = (PDETOUR_EXE_HELPER) new NOTHROW BYTE[sizeof(DETOUR_EXE_HELPER) + cSize]; in AllocExeHelper
,these codes will use global new function, global new function is a simple call to malloc.
I decided to do this only when my actual tests found that there was a deadlock problem if I didn't use my own memory allocation function, rather than just extrapolating and guessing. All the official examples and all the code you can find on the web are basically calling DetourUpdateThread(GetCurrentThread()); So this problem didn't break out, and other HOOK libraries like Mhook  have noticed this problem, so they also use their own memory management functions.

No, I mean placement new.
T* thing = new (ptr) T;

This syntax calls the constructor of T at the address ptr and returns a pointer to the newly-constructed object. It does not involve allocation or overloading. Just casting the result of HeapAlloc is undefined behavior.
However, after looking at your code more closely, I notice that you had already done that, because I previously only looked at the cast. But one issue is that you should technically only access the new object through the return value of placement new, because that's the only safely derived pointer. I would suggest to rewrite the functions like this:
template<class T, class Arg>
T* DetourCreateObject(Arg arg)
{
	void* p = HeapAlloc(DetourGetHeap(), 0, sizeof(T));
	if (!p)
	{
		return NULL;
	}

	return ::new(p) T(arg);
}

Also, in DetourDestroyObject p should probably be taken by reference so that the final p = NULL; assignment is propagated to the caller.

No, I mean placement new.
T* thing = new (ptr) T;

This syntax calls the constructor of T at the address ptr and returns a pointer to the newly-constructed object. It does not involve allocation or overloading. Just casting the result of HeapAlloc is undefined behavior.
However, after looking at your code more closely, I notice that you had already done that, because I previously only looked at the cast. But one issue is that you should technically only access the new object through the return value of placement new, because that's the only safely derived pointer. I would suggest to rewrite the functions like this:
template<class T, class Arg>
T* DetourCreateObject(Arg arg)
{
	void* p = HeapAlloc(DetourGetHeap(), 0, sizeof(T));
	if (!p)
	{
		return NULL;
	}

	return ::new(p) T(arg);
}

Also, in DetourDestroyObject p should probably be taken by reference so that the final p = NULL; assignment is propagated to the caller.

I decide to not use reference to DetourDestroyObject parameter,  Since I found Detours to be well programmed, and its delete operation was mostly follow a reset pointer operation like below code, I did not set it to reference type in order to change Detours code as little as possible.
CImageImportFile::~CImageImportFile()
{
    if (m_pNextFile) {
        delete m_pNextFile;
        m_pNextFile = NULL;
    }
    if (m_pImportNames) {
        delete[] m_pImportNames;
        m_pImportNames = NULL;

If DetourDestroyObject' parameter was set to reference type,  the codes like 'm_pImportNames = NULL;'  should be remove for for the sake of efficiency, and I found many similar code existed.  so I decide to do not use reference at that moment, you are official , you have many high rights to decides to remove these junk code if change p to reference type.

No, I mean placement new.
T* thing = new (ptr) T;

This syntax calls the constructor of T at the address ptr and returns a pointer to the newly-constructed object. It does not involve allocation or overloading. Just casting the result of HeapAlloc is undefined behavior.
However, after looking at your code more closely, I notice that you had already done that, because I previously only looked at the cast. But one issue is that you should technically only access the new object through the return value of placement new, because that's the only safely derived pointer. I would suggest to rewrite the functions like this:
template<class T, class Arg>
T* DetourCreateObject(Arg arg)
{
	void* p = HeapAlloc(DetourGetHeap(), 0, sizeof(T));
	if (!p)
	{
		return NULL;
	}

	return ::new(p) T(arg);
}

Also, in DetourDestroyObject p should probably be taken by reference so that the final p = NULL; assignment is propagated to the caller.

I create DetourCreateObject function like ATL collections classes, so I think it is no problem at that mement, the code like
the below code in ATL of VS2019 and so on.
template< typename E, class ETraits >
typename CAtlList< E, ETraits >::CNode* CAtlList< E, ETraits >::NewNode(
	/* _In_ */ INARGTYPE element,
	_In_opt_ CNode* pPrev,
	_In_opt_ CNode* pNext)
{
	GetFreeNode();

	CNode* pNewNode = m_pFree;
	CNode* pNextFree = m_pFree->m_pNext;

	::new( pNewNode ) CNode( element );

	m_pFree = pNextFree;
	pNewNode->m_pPrev = pPrev;
	pNewNode->m_pNext = pNext;
	m_nElements++;
	ATLASSUME( m_nElements > 0 );

	return( pNewNode );
}

@sylveon and the VS solution is not conflicting, it only call the below code:
SET DETOURS_TARGET_PROCESSOR=XXX
cd ..
nmake

but exist it will friend for edit, modify and debug code in Detours.


perf: optimize msm gpu memory usage

Description
This PR is a performance improvement that allows the base to be recycled after initial allocation without reallocating when using MSM GPU in kzg commitment scheme.

@GideokKim "feat(math): add base copy option change" What does this commit message mean? I really can't relate well with the diff.

f26c389: refac(device): refac(device): -> refac(device):

Please remove scope from feat(crypto/zk): add gpu memory accessor functions

Please change c to c/zk in feat(c): modify commit functions with gpu support


Docker SD missing service: and container: networking modes

What did you do?
Using Docker Compose, I have two containers, summarized here:
- container_name: mysql
  hostname: mysql
  image: mysql:5
  networks:
    private: {}

- container_name: exporter__mysql
  depends_on:
    - mysql
  image: prom/mysqld-exporter
  network_mode: service:mysql

My goal is to have a Pod-like ability to hit the mysql container on both ports 3306 (MySQL traffic), and 9104 (exporter traffic).
What did you expect to see?
That exporter__mysql would show up as discoverable within Prometheus's Service Discovery, which I could then further filter labels and select.
What did you see instead? Under which circumstances?
When I view all containers discovered by Prometheus using the Docker socket, it does not include the exporter__mysql container. I've tried both network_mode: service:mysql, as well as network_mode: container:mysql and neither work. If I move exporter__mysql to the private network in which mysql is running (network: private), then it shows up in Prometheus Docker socket discovery.
I thought I might be running into #7684, which indicates that containers need to expose ports:

It looks like your services are not exporting any ports, which is why they do not appear in service discovery.

But I confirmed that the running container is exposing 9104 and that I could hit it using the mysql hostname:
$ docker inspect exporter__mysql | jq -r '.[].Config.ExposedPorts'
{
  "9104/tcp": {}
}

$ docker run -it --rm --net private alpine wget -qO- mysql:9104/metrics | wc -l
1920

Environment

System information:

$ uname -srm
Linux 5.4.0-91-generic x86_64

Prometheus version:

$ docker exec -it prometheus prometheus --version
prometheus, version 2.32.1 (branch: HEAD, revision: 41f1a8125e664985dd30674e5bdf6b683eff5d32)
  build user:       root@54b6dbd48b97
  build date:       20211217-22:08:06
  go version:       go1.17.5
  platform:         linux/amd64

Prometheus configuration file:

global:
  scrape_interval:     15s
  evaluation_interval: 15s

scrape_configs:
  - job_name: 'docker-containers'
    docker_sd_configs:
      - host: unix:///var/run/docker.sock
    relabel_configs:
      # Select containers whose name is prefixed by `exporter__`.
      - source_labels: [__meta_docker_container_name]
        regex: /exporter__.+ # For some reason, container names begin with a '/' character.
        action: keep
      # Create new label named 'container' with the value from the meta container name label.
      - source_labels: [__meta_docker_container_name]
        target_label: container
        regex: /(.+)

Note: The above config works for other exporters which aren't tied to specific services. I am successfully running and scraping metrics for the Node and cAdvisor exporters. The issue is that the Docker socket service discovery is outright missing containers who share network namespaces with other containers.

Logs:

No issues:
ts=2022-01-08T08:49:17.468Z caller=main.go:1129 level=info msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml
ts=2022-01-08T08:49:17.469Z caller=main.go:1166 level=info msg="Completed loading of configuration file" filename=/etc/prometheus/prometheus.yml totalDuration=773.879µs db_storage=1.63µs remote_storage=1.563µs web_handler=679ns query_engine=1.434µs scrape=333.957µs scrape_sd=74.472µs notify=11.014µs notify_sd=6.806µs rules=1.385µs

Is there any chance that you could dump the http requests between Docker and Prometheus?

@roidelapluie, I can try. Do you have thoughts on this? I'm thinking to just make either a nc or socat socket, change Prometheus to point at that TCP endpoint, dump the data to a file, and then filter the data in Wireshark or something. Is there anything more straight forward? I was looking at just strace'ing the prometheus process, but I saw a bunch of byte-like data and I'm not sure how to interpret it, or if it's something that strace can output correctly.

You could enable the http listener and use Wireshark

I finally got around to dumping this information. I will skip the tcpdump set up for now as I believe we can focus on the relevant data in the response from the Docker daemon. (Let me know if you want these details.)

I am including three containers from the Docker daemon response to Prometheus:

mysql: Actual MySQL container.
exporter__mysqld: The Prometheus MySQL exporter, associated with the mysql container's network.
exporter__mysql: A simple container that proxies connections to exporter__mysqld.

Restating the problem:

exporter__mysqld does expose scraped metrics at http://mysql:9104/metrics, but Prometheus doesn't list it in Service Discovery (or Targets).
exporter__mysql is a separate container in my private network which just proxies to http://mysql:9104/metrics, and Prometheus does list it in Service Discovery (and Targets).

This is how I've been able to monitor my DB up until now, I've just been using exporter__mysql. I'd like to remove this container and have Prometheus "see" exporter__mysqld.
Docker daemon response to Prometheus:

mysql
{
  "Id": "b3141ee0925b9075c75dfce62673ef8dd17f60d15f65cf34b670fd8d9010bc42",
  "Names": [
    "/mysql"
  ],
  "Image": "mysql:5",
  "ImageID": "sha256:42f82e150ec28054e528d2de42299225b0985530bc7e2f688941e5e323b372f3",
  "Command": "docker-entrypoint.sh mysqld",
  "Created":<PHONE_NUMBER>,
  "Ports": [
    {
      "PrivatePort": 3306,
      "Type": "tcp"
    },
    {
      "PrivatePort": 33060,
      "Type": "tcp"
    }
  ],
  "Labels": {
    "_ServiceDirectory": "mysql",
    "com.docker.compose.config-hash": "d73015df2d6348ce790e352370149c2201d917e07be58d035dccc8592cf75e5a",
    "com.docker.compose.container-number": "1",
    "com.docker.compose.oneoff": "False",
    "com.docker.compose.project": "REDACTED",
    "com.docker.compose.project.config_files": "REDACTED",
    "com.docker.compose.project.working_dir": "REDACTED",
    "com.docker.compose.service": "mysql",
    "com.docker.compose.version": "1.28.0"
  },
  "State": "running",
  "Status": "Up 10 days",
  "HostConfig": {
    "NetworkMode": "private"
  },
  "NetworkSettings": {
    "Networks": {
      "private": {
        "IPAMConfig": null,
        "Links": null,
        "Aliases": null,
        "NetworkID": "94389f46d90210bf321c13edef8290ad64d177f385affdd614951a55795dd0b8",
        "EndpointID": "421981ddc5ea37102ceaacded364c53332a4e1d16ba4802301b39bb56d2ca211",
        "Gateway": "<IP_ADDRESS>",
        "IPAddress": "<IP_ADDRESS>",
        "IPPrefixLen": 24,
        "IPv6Gateway": "",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "MacAddress": "02:42:c0:a8:e0:2c",
        "DriverOpts": null
      }
    }
  },
  "Mounts": [
    {
      "Type": "bind",
      "Source": "/docker/mysql/data",
      "Destination": "/var/lib/mysql",
      "Mode": "rw",
      "RW": true,
      "Propagation": "rprivate"
    }
  ]
}

exporter__mysqld
{
  "Id": "b2fe1b66a5a5dc474e74697f83ed47a80e57c6c50f94d0c2b2b250dd31bfb698",
  "Names": [
    "/exporter__mysqld"
  ],
  "Image": "prom/mysqld-exporter",
  "ImageID": "sha256:6af217645de36e69042e63c3f784f10fcee300b5fa9ee768c55f5f0a08a85bd6",
  "Command": "/bin/mysqld_exporter",
  "Created":<PHONE_NUMBER>,
  "Ports": [],
  "Labels": {
    "_ServiceDirectory": "prometheus",
    "com.docker.compose.config-hash": "54109a67f77211352685164f37f391d3a80ecc2197e0111815603b951e17930a",
    "com.docker.compose.container-number": "1",
    "com.docker.compose.oneoff": "False",
    "com.docker.compose.project": "REDACTED",
    "com.docker.compose.project.config_files": "REDACTED",
    "com.docker.compose.project.working_dir": "REDACTED",
    "com.docker.compose.service": "exporter__mysqld",
    "com.docker.compose.version": "1.28.0",
    "maintainer": "The Prometheus Authors<EMAIL_ADDRESS>  },
  "State": "running",
  "Status": "Up 13 minutes",
  "HostConfig": {
    "NetworkMode": "container:b3141ee0925b9075c75dfce62673ef8dd17f60d15f65cf34b670fd8d9010bc42"
  },
  "NetworkSettings": {
    "Networks": {}
  },
  "Mounts": []
}

exporter__mysql
{
  "Id": "821c10c99be8b22748f5d89a16a14f51589f305fac6eb079a8f12f2276eeef23",
  "Names": [
    "/exporter__mysql"
  ],
  "Image": "alpine/socat",
  "ImageID": "sha256:747019af87763d9bbe3e1645e0a714828176314503224192132b1648ccd2e991",
  "Command": "socat TCP-LISTEN:9104,reuseaddr,fork,su=nobody TCP:mysql:9104",
  "Created":<PHONE_NUMBER>,
  "Ports": [
    {
      "PrivatePort": 9104,
      "Type": "tcp"
    }
  ],
  "Labels": {
    "_ServiceDirectory": "prometheus",
    "com.docker.compose.config-hash": "93a18b0f7981b48eb7e6228343ac7aea84d0d7bb9d631131c3f3608cb4b6eb10",
    "com.docker.compose.container-number": "1",
    "com.docker.compose.oneoff": "False",
    "com.docker.compose.project": "REDACTED",
    "com.docker.compose.project.config_files": "REDACTED",
    "com.docker.compose.project.working_dir": "REDACTED",
    "com.docker.compose.service": "exporter__mysql",
    "com.docker.compose.version": "1.28.0"
  },
  "State": "running",
  "Status": "Up 10 days",
  "HostConfig": {
    "NetworkMode": "private"
  },
  "NetworkSettings": {
    "Networks": {
      "private": {
        "IPAMConfig": null,
        "Links": null,
        "Aliases": null,
        "NetworkID": "94389f46d90210bf321c13edef8290ad64d177f385affdd614951a55795dd0b8",
        "EndpointID": "9869dba83d73006c0f55660c6d91744dc05e8bdc0af47c263fdafb4055714251",
        "Gateway": "<IP_ADDRESS>",
        "IPAddress": "<IP_ADDRESS>",
        "IPPrefixLen": 24,
        "IPv6Gateway": "",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "MacAddress": "02:42:c0:a8:e0:29",
        "DriverOpts": null
      }
    }
  },
  "Mounts": []
}

So the fact that the Docker daemon is responding with (accurate) data for exporter__mysqld, I think it's either a bug with Prometheus, or something else in my config is causing this to not show up under Service Discovery (or Targets).

@roidelapluie Would you take a look at https://github.com/prometheus/prometheus/pull/10490 which should closes this issue?

I experience the same issue, are there any news?

I have the same issue.Is the issue fixed?

Hello from the bug scrub!
https://github.com/prometheus/prometheus/pull/10490 has finally been merged. (It has an issue of its own, but that's already been worked on.) We'll close this issue for now. Please follow up if you still have problem (using v2.54+).


Unused global scoped private variables / constants are not caught by the analyzer

Just noticed that unused private global variables / constants are not caught by the analyzer.
Since these are meant to be only used within the same source file, I would expect these would be detected as UNUSED_ELEMENT and be reported by the analyzer.

I'm sure this exists somewhere already, but I totally agree.


Allow parsing cookies with equal character in the value

From<EMAIL_ADDRESS>on February 11, 2012 12:17:06
E.g. JSESSIONID=9HTaCatOIaiO7ccHojDzuxwVoIU=
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=159

From<EMAIL_ADDRESS>on February 11, 2012 03:19:18
Status: Fixed

From<EMAIL_ADDRESS>on February 15, 2012 06:17:32
Issue 158 has been merged into this issue.


fixed mobile view of judgment party table where the last column words…

Fixed mobile view of judgment party table where breaking into two lines, also moved the centered text to the left a little as a layout compromise to enable the fix

Changes in this PR:
Trello card / Rollbar error (etc)
https://trello.com/c/qq5DbMaK/116-reduce-party-wrapping-on-mobile
Screenshots of UI changes:
Before

After

Codecov Report

Merging #481 (efed86c) into main (3300b9b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #481   +/-   ##
=======================================
  Coverage   77.51%   77.51%
=======================================
  Files          12       12
  Lines         636      636
  Branches       43       43
=======================================
  Hits          493      493
  Misses        131      131
  Partials       12       12

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


useCroct breaks on server-side

🐞 Bug report
The useCroct hook throws an error on SSR, even when used in client-side callbacks.
Steps to reproduce
import React, { useCallback } from 'react'
import { useCroct } from '@croct/plug-react'

export default function BuyButton({ slug }) {
    const croct = useCroct()
    const trackPurchaseIntentionsWithCroct = useCallback(() =>
        croct.tracker.track('goalCompleted', { goalId: slug })
    , [croct])

    return (<button onClick={trackPurchaseIntentionsWithCroct}>Comprar</button>);
}

Expected behavior
No error.
Screenshots

It was fixed in the latest version.


UX Improvement for Settings Page

Problem:
Many users are not aware that some options in the Settings->Device page are actionable beyond the CTA's (Call to Action) that are on the far right. This paradigm is not consistent in the UI since not all areas of the UI will behave the same despite not having any differentiating visual cues.
Refer to:

When Driver Camera area is tapped, more information can be expanded
When Camera Calibration is tapped, information regarding the accuracy of the mount is displayed for users to understand how well they have installed the device and is also great information to share when troubleshooting.

Solution:
Place a visual signifier beside the options that can be expanded, so users know that specific line is different from the rest. Please examples below:

Note:
Space between text and icon/symbol should be at the minimum 3 spaces so eligibility between text and icon/symbol is retained.
This is just an interim solution until Comma rolls out their new UI, but just like Comma is a shippable intermediary, this simple UI change can benefit the customers and users of OpenPilot in the short term.
Resources:
https://www.compart.com/en/unicode/U+24D8
https://www.compart.com/en/unicode/U+2304

We've decided to not ship intermediate design changes like this until we have the time for a proper design refresh.


Update NMT client to log latency

Adds changes needed to get latency for the s2s and s2t usecase, also cleans up unused variables.

Looks good


Finish changing hostname from aegir.docker to aegir.local.computer

The default hostname for Aegir was changed to aegir.local.computer.  This completes it by setting the defult AEGIR_CLIENT_EMAIL and updating the README.

Thanks


[Bit] add bit components count service

add badge show Bit (bit.dev) components count

Deploying a review app @ https://shields-staging-pr-3338.herokuapp.com/

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @guysaar223!

  Generated by :no_entry_sign: dangerJS against 47318b046a0279e9bf51c9277a7a7f14bc2b0c6b

Everything looks good! Can you envision any potential other bit related badges being of value down the road?
It looks like there are are some component level data points (looks like there's a status, download count, license, etc.) that I could potential see folks wanting badges, and perhaps user/profile info as well (# of collections for a profile, # of contributors, etc.).
If so then we may want to think through the badge route a bit before merging to see if  /bit/components is still best route

Everything looks good! Can you envision any potential other bit related badges being of value down the road?
It looks like there are are some component level data points (looks like there's a status, download count, license, etc.) that I could potential see folks wanting badges, and perhaps user/profile info as well (# of collections for a profile, # of contributors, etc.).
If so then we may want to think through the badge route a bit before merging to see if /bit/components is still best route

I think we can change the route to
`/bit/total-components
what do you think ?

I think we can change the route to
`/bit/total-components
what do you think ?

Is my understanding correct that the badge being added here is showing the total number of components in a collection? (again apologies as I am not familiar with bit.dev at all)

I think we can change the route to
`/bit/total-components
what do you think ?

Is my understanding correct that the badge being added here is showing the total number of components in a collection? (again apologies as I am not familiar with bit.dev at all)

exactly

Our badge routes should follow the pattern /service/noun/parameters/qualifiers
In this instance, the service is bit and the noun would be collection IMO, so I would suggest:
/bit/collection/total-components/...
That pattern should hold up well if we need to add badges for other nouns down the road (component, user, etc.) as well as additional metrics/measures for collections

Our badge routes should follow the pattern /service/noun/parameters/qualifiers
In this instance, the service is bit and the noun would be collection IMO, so I would suggest:
/bit/collection/total-components/...
That pattern should hold up well if we need to add badges for other nouns down the road (component, user, etc.) as well as additional metrics/measures for collections

agree, I have been changed it to:
/bit/collection/total-components/...


deprecated URIs

Deprecated URIs shouldn't happen, but have and will happen.
It would be good to have a way for a profile to identify URIs that a LRP implementing a profile shouldn't use, but which a LRC reading statements conforming to profile (possibly including earlier versions) will need to support.

One, I think adding a deprecation property is definitely a good idea.
Two, I think a good approach for your scenario is define a first version of the profile with the old URIs, already marked as deprecated, then define a new version of the profile with the new URIs (and the appropriate relations, notably exactMatch from the new URIs to the old URIs). Then anyone still using the old ones can use the old version, but authoring tools and such will hopefully clearly note deprecation, and everything's able to easily discover both the current preferred terms and their connections to the old terms.

Reading about 'exactMatch' was what inspired this thought, but that's specifically for "other profiles". Do old versions count as other profiles? Or do we need an "exact" property?

Yeah, another version would also be when the *Match options would be used, though between versions of the profile only exactMatch and maybe relatedMatch should be used.


Fix latest-pinned syntax

Thanks! I'm obviously not running v1 locally and it looks like github actions have always used that latest:# syntax :)


Add new board

I added my board to platform.ini, it is verified to work with the code.
Also added this board to README.md, switched to show boards as a list.
Review the changes and merge if you agree.

Thanks for the update - Great to hear that it's running your board!


Use attrs for object creation and cattrs for serialization

After running into some issues, and then really digging into the dataclasses_json code, I don't feel that good about depending on it. cattrs is a more robust project and I think that depending on attrs for dataclass-style classes is just fine. This PR converts all the existing classes to attrs and cattrs.
A few specifics:

New APIClient methods, .create() and .update() have been created, which can take an instance of <Entity> and either create or update the entity on CellEngine. This does not deprecate .create_<entity>(), which I think is still useful. This change was driven by the need to be able to create several Gates, then post them all at once, which disrupts the otherwise-fine flow of "one Entity corresponds to the same object on CE".

Additionally, it adds a self.client property to all standard classes for accessing APIClient; maybe later I will stop getting the Singleton client class from the global scope via ce.APIClient() and will instead just pass the client object around. This is what Google does.
I also removed custom_inherit as a dependency, because passing *args, **kwargs to the wrapped function makes mkdocs build --strict throw an error that I couldn't get around. Instead, I've just added a docstring that links in mkdocs to the relevant Gate classmethod.
Alternatives for serialization are:

marshmallow
pydantic
dataclasses
nothing at all, custom __init__ methods

Looks like this needs a rebase. Are you ready for review otherwise?

Not quite, almost

Superseded by the other PRs, yeah?


Support a wide range of Guava versions

Use GuavaCompatibility helper class from com.datastax.cassandra:cassandra-driver-core to support a wide range of Guava versions.
Avoid java-cassandra-driver preventing consumers from upgrading Guava.
From com.datastax.driver.core.GuavaCompatibility:
/**
 * A compatibility layer to support a wide range of Guava versions.
 *
 *
The driver is compatible with Guava 16.0.1 or higher, but Guava 20 introduced incompatible
 * breaking changes in its API, that could in turn be breaking for legacy driver clients if we
 * simply upgraded our dependency. We don't want to increment our major version "just" for Guava (we
 * have other changes planned).
 *
 *
Therefore we depend on Guava 19, which has both the deprecated and the new APIs, and detect
 * the actual version at runtime in order to call the relevant methods.
 *
 *
This is a hack, and might not work with subsequent Guava releases; the real fix is to stop
 * exposing Guava in our public API. We'll address that in version 4 of the driver.
 */

https://datastax-oss.atlassian.net/browse/JAVA-1928

Pull Request Test Coverage Report for Build 89

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.979%

Totals

Change from base Build 88:
0.0%

Covered Lines:
227

Relevant Lines:
239

💛  - Coveralls


[Parsing error] Function call in parameter default value is not supported

The following piece of code does not parse:
class ssh (
  $domain_name = hiera('abc'),
) {}

@racodond This should now work as expected, can you confirm?

I confirm. Thanks!
I added a specific unit test for PARAMETER: https://github.com/iwarapter/sonar-puppet/commit/c3da6c4c0cf7549586a3a110305c8d17c588f72a

:+1:


Lack of Support for OAuthBearer Mechanism with SASL_PLAINTEXT Protocol in Klaw

What is currently missing?
Klaw currently lacks support for the OAuthBearer mechanism with the SASL_PLAINTEXT protocol for Kafka. Specifically, the sasl.login.callback.handler.class property, which is required to configure the OAuthBearer mechanism, is not currently configurable within Klaw. This limitation prevents users from successfully connecting to Kafka clusters that utilize OAuthBearer authentication.
How could this be improved?
To address this issue, Klaw should be updated to include support for the OAuthBearer mechanism by allowing the configuration of the sasl.login.callback.handler.class property. This enhancement would enable users to authenticate with Kafka clusters using OAuthBearer and the SASL_PLAINTEXT protocol.
Is this a feature you would work on yourself?
Yes, I am interested in working on this feature. I have already tested the necessary changes locally and am prepared to contribute these updates to the open-source project.

@rkyadav271098 very impressive that you have raised this issue and already have a working version of it.
Indeed, OAuthBearer mechanism is not supported in klaw., I assume it's relatively a minor change in klaw cluster api to handle the new mechanism.
Pls submit a pr whenever you are ready.


Snapshots of recent heights

To provide atomic queries, it will probably be useful to keep snapshots of recent states (say, for all blocks from the last minute). Then we can resolve queries against a given height as long as it is in snapshot range.
Since RocksDB snapshots are lost on restart, we will either have to not guarantee recent states are snapshotted (e.g. when resetting) or replay blocks to build them. I would lean toward the former since any new queries will be against the most recent block which will always have a snapshot (there is only a window of a few seconds after starting a node when there are no snapshots, clients can just retry).

This is done


Fix faulty check in estimateGas

Description
This PR fixes a few faulty checks inside eth_estimateGas, namely:

If the transaction has a value of 0 and the account has a balance of 0, this shouldn't be a reason to fail
EVM application errors were not being taken into account during transaction execution

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[x] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[x] I have added the relevant labels
[ ] I have updated the official documentation
[x] I have added sufficient documentation in code

Testing

[x] I have tested this code with the official test suite
[x] I have tested this code manually

Manual tests
Account balance fix
An easy way to test this out would be to send transactions from an account that has 0 balance, and the value of the transaction being 0.
EVM reverts fix
To test out the EVM revert error fix during eth_estimateGas, a dummy SC can be deployed with a method that always fails (for example, it has a require statement that is always triggered), and eth_estimateGas called on a transaction that calls that method - the call should fail, and not return a gas estimate value.
Additional comments
Fixed EDGE-403

Closing in favor of https://github.com/0xPolygon/polygon-edge/pull/422


Allow verbose mode

I'm not sure that the default silence is really what I desire. Perhaps verbosity should be the default. In any case, at least allowed. You know, builds can fail. It happened to me just know, trying to use cargo bin makers. It's from the crate cargo-make which failed to build because of missing native dependencies. But I had to guess that and try to install it using good old cargo install, to find out why it's not compiling.

Fixed in v1.0.0. Thanks for the recommendation!

Thank you!


Matcher: haveLayoutConstraint

I'm trying to test that NSLayoutConstraints that have been added programmatically are being set.
I've created the following custom matcher:
#import "EXPMatchers+hasLayoutConstraint.h"

EXPMatcherImplementationBegin(hasLayoutConstraint, (NSLayoutConstraint *expected)) {

  match(^BOOL {

    for (NSLayoutConstraint *item in actual)
    {
      if (item.firstItem == expected.firstItem &&
          item.firstAttribute == expected.firstAttribute &&
          item.relation == expected.relation &&
          item.secondItem == expected.secondItem &&
          item.secondAttribute == expected.secondAttribute &&
          item.multiplier == expected.multiplier &&
          item.constant == expected.constant) {
        return YES;
      }
    }

    return NO;
  });

  failureMessageForTo(^NSString * {
    return @"The layout constraint is not found;";
  });

  failureMessageForNotTo(^NSString * {
    return @"The unexpected layout constraint was found in the given array.";
  });
}
EXPMatcherImplementationEnd

If this would be useful to anyone else, I'd love to see it implemented.

Think this would make a good standalone library ( with some more auto layout specific DSLs! )
So I'm closing the issue on getting it into master.


Source for Heat map calendar example

Hi,
Can I get the link to the source code of the calendar heat map image shown in the Introduction part?
If not, a link to any heat map example would be great. Thanks

https://github.com/nicgirault/circosJS/blob/master/demo/heatmap.js


Seats.io chart is not loading in release apk of react native android.

I have called the below code in the SeatsioSeatingChart.js file inside the render function.
        style={{ flex: 1, backgroundColor: 'yellow', alignSelf: 'stretch' }}>
        <WebView
          ref={(r) => (this.webRef = r)}
          originWhitelist={['*']}
          // source={{ html: this.html() }}
          source={{ uri: 'file:///android_asset/seats.html' }}
          style={{ width: 370, height: 300, backgroundColor: 'lightblue' }}
          domStorageEnabled={true}
          javaScriptEnabled={true}
          // injectedJavaScriptBeforeContentLoaded={this.pipeConsoleLog()}
          onMessage={this.handleMessage.bind(this)}
        />
      </View>

I see you replaced the source with file:///android_asset/seats.html, are you sure that file is being resolved correctly? And that it contains the correct code?
I don't see why you would need to change the html source of the webview, tbh.

yes, I have to change this code bcoz it was not loaded the chart.
This is my HTML file, which I have put inside android/app/src/main/assets

    <title>seating chart</title>
    <meta name="transparent" content="true" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta name="theme-color" content="#000000" />

  </script>

No, if your chart is not loading, it's because of some other problem, not because the source html is not correct.
In your html (which is not well formed btw), you're never calling new seatsio.SeatingChart({...}).render(), so that cannot possibly work.

source HTML is correct, and also load while developing. It's only not showing in the release apk. when I run this apk I can see the logs inside the SeatsioSeatingChart.js file. I have put console logs inside componentdeiUpdate() and rerenderChart() method.

I'm sorry, but without this, the chart cannot possibly load.
I can only reiterate that A) you do not need to change the html source, and B) that if the chart does not load, then that's because of another reason.
Also, please note that this repo contains nothing more than a proof of concept: it's not an officially supported library. Will update the readme to make that more clear.


After vcpkg integrate install MSVS intellisence doesn't find header files

Describe the bug
After vcpkg integrate install MSVS intellisence doesn't find header files.
I try to write #include<boost/... and any suggestion appears.
When I put headers ignoring fact that intellisence can't find it - the intellisence could give correct suggestion for classes in that header and anything compiles good.
Environment

OS: Win10 (with last updates)
Compiler: MSVS2022 with last updates + Visual assist (last version)

To Reproduce
Steps to reproduce the behavior:
0. clone vcpkg repo

./vcpkg install boost
./vcpkg integrate install
I try typing #include<boost/... and nothing appears in the suggestion

Expected behavior
When I typing #include<boost/... - there should appears suggestions for boost libraries
Additional context
When I put headers ignoring fact that intellisence can't find it - the intellisence could give correct suggestion for classes in that header and anything compiles good.

@aPSopt Thanks for posting this issue, have you downloaded the build components? can you provide your project settings file? Is there a port for downloading the corresponding triplet?

I did the followed steps:

clone vcpkg in c:/d/ folder

set up followed environment variable for downloaded vcpkg:

install boost

made
vcpkg integrate install

made default msvs2022 console project
ConsoleApplication4.zip

And got the issue

Can you provide the components content of your Visual Studio Installer download?
for example: MSbuild、MSVC ... build tools、.NET 6.0 Runtime ...

Can you find vcpkg label in the project property page?

Can you provide the components content of your Visual Studio Installer download? for example: MSbuild、MSVC ... build tools、.NET 6.0 Runtime ...

Also I had installed

in scope of msvs2017
What else I can provide for help figure out issue?

Which triplet did you use and which configuration do your project use?

Triplet: x64-windows
Configuration: x64, debug, default msvs console application

Can you please complete a sample code, build it then provide the failure logs?

Test project you can find in attachment in my second comment from the top.
I note in initial message, that there are no any failure during build.
It is intellisence issue - doesn't works completion of include headers

Test project you can find in attachment in my second comment from the top. I note in initial message, that there are no any failure during build. It is intellisence issue - doesn't works completion of include headers

So maybe report to VS community instead?

I think this is the installation bug of vcpkg, isn't it?

If it builds and uses without any problems, it means that vcpkg has correctly set the additional include path. So this should be a VS intellisense issue.

This issue should be a Visual Studio C++ Intellisense issue, please open a feedback ticket in https://developercommunity.visualstudio.com/cpp/report.


Dev

Q
A

Bug fix?
no - yes?

New feature?
no - yes?

New sample?
no - yes?

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to Dev branch.

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

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;


UCF101 fails if root directory ends in "/"

Previously when the UCF101 dataset was trying to find indices, if the root directory given ended with "/" it would clip the first character of the string that it was looking for which would cause the dataset to fail.
For example, if the dataset was trying to check if "./ucf_data/videos/Bowling/v_Bowling_g06_c01.avi'" index should be added to the indices list, it would instead check if "owling/v_Bowling_g06_c01.avi' is in the set "selected_files".
Changing the 1: to a 0: would only allow root directories ending with "/" to pass. So instead I propose using the PathLib library when checking paths.

Is 2.7 support going to be dropped (given how 2.7 will be discontinued), or should I fix my solution?

I also had issues applying transforms when using the UCF101 dataset. I made some changes so that way this was not an issue. I also noticed that the changes I made could affect a few other datasets (kinetics and hmdb51), so I made changes in those files as well.

Thanks @Jbwasse2 for your contribution and sorry for the long delay before getting a reply.
As far as my understanding goes, this PR adresses two things at once:

fixing the problem with "/" as described in the PR
applying a transform frame by frame

Regarding the second point, there is a PR that is introducing a new way to decode video datasets so might become redundant. @pmeier probably has more details about this point.
As for the first point, there is currently an effort to migrate existing datasets to a new datasets API (as described here) and thus it might be best to wait for the migration before fixing the issue. The migration can be done by someone else of course @Jbwasse2 and due credit for identifying the bug and proposing a fix will be given to you.
Does that work for you @Jbwasse2?

@yassineAlouini given that this PR is ~2.5 years old, did you check if the problem actually persists? Regarding the other changes, we should follow the advice in https://github.com/pytorch/vision/pull/1703#discussion_r405534783 and not do this here. You are right that #5422 will make probably make it obsolete anyway.

@yassineAlouini given that this PR is ~2.5 years old, did you check if the problem actually persists?

That's a good point, I will check against the latest main branch and report back. :ok_hand:

Hello, thank you for the follow up. Your solution works for me.

As suggested @pmeier, I downloaded the dataset and tried a root path with an ending "/" and it did work (see screenshot below). Is that what you had in mind or do you have some additional tests I can try? Let me know since I have the dataset available now. :ok_hand:

Thanks for the follow-up @yassineAlouini. Since the issue seems to have been fixed in the mean time and other changes will be handled in #5422, I'm closing this PR. Thanks for the effort @Jbwasse2 and @yassineAlouini!


soc: nxp: lpc55s69: Add Sleep Mode to CPU0

Add sleep mode (corresponding to runtime idle in zephyr) to CPU0 on LPC55S69 to enable PM subsystem.

WIP because still needing to enable a system timer for sleep mode....


TC-CADMIN-1.9 is an invalid test case

first step：
sudo ./chip-tool pairing open-commissioning-window 1 1 900  1000 3228  --commissioner-name alpha
The maximum timeout of this step is 900S
second step：

On 2nd controller using chip-tool connect using wrong manual code. Repeat the step for 20 times.

sudo ./chip-tool pairing  code  2<PHONE_NUMBER>7 --timeout 3  --commissioner-name beta
But this step needs to wait for the device to time out, which takes about 50S for the device to time out. After 20 attempts, the total time exceeds 1000S, exceeding the 900S in the first step.
@bzbarsky-apple
@jepenven-silabs

@ChengqiangShe This command:
./chip-tool pairing code 2<PHONE_NUMBER>7 --timeout 3 --commissioner-name beta

should time out after 3 seconds, no?
In any case, bugs in test plans or test steps should be filed in https://github.com/CHIP-Specifications/chip-test-plans/issues/new/choose


Cron Allowed Pattern Expressions for Deploy.yaml in RedshiftAutomation conflict with

AllowedPattern: ^([0-59]|\*|\,|\-|\/) ([0-59]|\*|\,|\-|\/) ([0-59]|\*|\,|\-|\/|\?|L|W) ([0-59]|\*|\,|\-|\/) ([0-59]|\*|\,|\-|\/|\?|L|\#) ([0-59]|\*|\,|\-|\/)$
Valid cron expressions as defined by https://docs.aws.amazon.com/lambda/latest/dg/tutorial-scheduled-events-schedule-expressions.html do not pass validation
5 17 * * SAT * fails
The pattern should be updated to reflect the latest scheduled events expressions or better documentation should be provided to indicate why the allowed expressions pattern differs.

5 17 * * 6L * is the correct format

Why is this one closed? I am trying this patterns and they fail:
0 14 ? * SAT *
0 22 ? * SUN *
0 14 ? * TUE,THU *
0 14 ? * SAT *

Also with numbers instead of weekday string.
What am I doing wrong?

I've reopened the issue since this is still an issue with the existing templates.

I've already opened it, and I know why this happens:
https://github.com/awslabs/amazon-redshift-utils/issues/335


duplicate org name in guidance choices

see https://github.com/DMPbelgium/roadmap/issues/87

A bit more clarity:

on the plan edit page, you see a "short" list of available guidance groups, grouped by organization. We noticed that if the logged in user is of the same organization as one of the default organizations, that organization is listed twice in that list. Possible reason is here:

if @all_ggs_grouped_by_org.include?(current_user.org)
    # <- ADDED HERE
    @important_ggs << [current_user.org, @all_ggs_grouped_by_org[current_user.org]]
end
@default_orgs = Org.default_orgs
@all_ggs_grouped_by_org.each do |org, ggs|
    # <- ADDED HERE
    @important_ggs << [org, ggs] if @default_orgs.include?(org)

    # If this is one of the already selected guidance groups its important!
    @important_ggs << [org, ggs] if !(ggs & @selected_guidance_groups).empty? && !@important_ggs.include?([org, ggs])
end

Possibly fixed by applying @import_ggs.uniq! at the end?

The full list of guidance groups is fine, as that is not created with previous logic, but from the database itself.

Just noticed this while doing the upgrade to v4.0.0. I guess the duplicate choice occurs when @default_orgs.include?(current_user.org) evaluates to true.
Maybe the entire code snippet you shared could be refactored to something like the following?:
BEFORE
if @all_ggs_grouped_by_org.include?(current_user.org)
    # <- ADDED HERE
    @important_ggs << [current_user.org, @all_ggs_grouped_by_org[current_user.org]]
end
@default_orgs = Org.default_orgs
@all_ggs_grouped_by_org.each do |org, ggs|
    # <- ADDED HERE
    @important_ggs << [org, ggs] if @default_orgs.include?(org)

    # If this is one of the already selected guidance groups its important!
    @important_ggs << [org, ggs] if !(ggs & @selected_guidance_groups).empty? && !@important_ggs.include?([org, ggs])
end

AFTER
    @default_orgs = Org.default_orgs
    @all_ggs_grouped_by_org.each do |org, ggs|
      # add to important_ggs if org is current_user.org or a default_org, or if ggs is already a selected guidance group
      if @default_orgs.include?(org) || (org == current_user.org) || !(ggs & @selected_guidance_groups).empty?
        @important_ggs << [org, ggs]
      end
    end

Just noticed this while doing the upgrade to v4.0.0. I guess the duplicate choice occurs when current_user.org is included in @default_orgs.
Maybe the entire code snippet you shared could be refactored to something like the following?:
BEFORE
if @all_ggs_grouped_by_org.include?(current_user.org)
    # <- ADDED HERE
    @important_ggs << [current_user.org, @all_ggs_grouped_by_org[current_user.org]]
end
@default_orgs = Org.default_orgs
@all_ggs_grouped_by_org.each do |org, ggs|
    # <- ADDED HERE
    @important_ggs << [org, ggs] if @default_orgs.include?(org)

    # If this is one of the already selected guidance groups its important!
    @important_ggs << [org, ggs] if !(ggs & @selected_guidance_groups).empty? && !@important_ggs.include?([org, ggs])
end

AFTER
    @default_orgs = Org.default_orgs
    @all_ggs_grouped_by_org.each do |org, ggs|
      # add to important_ggs if org is current_user.org or a default_org, or if ggs is already a selected guidance group
      if @default_orgs.include?(org) || (org == current_user.org) || !(ggs & @selected_guidance_groups).empty?
        @important_ggs << [org, ggs]
      end
    end

Just realised that this might fix the duplication issue, but it would mess up the desired ordering of the GG's.


Feature/addclientyml

Testing and adding front end CI yaml file.

No need to review this yet. I'm just working on getting the CI working. I'll let people know when we need it reviewed.


CDC_ACM USB not recognized by windows as serial port

Describe the bug
The USB CDC-ACM port is usable under Linux but not usable under Windows 10 unless it is built as a composite device.
To Reproduce
Using the nrf52840 Development Kit board, with a USB cable plugged into the JLink USB connector for programming.
Steps to reproduce the behavior:

cd samples/subsys/usb/cdc_acm
mkdir build; cd build
cmake -GNinja -DBOARD=nrf52840_pca10056 ..
ninja
ninja flash
Plug USB cable into "nrf USB" connector.

Expected behavior
Under Linux, /dev/ttyACM1 is created when the second USB is plugged in and is usable as a serial port with a serial terminal such as minicom.  Under Windows 10, a COM port is created but has an error and is not usable.
This device cannot start. (Code 10)

A device which does not exist was specified.

Impact
The serial port is not accessible to Windows 10 applications.  A workaround is to add the define
CONFIG_USB_COMPOSITE_DEVICE=y
to the prj.conf file and rebuild.  This results in a CDC ACM port that is usable under both Linux and Windows 10.
Screenshots or console output
Screenshot of Windows 10 port with error

Environment (please complete the following information):

OS: Built under Ubuntu 18.04
Toolchain: gcc-arm-none-eabi-7-2018-q2-update
Commit SHA or Version used: d8c5c9dcf1

Additional context
None

Windows 10?, weird. Could you please try CONFIG_CDC_ACM_IAD=y?

Just tried it with CONFIG_CDC_ACM_IAD=y instead of CONFIG_USB_COMPOSITE_DEVICE=y and it works under both Linux and Windows 10.
Thanks for the suggestion!

CONFIG_CDC_ACM_IAD was introduced as workaround for Windows 7, as I remember, there should be no issues on Windows10. @masz-nordic any thoughts?

I was able to reproduce this on Windows 10 1809 with current master. I will try bisecting and testing on various OS versions when I have some time.
@pfvogel What Windows 10 version are you using?

@masz-nordic Windows 10 Home 1809

I have seen this on Windows 10 Pro 1803.
CONFIG_CDC_ACM_IAD=y works fine.

I have experienced the same problem using v1.14 (LTS) of Zephy. Sadly "CONFIG_CDC_ACM_IAD" doesn't seem to be supported in that version.
Are there any plans to backport relevant fixes?


Update dogfood.py ot support UFT-8 for READMEs

What does this PR do?
This updates the dogfooding python script to support UTF-8 encoding on READMEs. I looks like gitlab for some reason was attempting to read the file as ASCII, which broke when we added a warning Emoji to the README in the Flutter SDK.
I also added --dry-run which does everything but push and create the PR.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #944 (f3cc78b) into develop (e5ddff4) will increase coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #944      +/-   ##
===========================================
+ Coverage    82.86%   82.99%   +0.13%
===========================================
  Files          265      265
  Lines         9035     9035
  Branches      1458     1458
===========================================
+ Hits          7486     7498      +12
+ Misses        1145     1142       -3
+ Partials       404      395       -9

Impacted Files
Coverage Δ

...rc/main/java/com/datadog/opentracing/DDTracer.java
56.07% <0.00%> (+0.42%)
:arrow_up:

...og/android/rum/internal/anr/ANRDetectorRunnable.kt
86.21% <0.00%> (+3.45%)
:arrow_up:

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
88.51% <0.00%> (+4.02%)
:arrow_up:

...ndroid/core/internal/persistence/file/EventMeta.kt
90.00% <0.00%> (+10.00%)
:arrow_up:

...android/log/internal/logger/TelemetryLogHandler.kt
100.00% <0.00%> (+25.00%)
:arrow_up:


[WIP] feat(ArtworkFilter): Make filter URL driven so that browser back buttons preserve previous selections

The type of this PR is: Feature
This PR solves GRO-824
Description
This updates our Artwork filter so that we can drive via the back / forward buttons on the browser. Previously when a user made a selection and then hit the back button it would take them away from their previous selection, versus pushing it into the browsers history stack. This fixes that.
Also fixes a bunch of random UX issues like the page loader post filter select being stuck at the top of the page rather than in the viewport, and the zerostate doing the same. Now they will stay within the users scroll position eliminating confusion.

Closing in favor of pass 2: https://github.com/artsy/force/pull/10069


Android transitions not working v4-beta branch

Version
Tell us which versions you are using:

react-native-router-flux v4.?.? (v3 is not supported)
"4.0.0-beta.18"
react-native v0.?.?
"0.47.1 ",
testing on Samsung Galaxy S6

Expected behaviour
Android transitions are not working in v4-beta branch.
Actual behaviour
Even in the example demo, when ran on an android device, all transitions are pop-ups from the bottom.  Same issue occuring in our app after upgrading.  I know other transitions were supported in v3 so is this just one of the current drawbacks of the beta v4 branch?  If this isn't currently in the process of getting fixed then I would be happy to add a note about this to docs.
Steps to reproduce
For non-obvious bugs, please fork this component, modify Example project to reproduce your issue and include link here.

Git clone example app
Run on Android
Notice all transitions are pop-ups

Duplicate of #2177. Feel free to add note. However you may add custom transitions with latest master - check Example with 'fade' transition for some screens.


[ComposerJsonManipulator] Export authors, type and conflicting

Followup of https://github.com/symplify/symplify/pull/2604
The test was not using the getJsonData.

@TomasVotruba What do you think? Where type and conflicting missing by mistake or can we also add them?

@TomasVotruba Can this be merged? I'm kinda blocked by this for LongRunning and SimpleBus projects.

I've let GitHub (I trust him :D) rebase on master, so we can see CI.

Looks good, CI is giving valid feedback now

It's ready

Nice work. Readable and simple, thank you :+1:
The JsonMatches is new for me, cool class.

Thanks for merging. Would be great to have this tagged 🙏

You're welcome.
I'm working on few PHPStan rules changes. I'll tag a patch version today/tomorrow


fix adaptive circle inject #4959

What is the purpose of the change
解决通过SpiExtensionFactory对Adaptive的set方法注入时的循环引用问题
issue #4959
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.guzemin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #5003 into master will decrease coverage by 0.53%.
The diff coverage is 79.49%.

@@             Coverage Diff              @@
##             master    #5003      +/-   ##
============================================
- Coverage     63.89%   63.35%   -0.54%
- Complexity      451      453       +2
============================================
  Files           769      790      +21
  Lines         33261    35094    +1833
  Branches       5235     5492     +257
============================================
+ Hits          21252    22234     +982
- Misses         9571    10323     +752
- Partials       2438     2537      +99

Impacted Files
Coverage Δ
Complexity Δ

.../common/extension/factory/SpiExtensionFactory.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...apache/dubbo/common/extension/ExtensionLoader.java
79.44% <79.44%> (+0.37%)
0 <0> (ø)
:arrow_down:

...ing/zookeeper/support/AbstractZookeeperClient.java
66.29% <0%> (-3.38%)
0% <0%> (ø)

...he/dubbo/registry/zookeeper/ZookeeperRegistry.java
66.66% <0%> (-0.71%)
0% <0%> (ø)

...che/dubbo/common/compiler/support/JdkCompiler.java
64.54% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...a/org/apache/dubbo/common/json/ParseException.java
0% <0%> (ø)
0% <0%> (?)

...o/rpc/protocol/thrift/DubboClassNameGenerator.java
100% <0%> (ø)
0% <0%> (?)

.../java/org/apache/dubbo/common/json/JSONObject.java
17.07% <0%> (ø)
0% <0%> (?)

.../java/org/apache/dubbo/common/json/JSONWriter.java
58.94% <0%> (ø)
0% <0%> (?)

.../apache/dubbo/rpc/protocol/thrift/ThriftUtils.java
91.8% <0%> (ø)
0% <0%> (?)

... and 32 more

Continue to review full report at Codecov.

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


Gekko stops working after few hours

I have been able to setup gekko, backtest strategies, create my own strategies and indicators, and everything seems to be working.
I have also been able to setup live gekkos for paper trading live with my strategies.  They seem to be working fine for as long as I check (30 min after setting up).  Then I leave the system alone.  Next morning, I  am not able to connect to gekko.
The weird part is that when I run "ps ax", it shows node running and some child processes I believe for the live gekkos.
11982 pts/1    S+     0:00 grep --color=auto node
16437 ?        Sl     0:42 node gekko.js --ui
16537 ?        Sl     1:39 /usr/bin/nodejs /root/gekko/core/workers/pipeline/child
16547 ?        Sl     0:13 /usr/bin/nodejs /root/gekko/core/workers/pipeline/child

Then I try to connect from my browser and it doesn't.  I run "ps ax" again and it does not show the parent node process anymore, but it shows the child.
12034 pts/1    S+     0:00 grep --color=auto node
16547 ?        Sl     0:13 /usr/bin/nodejs /root/gekko/core/workers/pipeline/child

Basically I haven't had success with running gekko for long term.
If I restart gekko, the live gekkos are gone, they don't persist for whatever reason.  However I still  have history data that I had gathered before for backtesting.
Has anyone had this kind of issue.  Any help will be appreciated.

Could you tell more about how you run gekko (where do execute the node gekko --ui command) and what environment you are running on (server, laptop, raspberry pi, etc)?
If you for example SSH into a server and start node gekko --ui straight from the terminal the process is bound to the SSH session, meaning as soon as SSH drops the Gekko server will stop.

The weird part is that when I run "ps ax", it shows node running and some child processes I believe for the live gekkos.

When you run node gekko --ui a single "server controller" process is started, if you start live gekkos they are executed through child processes. Similar to the sandbox model used by your browser (if you open a new tab in firefox or chrome, everything is run in it's own subprocess under the hood).

Thanks for the response.  I run it on a server.  I had tried disowning the process before shutting down the ssh connection and I even tried to run it as daemon using daemon library from node.  But nothing helped.
However nohup seems to work.  It successfully ran overnight.
Thanks.


Provide optional query parameters along with the body payload.

For body-based requests, the current connector supports either query parameters or body parameters but not a mix of both.
Some REST API require query parameters like ?version=123&id=1 or an apiKey as query parameter in addition to the body payload.

Hi @OlivierZembri
Thank you for submitting this issue and preparing the PR.
I'm taking look at it.

Released in 0.12.0.
Version is already pushed to maven central. It usually takes some time until it will be visible on connector's maven page but it should be available to download from maven already


Monitoring beach tab

The monitoring tab for Mote beach data is not refreshing.

Link to the Mote data returns an error. New links are available and program needs to be updated.


Consider promoting Respond

To its own mini-mod or perhaps simply its own pkg here.
Likely wringing my hands on this one ..

Hand wring complete!  Settled into its own pkg as of bb21250


handle failed updates for json parse issues (zero length seems most c…

…ommon) in a more homeassistant way

this should fix issue #14


bug: View caching and getElementById

Type: bug
Platform: mobile webview
I'm using Google javascript maps in my Ionic app, and they stopped working when I upgraded to 1.0RC5 from an earlier 1.0 beta. When I turn off caching for this view then the maps work again, but I'd like to use caching.
I'm using REST style URLs in my app, so the link for my page with the map looks like '#/page/{{item.id}}'. With caching on, the maps load fine on the first of these pages I open, and they continue to work if I reopen the page with that id, but they have an empty div instead of a map for pages with other ids.
I can see my map-creation function completes without error in both cases. Here's the bit in my controller that I assume is at issue:
map = new google.maps.Map(document.getElementById("map"), mapOptions)
Is the div returned by this getElementById call not the one being shown? Or is something else going on?

Greetings @craig-at-rsg!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Greetings @craig-at-rsg!
My sensors indicate that I require more information in order to assist you.

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this happen occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?

Additionally, providing a codepen that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting the forum, where many humans will be able to offer wisdom and advice.
Thank you for allowing me to assist you.

This sample shows the bug on both android and ios, just click back and forth between the links. The console will log that the text in the div is being replaced, but it won't be replaced for the 2nd link.
angular.module('starter', ['ionic'])
    .config(function ($stateProvider) {
        $stateProvider
            .state('page', {
                url: '/page/:param',
                template: "
Text not replaced
Works
Doesn't",
                controller: 'PageController'
            });
    })
.controller('PageController', ['$scope', function ($scope) {
	   $scope.$on('$ionicView.enter', function() {
           console.log('Replacing text');
        document.getElementById("container").textContent = 'Text replaced';
           console.log('Replaced text');
       });
    }])
.run(['$state', '$ionicPlatform', function($state, $ionicPlatform) {
  $ionicPlatform.ready(function() {
      $state.go('page', {param: 'cached'});
  });
}]);

You want to get the element of the active page. With cached views, getElementById will always yield inconsistent results because other pages still exist in the DOM (they're just hidden). Try this selector instead.
document.querySelector('[nav-view="active"] #map')
If you're still having trouble, this is better a discussion for the forums than an issue with Ionic.


balena-yocto-scripts: Update to v1.14.9

Update balena-yocto-scripts from 1.14.8 to 1.14.9
Changelog-entry: Update balena-yocto-scripts from v1.14.8 to v1.14.9
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@resin-jenkins retest this please

@resin-jenkins retest this please

@resin-jenkins retest this please

@resin-jenkins retest this please

@resin-jenkins retest this please

@resin-jenkins retest this please


Qustions about dynamic NTK interpolation fine-tuning and non-linear interpolation methods

Hello LongLora Team,
I have been following your work with great interest, particularly regarding the dynamic NTK. While reviewing the code and paper, I noticed that the current experimental results are primarily based on the PI (linear interpolation) method. I am curious to know if you have conducted experiments on interpolation fine-tuning with dynamic NTK. If so, I would be interested in learning more about the corresponding results and findings.
Additionally, I am intrigued by the possibility of experiments with non-linear interpolation methods such as YaRN and NTK. Have you explored similar approaches, and if there are any relevant experiments or findings, I would like to know more about them.
Thank you for your time and efforts!

Hi,
Many thanks for your question. Actually, we have not conducted these experiments yet.
Regards,
Yukang Chen


🍒 Cherry pick PR #6313 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/6313 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.1.15-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @AndrewGable in version: 1.1.15-15 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


feat(ofs): introduce macos support

WIP

waiting for https://github.com/Sherlock-Holo/fuse3/pull/90

recreate https://github.com/apache/opendal/pull/5136 due to rebase hell

Thanks a lot for your work! @oowl


issue with adapter and metric pushed via pushgateway: custom metric stays at 0

hello,
I'm testing a configuration where I'm trying to send custom metrics both with pull and push modes.
for the pull mode I'm using the image found in the adapter walkthrough: here, wrapped in this gist
For the push mode I'm using the following gist: here
My setup is based on the community prometheus chart here and the community prometheus-adapter chart here. I've created my own chart which simply depends on those charts and passes in some default values to configure prometheus.
The adapter chart is not customized (beside settings prometheus url and port), the prometheus chart instead has been configured by this values.yaml
I'm not using the operator and I annotate the pods for the pull example
what happens is:

if I deploy the pull example everything works like a charm and the pods start autoscale depending on the published metric
if I deploy the push example everything seems right up to prometheus, which scrapes from the pushgateway and shows the metric correctly on screen. The adapter discovers the metric but prints a constant value of 0, while I'm expecting a constant value of 25m (according to the linked push example yaml).

Here the comparison of the push and pull outputs:
# get metrics from the push example
matteo@matteo-Aspire-A315-55G:~/Documents/.../prometheus/helm$ kubectl get --raw
"/apis/custom.metrics.k8s.io/v1beta1/namespaces/default/pods/*/http_push_requests"

{"kind":"MetricValueList","apiVersion":"custom.metrics.k8s.io/v1beta1","metadata":{"selfLink":"/apis/custom.metrics.k8s.io/v1beta1/namespaces/default/pods/%2A/http_push_requests"},"items":[{"describedObject":{"kind":"Pod","namespace":"default","name":"sample-app-push-75dd54ff8c-wdp68","apiVersion":"/v1"},"metricName":"http_push_requests","timestamp":"2021-02-04T09:23:31Z","value":"0","selector":null}]}

# get the metrics as per the default pull walkthrough
matteo@matteo-Aspire-A315-55G:~/Documents/.../prometheus/helm$ kubectl get --raw
 /apis/custom.metrics.k8s.io/v1beta1/namespaces/default/pods/*/http_requests"

{"kind":"MetricValueList","apiVersion":"custom.metrics.k8s.io/v1beta1","metadata":{"selfLink":"/apis/custom.metrics.k8s.io/v1beta1/namespaces/default/pods/%2A/http_requests"},"items":[{"describedObject":{"kind":"Pod","namespace":"default","name":"sample-app-998b9cbc4-mln7z","apiVersion":"/v1"},"metricName":"http_requests","timestamp":"2021-02-04T09:23:36Z","value":"16m","selector":null}]}

I've spent 2 hours poking around without any clue. What info cloud I provide you to help me debug this issue?
Thanx a lot!

My fault: the default prometheus-adapter chart configMap seems to compute deltas between values rather than republish pure values, therefore being my example pushing a constant value, the output was a constant 0. by generating random numbers everything has started making more sense.


Support decouple_commit for all olap sinks ?

Is your feature request related to a problem? Please describe.
Do we need to support decouple_commit for all olap sinks? Currently, we support iceberg and deltalake and starrocks
from https://github.com/risingwavelabs/risingwave/issues/17214#issuecomment-2162301929
And do we need to support the alter parameter for dynamic adjustment from @neverchanje
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

I think the answer should be "yes, let's do it"
Tracked in #17095


Remove all insert_a... method and instead use Boxes in spec/support/boxes/

Closed by https://github.com/luckyframework/lucky_record/pull/159


Pagination shrinks the datagrid on selection in IE 11

Describe the bug
When the clarity datagrid is used together with the pagination functionallity the datagrid shrinks when the datagrid selection changes.
How to reproduce
Stackblitz does not work under IE 11, thus to reproduce this I have used a locally created project.
If needed I can host this simple project sample somewhere for download.
Video of the reproduction:  https://www.dropbox.com/s/ze77d358he969ms/datagrid-shrink.mp4?dl=0
Code snippet:
app.component.html
<clr-datagrid [(clrDgSelected)]="selectedItem">
    <clr-dg-column>Name</clr-dg-column>
     <clr-dg-row *clrDgItems="let item of items" [clrDgItem]="item">
       <clr-dg-cell>
          {{item.name}}
       </clr-dg-cell>
    </clr-dg-row>
    <clr-dg-footer>
       <clr-dg-pagination #pagination [clrDgPageSize]="numberOf"></clr-dg-pagination>
    </clr-dg-footer>
 </clr-datagrid>

app.component.ts
import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent {
  selectedItem: any[] = [];
  items: any[] = [{name: "Foo"}, {name: "Bar"}];
  numberOf: number = 5;
}

Expected behavior
When items are selected in the datagrid,there should be no shrinking and expanding.
Versions
App

Angular: 9
Node: 10
Clarity: 3.0.0-rc.1

Device:

Type: PC
OS: Windows
Browser IE
Version 11

Hi @ickobombata it would help greatly to have the same reproduction (as a github repo or stackblitz) to give us the ability to see your exact setup.

Here is a stackblitz with the reproduction code:
https://stackblitz.com/edit/clarity-light-theme-v2-v5rv96
As stated above stackblitz does not work under IE due to a bug.

There is an additional issue when the pagination footer is added, namely
a scroller appears when an item is selected in the datagrid.

Hi @ickobombata, I reviewed this and the issue is related to having nothing inside of the footer. We expect that you'll project some content inside of it, so the solution is to project something like
<clr-dg-footer>
    <clr-dg-pagination #pagination [clrDgPageSize]="10">
        <clr-dg-page-size [clrPageSizeOptions]="[10,20,50,100]">Users per page</clr-dg-page-size>
        {{pagination.firstItem + 1}} - {{pagination.lastItem + 1}}
        of {{pagination.totalItems}} users
    </clr-dg-pagination>
</clr-dg-footer>

Closing as its expected you'll have content, even a   will suffice to project something.


JAR paths seem to not work as intended

HOME_DIR=/home/bduser01 # replace with your home directory
HOME_DIR_STRING="/home/bduser01" # same but in string format

cd ${HOME_DIR}/rd-n2-automotive/layers/poky
bd_scan_yocto \
--detect-jar-path "${HOME_DIR_STRING}/synopsys-detect/downloads/synopsys-detect-8.11.0.jar" \
-p "AIS:RD-N2-automotive" \
-v "test" \
-t "baremetal-image" \
-m "${HOME_DIR_STRING}/rd-n2-automotive/build/tmp_baremetal/deploy/licenses/baremetal-image-fvp-rd-n2-automotive-20230718121437/license.manifest" \
--blackduck_url $BDURL \
--blackduck_api_token $BDAPITOKEN \
--blackduck_trust_cert \
--debug

This is an example of a sample shell script on a yocto build. The output can be seen below:
INFO:root:--------------------------------------------------------------------------------
INFO:root:--------------- Yocto Black Duck Signature Scan Utility v1.0.4 -----------------
INFO:root:--------------------------------------------------------------------------------
INFO:root:----------------------------------   PHASE 0  ----------------------------------
INFO:root:GETTING YOCTO ENVIRONMENT
INFO:root:- Running 'bitbake -e' ...
INFO:root:Bitbake Env: deploydir=/home/bduser01/rd-n2-automotive/layers/poky/build/tmp/deploy
INFO:root:Bitbake Env: ipk_dir=/home/bduser01/rd-n2-automotive/layers/poky/build/tmp/deploy/ipk
INFO:root:Bitbake Env: rpm_dir=/home/bduser01/rd-n2-automotive/layers/poky/build/tmp/deploy/rpm
INFO:root:Bitbake Env: download_dir=/home/bduser01/rd-n2-automotive/layers/poky/build/downloads
INFO:root:Bitbake Env: image_pkgtype=rpm

RUNNING WIZARD (Use --no_wizard to disable) ...
- Nothing for Wizard to do - continuing ...

INFO:blackduck.Client:Using a session with a 30 second timeout and up to 3 retries per request
INFO:blackduck.Authentication:success: auth granted until 2023-08-30 18:16:25.224533+01:00
INFO:root:Connected to Black Duck server https://arm.app.blackduck.com
INFO:root:----------------------------------   PHASE 1  ----------------------------------
INFO:root:RUNNING DETECT ON BITBAKE PROJECT ...
Error: Could not find or load main class .home.bduser01.synopsys-detect.downloads.synopsys-detect-8.11.0.jar--detect.project.name=AIS:RD-N2-automotive
Caused by: java.lang.ClassNotFoundException: /home/bduser01/synopsys-detect/downloads/synopsys-detect-8/11/0/jar--detect/project/name=AIS:RD-N2-automotive
ERROR:root:Unable to run Detect Bitbake scan

More information about reproducing can be found through the file sent over by the ARM-OSS team directly in the Synopsys support slack channel, but the gist is that the python script seems to replace the "."s with "/"s for some reason. The script was run both using a venv and without one (same result either way).

removing that flag seems to work, but this is presumably not an intended feature

Addressed issue with v1.0.5 subject to testing.
Issue was missing spaces for some options when running Detect


Milestone 5: Style

Dear TSE :wave:
HEROKU :link:
README :spiral_notepad:
:art: We have used the Zeplin Design to finish our project.
With all my respect... :pray:

Thank you so much @suretrust for the review.
Please note that the live version is not updated.

Thank you so much @suretrust for the review.
Please note that the live version is not updated.

The latest changes have been released now :blush:


How do i set fixed audio/video bitrate?

While using apprtc.appspot.com i had option to set manually audio/video upload/download bitrate:
var audioSendBitrate = '50';
var audioRecvBitrate = '50';
var videoSendBitrate = '100';
var videoRecvBitrate = '100';
var videoSendInitialBitrate = '100';
In SimpleWebRTC how do i set that please?

@envery solution works for me.