[Feature Request] Allow Users to Load Account Files

Currently, you are able to export your accounts via a file with the content of the txt file as your signing key.  It would be nice if we could load these account files in the gui, though.

It could look something like this (with my amazing artistic ability):

When you click the Load File button, the content of the file selected from the file picker would be injected into the signing key form input.  We could also maybe set the nickname as the name of the file, but that would need debate.

Dupe of #149 sorry.


Fix issue where hooks are being overwritten by Mixin init

@Wildhoney
This is similar to #91 where hooks cannot be defined on a component because they get overwritten. The ideal situation would be that like the options, we do not use a global object... unfortunately, in my testing, it was timing out...
Thoughts?

@lardawge I've just merged PR https://github.com/Wildhoney/EmberDroplet/pull/99 that should fix this issue – could you please give v2.0.1 a try?


Support boolean type to variables' ops and assign-like ops.(#12046)

Fix #12046.

Can one of the admins verify this patch?

Jenkins, test this please

Jenkins, test this please

Jenkins, test this please

Have updated the code.

Jenkins, test this please


Investigate and implement reactive 2-way route bindings

We need a better solution for updating the URL and UI, keeping both in sync, particularly for product grid filtering, sorting, and pagination.
Requirements:

URL is the source of truth but is also bound to MobX routing store.
There is one defined and documented way that any component should trigger URL updates.
The solution is generic, allowing us to use most of it in another storefront that may not use mobx or NextJS.
Changes are reflected immediately in the URL and the UI reactively updates, but the page does not refresh.
Works with SSR

Idea:
The individual components need not think of this as routing, nor even know that it's bound to the URL. It could simply be an action in the UI store, where any component might do uiStore.updateProductGridFilters({ ... }) or uiStore.updateProductGridSort({ ... }). The grid/pagination components can simply use filtering and sorting props from mobx store. Then URL binding can be achieved by updating the URL when certain uiStore props change (autorun) and updating mobx props when URL changes.
Here is example two-way binding pattern that I once wrote for another app, but this used react-router and redux, and would not work with SSR. Might still be useful as a starting point:
import querystring from 'query-string';
import { browserHistory } from 'react-router';

const actionList = [];
let acting = false;
let lastQs = {};

function updateLocationSearch(qs) {
  // Get the new query string as a string
  let newQs = querystring.stringify(qs);

  // Since window.location.search has the "?" if there's any string, add that
  // back for comparison with the existing string
  if (newQs.length) newQs = `?${newQs}`;

  // It's very important to update only when we've actually changed something
  // or we'll trigger an infinite loop.
  if (window.location.search !== newQs) {
    browserHistory.replace(`${window.location.pathname}${newQs}`);
  }
}

/**
 * Call mapStateToQueryStringParam to specify that a query string param should
 * be updated to be kept in sync with some part of the redux state whenever a
 * certain action changes that state (after the action is done).
 * @param {String} param - The name of the query string param to set
 * @param {Object} [options] - Options
 * @param {Function} options.paramToState - A function that accepts the param value, called on every route change. If something is returned, it is assumed to be an action and is dispatched.
 * @param {Function} options.stateToParam - A function that accepts the new state, after the action is done, and returns the query string param's new value. Must return a string to set the param or any non-string to clear the param.
 * @param {String[]} [options.routes] - The routes on which to show the query string
 */
function mapStateToQueryStringParam(param, options = {}) {
  actionList.push({
    options,
    param,
  });
}

/**
 * Call getQueryStringStateListener with your store to get back a listener. Like this:
 *
 * store.subscribe(getQueryStringStateListener(store));
 *
 * @param {Object} store - A redux store
 */
function getQueryStringStateListener(store) {
  return function queryStringStateListener() {
    if (typeof window === 'undefined') return;

    // We use `acting` to make sure we do not run this listener when any of the
    // paramToState functions emit actions that modify state WHILE this function
    // is already running. This is extra protection against infinite looping.
    if (acting) return;
    acting = true;

    // If commas are escaped, change back to commas
    const search = window.location.search.replace(/%2C/g, ',');
    const qs = querystring.parse(search);
    const pathname = window.location.pathname;

    if (JSON.stringify(qs) !== JSON.stringify(lastQs)) {
      actionList.forEach(({ options, param }) => {
        if (
          // If this mapping applies to all routes or to the current route
          (!options.routes || options.routes.indexOf(pathname) > -1) &&
          // And there is a paramToState function
          options.paramToState &&
          // And the param changed
          JSON.stringify(qs[param]) !== JSON.stringify(lastQs[param])
        ) {
          const action = options.paramToState(qs[param]);
          if (action) store.dispatch(action);
        }
      });
    }

    const nextState = store.getState();

    // For all other state changes, check to see whether a query string param
    // needs updating to stay in sync.
    actionList.forEach(({ options, param }) => {
      // Update the query string for the current path, we do not clear the params
      // here because this deletes any duplicate params shared by seperate routes
      if (
        // If this mapping applies to all routes or to the current route
        (!options.routes || options.routes.indexOf(pathname) > -1) &&
        // And there is a stateToParam function
        options.stateToParam
      ) {
        // Run the provided function, which pulls the qs value out of the state object
        const value = options.stateToParam(nextState);

        // Set or clear the param
        if (typeof value === 'string') {
          qs[param] = value;
        } else {
          delete qs[param];
        }
      }
    });

    updateLocationSearch(qs);

    acting = false;
    lastQs = qs;
  };
}

export { getQueryStringStateListener, mapStateToQueryStringParam, updateLocationSearch };

This is how it was used:
store.subscribe(getQueryStringStateListener(store)); // redux store listener

mapStateToQueryStringParam(paramName, {
    paramToState(value) {
      // Return a redux action to be dispatched
    },
    replace: true,
    routes: ROUTES, // an array of routes on which this query param should be watched/bound
    stateToParam(state) {
      // return a value for the param based on current redux state. Runs whenever state changes.
    },
  });

Also as part of this, we should investigate how this can also work with event tracking.

@ticean / @reactioncommerce/architecture you might have thoughts on routing here.

@rosshadden @mikemurray @ticean
This issue may be relevant to the work being done on routing.

I agree this is somewhat relevant, but this is primarily about binding the query string to state when we are NOT refreshing the page. Example, as you're adjusting catalog grid filters, we're updating the query string so that you'll see the same filtered view if refreshing or sharing that link.
So I would try to decouple these ideas since the larger routing project is about what happens when switching between pages while this issue is about tracking state in the URL while on a single page.


Change wording of some strings

I'm not particularly happy about "Incoming server settings are OK". But I liked all other suggestions I've heard so far even less.
Suggestions welcome.

I personally don't like OK, but why not asking Jason?

I was asking the people good with words. No luck so far.
How about "Incoming server settings verified"?


Use mypy with pre-commit hook

Codecov Report

Merging #70 (ac8b097) into release-candidate (81f7279) will not change coverage.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##           release-candidate       #70   +/-   ##
===================================================
  Coverage             100.00%   100.00%
===================================================
  Files                     50        50
  Lines                    860       860
===================================================
  Hits                     860       860


add test for advanced biosphere

Add a test that checks if the static LCA inventory per emission (e.g. CO2) is the same as the sum of the temporalized emissions of the same type.

I checked this in the commit 053e3cc64df5a577fc63fcd58572698d96b26a8e on the bioflows branch. And this is true. Test needs to be implemented still though, automatically for all env flows.


_yarn_linear_ramp_mask() missing 1 required positional argument: 'device'

In vllm/model_executor/layers/rotary_embedding.py, function _yarn_linear_ramp_mask need a parameter device and it doesn't have a default value, but in line:307: inv_freq_mask = (1 - _yarn_linear_ramp_mask(low, high, self.rotary_dim // 2, dtype=torch.float)) * self.extrapolation_factor don't use this parameter.

+1， Perhaps we should deploy a static syntax checker in the GitHub Actions of this project.


Update sbt to 1.5.1

Updates org.scala-sbt:sbt from 1.5.0 to 1.5.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.5.0).
You might want to review and update them manually.
containers/release-candidate/setup-container.sh
daffodil-test-ibm1/src/test/resources/test-suite/tresys-contributed/mixed-binary-text.tdml

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-patch, old-version-remains

+1

[X] Do all automated continuous integration checks pass?
Yes
[X] Is the update a patch, minor, or major update?
Patch update, changelog seems like reasonable changes to include
[X] Is the license still compatible with ASF License Policy?
Yes, still ALv2
[X] Have any changes been made to LICENSE/NOTICE files that need to be incorporated?
No changes, but we don't distribute sbt, no need to inclusion in repo
[X] Have any transitive dependencies been added or changed?
No changes

The idea was to download and build the right sbt version when building the container so that it can be avoided everytime the we run the container.
Maybe a better alternative would be for this to find the build.properties file and get the sbt version from that?
Or maybe that's not even necesary and we sholdn't worry about it? Building release candidates isn't exactly a fast process so maybe we don't care about the extra time needed to download/build sbt?

Let's try the last idea.  Since building a release candidate occurs in the GitHub Actions environment (even though you run inside a container), it shouldn't take that long to download/build sbt on the fly.

Building an RC actually isn't done in GitHub actions. It's a somewhat manual process that requires secret keys/passwords from whoever is building it. But I think it's worth removing, we can always add it back if find it does add a significant amoujnt of time. I'll add a fixup commit


Remove support status for Ubuntu 14.04 in .NET Core 2.2

The 2.2 release note state that .NET Core 2.2 supports Ubuntu 14.04, which is not true. Rich Lander said:

Platform Support
.NET Core 2.2 is supported on the following operating systems:

Ubuntu: 16.04+

[...]
Ubuntu 14.04 doesn’t have much life left. We decide that this release was the right time to declare 16.04 as the minimum version. See: https://www.ubuntu.com/about/release-cycle

Please put Ubuntu 14.04 to Out of support OS versions section.

@leecow @vivmishra can you confirm and make the change please?

@richlander

I just talked to @vivmishra ... he is going to update the 2.2 release notes.
To explain ... we have an unwritten policy where we take a look at which distro versions will go out of support within 6 months of a new .NET Core release. We then subjectively decide whether to continue supporting it until the EOL date or not. It isn't a hard-and-fast rule. In this case, the last release before 2.2 was an LTS release, so there is no forcing function for people to adopt 2.2 (unlike 2.0). As a result, I think that everyone is well-enough served by this decision: 14.04 users can continue to use 2.1, 2.2 users will not be surprised by 14.04 support being dropped within 6 months, and the .NET team can can reduce a testing leg. That's the thinking in a nutshell.
Now to the real sausage making: I did not communicate this very well within the team, except via the blog post. I apologized to @leecow and @vivmishra. I also wish to apologize to anyone else that was confused/affected.
And to state the obvious, .NET Core 2.1 support for 14.04 will end in April 2019, as most people familiar with Ubuntu EOL dates would expect.


Bookmark CFIs using Ranges instead of Spatial offset (WIP) #157

See #157
Notes:

How well does this work with RTL/VWM?
CFI library sync up

Some irrelevant (potentially useful) changes sneaked in:
- Attempt at preventing image overrun, now takes into account of padding/margin..
~~https://github.com/readium/readium-shared-js/pull/158/files#diff-5899c9a9fc900e9651da6e2d81f3025bR778~~
- Reduce extraneous pagination events that occur under certain conditions..

@danielweck

I look forward to giving this a try Juan.
Eventually, would it be possible to extract the onPaginationChanged fixes into a separate Pull Request? I think we would need to track potential regression bugs separately for this (e.g. Media Overlays page turn sync engine)

@danielweck I have removed the separate fixes from this PR.
I also reviewed the CFI library usage and have determined that this is compatible with everything in 'develop' on the cfi library repo. So I will update the CFI library in this branch with a build from there.

Thanks @JCCR much appreciated. Sorry I don't have time to look into the details right away.
PS: updating the pre-built CFI lib sounds like a good idea, and this feature branch / Pull Request is a good place to do it.

@danielweck Yea, it's ok if you can't right now. I found a bug with my CFI library update anyway :)

@danielweck Cleaned up some code a bit, and fixed code missing in the CFI library for some of this.

Closed in favour of #210


Some red LEDs (EZ DEBUG LED?) are controlled, too

I noticed, that some red LEDs are on on the MSI X470 Gaming Plus. One is directly on the one RAM port I have installed RAM to and one is right at the PCI-E x16 port.
First I was confused, since everything works. EZ DEBUG LED from MSI isn't documented a single bit, so I wrote them a e-mail. The answer was, the EZ DEBUG LEDs are only turned on if the hardware is missing or a failure.
I started again your tool, turned off and on the RGB-LEDs... The red LEDs are controlled by your tool, too! They even flash if I set it in the tool.
So, maybe your tool changes too much on the MB?
Thats not really an issue, I just wanted you to know this behavior.
Update
So the EZ DEBUG LEDs are on the right side, 4 with a caption. Turned off. I'd assume the red LEDs which are turned on would be associated with them, but doesn't seem so. They don't have a caption.
On the picture, you can see both red LEDs and the EZ DEBUG LEDs on the right side, with their caption.
https://i.imgur.com/hNRqiqJ.jpg

Right, it seems that the tool controls all LEDs on the motherboard. I wasn't sure about that.
It's not that the tool changes each specific LED, but rather that the chip controls all the LEDs at once. Likely not something I could change if I wanted to.
Other than that, does the tool work properly?

Thanks for the info, though.

It's also strange, that only the LEDs are turned on, where I installed something (GPU and one RAM).

Other than that, does the tool work properly?
From what I tested, yes. I didn't test LUA scripts. I'm still on the initial release, since I can make it work with Python instead of LUA. Would have been nice, if you kept the command line still in the new version. A friend of mine uses the newest version and seems happy with it.

It's also strange, that only the LEDs are turned on, where I installed something (GPU and one RAM).
Do you have any clearer picture of it?  When it comes to the LEDs to the right, if they are at the back, then it's the backlight and is supposed to be on if MB lighting is on. A quick glance to photos of the MB led me to believe that's the only MB LED you have.

From what I tested, yes. I didn't test LUA scripts. I'm still on the initial release, since I can make it work with Python instead of LUA. Would have been nice, if you kept the command line still in the new version. A friend of mine uses the newest version and seems happy with it.
The point of the new release was to make it simpler for the average user and also quicker to use, even for me. The only advantage you have with command line + Python option is in importing any module you want, or integrating my tool with other tools. Lua is pretty easy, similar in some respects to Python, and also simpler feature-wise, plus scripts will be loaded automatically on Windows start-up. You should give it a try.

Also, what MB is your friend using?

Do you have any clearer picture of it? Your original one doesn't let me see the RAM LED you speak of.

https://i.imgur.com/VlXosr8.jpg

When it comes to the LEDs to the right, if they are at the back, then it's the backlight and is supposed to be on if MB lighting is on. A quick glance at photos of the MB led me to believe that's the only MB LED you have.

I mean these 4. They are the EZ DEBUG LEDs.

The point of the new release was to make it simpler for the average user and also quicker to use, even for me. The only advantage you have with command line + Python option is in importing any module you want (debatable whether that actually gives much of an advantage), or integrating my tool with other tools. Lua is pretty easy, similar in some respects to Python, and also simpler feature-wise, plus scripts will be loaded automatically on Windows start-up. You should give it a try.

Ya, currently I am using just the example script, so I could use the example LUA script aswell. I just put the script in the Taskplaner of Windows.

Also, what MB is your friend using?

Same as me, the X470 Gaming Plus.

I opened the case just for you
They seem to be just for design and maybe they light up even if the official Mystic Light is used.
https://i.imgur.com/VlXosr8.jpg

They are simply for decoration according to this:
https://forum-en.msi.com/index.php?topic=305853.0
Could be that they give slot-specific failure information, but come to think of it, I had seen something about RAM LEDs while reverse engineering Mystic Light. To clarify, the RAM LEDs are controlled by the tool as well? They don't seem to have the same colour as the backlight, so is it that the tool turns them on/off but can't control their colour? But you say they flash too. What exactly can you change about them?

I mean these 4. They are the EZ DEBUG LEDs.

Ah, okay then. These are debug LEDs only, indeed. The tool shouldn't affect them whatsoever.

They are simply for decoration according to this:
https://forum-en.msi.com/index.php?topic=305853.0

Ya, seems like that.

Could be that they give slot-specific failure information, but come to think of it, I had seen something about RAM LEDs while reverse engineering Mystic Light. To clarify, the RAM LEDs are controlled by the tool as well? They don't seem to have the same colour as the backlight, so is it that the tool turns them on/off but can't control their colour? But you say they flash too. What exactly can you change about them?

The tool only decides if they are turned on or off and if they flash or not. Always red.

Ah, okay then. These are debug LEDs only, indeed. The tool shouldn't affect them whatsoever.

Yes, I first assumed the deco-LEDs would be associated with them. But no, just blinky blinky.
If they also would be in RGB, I wouldn't have assumed that. I'd say, that's bad design by MSI.
That clarified a lot, thanks. You can close this, if you don't have any other questions.

Other than that, does the tool work properly?

I just noticed, that the newest version does like 7-8% CPU load. That's a lot! Even the Task-Manager says, that the power consumption is very high.
The Python script stays on 0-0,1%.
The first thing I wanted to do is, reloading the script. That's not possible, I need to kill the process in the Task-Manager.

Clicking on "Apply" or "Disable all lighting" stops the script. I suppose that's not the most intuitive thing.
But the CPU usage problem had already been fixed. Are you using 1.0.2?

Nevermind, you're absolutely right. I fixed it in 1.0.1 and broke it again in 1.0.2. os.sleep is consuming all the CPU time.

Fixed in v1.0.3.

Works perfect!


Crash

When I enter a manga and go down to the end, the app closes me :/
PS: put that to link account again or save favorites in the cloud, minimum 👍

Duplicate  of #160


Implement BLAKE2

https://www.blake2.net

@05nelsonm are you going to support this soon?

I'd love to actively work on this asap, but atm I am slammed.
PR's are always welcome!

Not sure if this will help or not, I converted the bouncycastle implementation to Kotlin for use in my own KMM hashing library - source available https://github.com/appmattus/crypto/tree/main/cryptohash/src/commonMain/kotlin/com/appmattus/crypto/internal/core/bouncycastle/blake2


Release with new Goodhosts CLI

1.1.7 or would we go for 1.2?

Looking at 1.1.1 there isn't a big change in the cli utility

Closing as done


Update repo?

The PDFium repo is quite a ways out of date. Would it be possible to either get the repo updated, or get access so I can update the repo myself?

Ping.

ping.

Ping, any chance to get this updated, or control passed off so it can be updated?

ping.

Ping. Any chance we can update this?

Currently, the official repository seems to be https://pdfium.googlesource.com/pdfium/.
A maintained project building on PDFium is https://github.com/pvginkel/PdfiumViewer.

Yes, but the github mirror showed high in search ranking and it's 3 years
out of date.  I'd like to sync it to tip of tree but there is no response
from the creator.
Dan
On Aug 24, 2017 01:57, "Oliver Kopp"<EMAIL_ADDRESS>wrote:
Currently, the official repository seems to be https://pdfium.googlesource.
com/pdfium/.
A maintained project building on PDFium is https://github.com/pvginkel/
PdfiumViewer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PDFium/PDFium/issues/2#issuecomment-324540896, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAli4M5ptepi16Y56DeBGCCqvcR2FIIks5sbRDUgaJpZM4J8Tun
.

The owner of this repository should either:

Set up mirroring from the official repo,
Mention prominently in the README how it is different from the official repo and why (for instance they stopped at commit X because of reason Y),
or delete the repo.

I've been keeping a mirror of the official repo at https://github.com/dj2/pdfium. It's usually no more then a week behind.

ping?


Handle tiers that creates a "prepaid" card after payment

Draft
User story
For "host collectives" (collectives linked to a fiscal host to manage their budget), we want to create special tiers that create a "prepaid" card after a payment is validated.
Limitations

This should be available at first only for tiers of "host collectives". They can be recognized with their settings.hostCollective=true ie: http://opencollective.com/opensource
The tier itself should be activated for this special behavior: settings.createPrepaidCard=true

Specification

A prepaid card (valid on the host) will be created and owned by the account initiating the donation. Platform fees and host feeds should naturally be removed from it.
The balance of the "host  collective" should be deducted from the value once the prepaid card is created. Do we need to create a transaction to materialize that?

Data
Payment Method entry
{
    "primary" : false,
    "initialBalance" : order.totalAmount - fees,
    "CollectiveId" : order.fromCollective.id,
    "currency" : order.fromCollective.host.currency,
    "customerId" : order.fromCollective.slug,
    "service" : "opencollective",
    "type" : "prepaid",
    "data" : {
      "HostCollectiveId": order.fromCollective.host.id
    },
    "createdAt" : NOW(),
    "expiryDate" : NOW() + 1 month
}

It was not exactly implemented like initially specified but this is done.


Translated "Discord" to the selected language for most languages

Fix for issue #745 and #705
This is only for some languages, I didn't wanna touch about 5 because I wasn't familiar with them.

Why would you translate Discord? It is a name...

Is this a joke?
Discord is an app....

Why would you translate Discord? It is a name...

Well from what I know in some other countries, "discord" is in their language so they might not understand it because discord has the name to the location.

@prokopschield Discord is the name of an app, isn't it? Would you translate Dogehouse to Kuttaghar in urdu?

Why would you translate Discord? It is a name...

Well from what I know in some other countries, "discord" is in their language so they might not understand it because discord has the name to the location.

Discord, as in the app, is always Discord, in every language.

discord is an English word too, so that's why it has translations. but in the case of Discord is a proper noun.

so we dont need to translate Discord as far as I know.

@prokopschield Discord is the name of an app, isn't it? Would you translate Dogehouse to Kuttaghar in urdu?

I guess to

so we dont need to translate Discord as far as I know.

Your right, you may close the PR.


Update information regarding source, format and supportability of dataset and inline.

Looking into ADF interface, in fact using inline datasets with json in Azure Data Lake store is actually supported. And at the end of the day resolve some issues regarding parsing json files (even one produced by other copy activitiy)

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

ID: 4810e7d6-28ed-d956-44b6-77fe62b579e5
Version Independent ID: 98b5df43-40de-ee10-e63c-c5f15eca1a16
Content: Source transformation in mapping data flow - Azure Data Factory
Content Source: articles/data-factory/data-flow-source.md
Service: data-factory
GitHub Login: @kromerm
Microsoft Alias: makromer

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

We have assigned the issue to the content author . They will evaluate & update the document as appropriate

fixed and publishing this week

#please-close


manufacture-date is not date and time

The manufacture-date element is a simple date without time (or even less, e.g. "2019-11"). Thus, the yang:date-and-time type cannot be used.

Even the time is not required - yang:date-and-time could be used, by setting hours, minutes and seconds to 0.
example
As alternative a new common type definition should be defined:
typedef date {
  type string {
    pattern
      '^\d{4}-\d{2}-\d{2}?(Z|[\+\-]\d{2}:\d{2})$';
  }

alternative

Draft proposal:
Add a new typedef in the core-model, describing a date, and modify manufacture-date to use that type.
typedef date {
  type string {
    pattern
      '^\d{4}-\d{2}-\d{2}$';
  }
 description
  "The date type is a profile of the ISO 8601
      standard for representation of dates using the
      Gregorian calendar.  The profile is defined by the
      full-date production in Section 5.6 of RFC 3339.";
 reference
 "RFC 3339: Date and Time on the Internet: Timestamps";

The date described as YYYY-MM-DD is according to RFC 3339 Section 5.6, which uses the date format in accordance with ISO 8601 standard.
Using the newly proposed date definition instead of the existing date-time is also in accordance with RFC 6933 Section 2.12.1

Alternative proposal to the 5G-xhaul call on 12th of October 2022:
The EquipmentInstance::manufactureDate : String attribute (which is automatically translated into datatype IETF YANG DateAndTime), shall be represented as a String in YANG in future and the description shall change from
"This attribute represents the date on which this instance is manufactured."
towards
"This attribute represents the date on which this instance is manufactured. The date type is a profile of the ISO 8601 standard for representation of dates using the Gregorian calendar. The profile is defined by the full-date production in Section 5.6 of RFC 3339. Values shall follow the pattern: ^\d{4}-\d{2}-\d{2}$ . Reference: RFC 3339: Date and Time on the Internet: Timestamps".
These changes shall be executed during the UML2YANG tooling and will not be documented in any UML.

Implemented as decided.


source code formatting : scalariform

https://github.com/sbt/sbt-scalariform

https://github.com/daniel-trinh/scalariform

ScalaFmt seems to be getting some traction these days, might be worth considering:  https://github.com/olafurpg/scalafmt


feat(service): Add WhatsApp service

Is your feature request related to a problem? Please describe.
Missing support for the popular messaging platform WhatsApp.
Describe the solution you'd like
Implement a notification service like we already did for Telegram etc. At the time writing this Rhymen/go-whatsapp seems to be our best option for implementing it.

Hi @nikoksr, I'd like to give this a shot.

@checkaayush, hope things are going well. Let us know if you need any help!


support push to graphite

Codecov Report

Merging #1586 (95c9d34) into main (75142c9) will decrease coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1586      +/-   ##
==========================================
- Coverage   61.24%   61.13%   -0.11%
==========================================
  Files         133      133
  Lines       22415    22424       +9
==========================================
- Hits        13727    13708      -19
- Misses       7127     7153      +26
- Partials     1561     1563       +2

Impacted Files
Coverage Δ

pkg/fuse/context.go
56.75% <0.00%> (-10.82%)
:arrow_down:

pkg/meta/info.go
86.27% <0.00%> (-3.93%)
:arrow_down:

pkg/chunk/cached_store.go
75.08% <0.00%> (-1.55%)
:arrow_down:

pkg/vfs/reader.go
80.29% <0.00%> (-1.28%)
:arrow_down:

pkg/meta/base.go
71.54% <0.00%> (-0.51%)
:arrow_down:

pkg/meta/tkv.go
75.87% <0.00%> (-0.26%)
:arrow_down:

pkg/meta/redis.go
72.99% <0.00%> (+0.03%)
:arrow_up:

pkg/meta/sql.go
67.13% <0.00%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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

graphite:

pushgateway:


minor path problem

Minecraft version & Mod Version:
1.11.2 + latest 1.11.2 version ;)
Single player or Server:
Both
Describe problem (what you were doing / what happened):
wrong path Q:/CODE/minecraft/eclipseWorkspace/
(src/main/java/com/lothrazar/cyclicmagic/registry/RecipeFileWriter.java)
Crash log (if any):
no crash just a big log
https://gist.github.com/boosterdev/f55ce3cc9095192eb0372bea81caddb0

yeah good call, i meant to disable that before release oops

https://minecraft.curseforge.com/projects/cyclic/files/2456973


Cow: Watch muktika.in

Cow requests the watch of the watch_keyword muktika\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

muktika\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Dragonrage in Charcoal HQ


[Feature] Add a skip request function

I have checked the following:

[X] I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add
It will be useful to skip a request programmatically for example by testing a variable set by a previous request.
It could be useful to build more complex testing scenario.
Mockups or Images of the feature
This feature exists now in Postman

Yes, it is useful indeed, we also use it in postman.
So it could be the following syntax to be close to postman syntax:
// set a local variable to true
// change to false to see all tests get executed
const skipTest = true;

// this test will always be executed
test("Status code is 200", function () {
    expect(res.getStatus()).to.equal(200);
});

// this test will be skipped when skipTest is set to true
(skipTest ? test.skip : test)('Response time is less than 200ms', function () {
    expect(res.getResponseTime()).to.be.below(200);
});

The skipped tests need to be counted in reports like the failed and passed tests.

Hi i studied a solution and need some inputs
1 - Update Bru on packages/bruno-js/src/bru.js
Next to
  setNextRequest(nextRequest) {
    this.nextRequest = nextRequest;
  }

Add something like
  skipRequest() {
    this.skipRequest = true;
  }

2 - Update ScriptRuntime on packages/bruno-js/src/runtime/script-runtime.js
Exclusively on the function runRequestScript update the return to
    return {
      request,
      envVariables: cleanJson(envVariables),
      collectionVariables: cleanJson(collectionVariables),
      nextRequestName: bru.nextRequest,
      skipRequest : bru.skipRequest
    };

3 - Update the renderer:run-collection-folder on packages/bruno-electron/src/ipc/network/index.js
Before
    if (preRequestScriptResult?.nextRequestName !== undefined) {
        nextRequestName = preRequestScriptResult.nextRequestName;
    }

Add
    if (preRequestScriptResult?.skipRequest) {
        continue;
    }

Bonus:
Would be great to add the translation on packages/bruno-app/src/utils/importers/translators/postman_translation.js
From
pm.execution.skipRequest();
To
bru.skipRequest();

Hi, i made the improvement, how can i request publish access to create the feature branch and create the PR?
Check the result bellow

@helloanoop @lohxt1 I would like to contribute with this feature, how can i request push permissions?
What i got:

Looks like this has been built some months ago and awaiting to be merged into the main release. do we need the community to raise this visibility so that it can get prioritized?

Hi @ben-sai,
As you can see, @martinsefcik has suggested an improvement in the PR. Unfortunately, I haven’t been able to implement it in the past few weeks due to time constraints. However, I believe it would be best to incorporate this improvement before merging, so the feature can be at its best for all of us.

Confirm, important function.


JVM crash with Java 7 + Agent 1.3.0

Describe the bug
We updated apm agent to 1.3.0 yesterday and then after about 18 hours two instances got JVM crash which look pretty similar.
# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x000000008fb018d8, pid=122146, tid=140043922573056

Both are using Java 7 (7.0_75 and 7.0_141). One is running on Glassfish 4.0 and the other Payara <IP_ADDRESS>.1.
Debug logs
Current thread (0x00007f7ee0354800):  JavaThread "apm-reporter" daemon

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  0x000000008fb018d8

Also there is co.elastic.apm.agent.report.serialize.DslJsonSerializer::sanitizeTagKey in both compilation events.
Full logs:
hs_err_pid122146.log
hs_err_pid43918.log
This might be related to elastic/apm-agent-java#444

Looks like the issue still happens with this snapshot:
https://gist.github.com/TeroPihlaja/34567b0f778d0f2c759b2b53a61a5193

Bummer :(
Are you using the agent with newer Java versions (8+) for other applications? Do you see similar problems there? Or does that seem to be a Java 7 issue only?

@TeroPihlaja really sorry to hear that!
I see there are several errors occurring close to the time of the crash related to JNI. Unfortunately, there is not a lot of info to tell me where exactly the problem is. Could you run again with the following cmd-line arguments: -Xcheck:jni, -verbose:jni and if GDB is available, also -XX:OnError="gdb - %p"? Maybe we will have additional information in the applications logs, in addition to the crash log, to direct us to the root cause.
In addition, please add -Delastic.apm.flush_interval=200ms and let's see if it has any effect on the (very consistent) crash time.
Lastly, if you can try running the same on Java 8, that can be very insightful.
Thanks for your invaluable input!

We are running 1.3.0 with Java 8. This issue seems to only happen on Java 7.
I will try your suggestions and see what happens.

Another idea would be to disable compilation for the sanitizeTagKey method like this: -XX:CompileCommand=exclude,co.elastic.apm.agent.report.serialize.DslJsonSerializer::sanitizeTagKey

-Delastic.apm.flush_interval=200msdoes not seem to have any affect on the crash time on 1.3.0 release.
elapsed time: 50010 seconds (0d 13h 53m 30s)```

OK, that was a long shot. But what about additional data in the server logs? Anything new there that can provide additional info about JNI issues? Or any gdb logs?

Looks like those command line argument changes weren't actually in use yet. I will try again and let you know tomorrow (after it crashes again).
There's no gdb installed on this system and I'm not too familiar with it. If there's something specific you'd like to check from gdb I could probably install it on the server.

Nothing specific I know I am looking to get from gdb. I hoped this configuration could provide more info about the time of the crash. Looking forward to hear if there's any additional info in logs after the next crash.
Thanks a lot for your cooperation and input!

Have you tried out the -XX:CompileCommand option? That could be a workaround for this JVM bug.

test.log
hs_err_pid42129.log
Here's the logs with the -Xcheck:jni -verbose:jni set.
I will try -XX:CompileCommand=exclude,co.elastic.apm.agent.report.serialize.DslJsonSerializer::sanitizeTagKey next.

Tested with -XX:CompileCommand=exclude,co.elastic.apm.agent.report.serialize.DslJsonSerializer::sanitizeTagKey
Still seems to crash:
hs_err_pid94892.log

@TeroPihlaja thanks, that may be very valuable input. It seems that the compilation of java.lang.invoke.LambdaForm$NFI/1305645237::invoke_J_D is the root cause (where<PHONE_NUMBER> in this case is probably a dynamically allocated name). Let's try adding -XX:CompileCommand=exclude,*.invoke_J_D now and see if it resolves the problem.
Assumption: LambdaForms are intermediate Java representation for method handles that were introduced in order to replace the assembly code used previously for method handles implementation. In the JVM, long and double types are represented as J and D respectively (and this convention is used in LambdaForm). Our metrics collection relies on method handles of JMX bean operations and in some cases we use a method handle that returns long and cast it to double, e.g. https://github.com/elastic/apm-agent-java/blob/d83d37b33ea4ef1aa0904bb35394c21779db54bb/apm-agent-core/src/main/java/co/elastic/apm/agent/metrics/builtin/SystemMetrics.java#L119
Besides the compiled method name (invoke_J_D), two additional factors make me think this JVM bug was exposed by our metrics mechanism:

the fact that the java.lang.invoke.LambdaForm$NFI/*::invoke_J_D compilation event always happens at 49980 seconds, a round multiple of 30, our default metrics interval time
the fact that these invocations occur on the apm-reporter thread

This assumption may be validated by setting -Delastic.apm.metrics_interval=1s and testing if it affects the crash time. If you could try that out as well it would be really great.
Thanks!

metrics_interval=1s caused crash in 1668 seconds. Now running with invoke_J_D exclusion.

Crashed in 3333 seconds with invoke_J_D exclusion.
This time last compilation event is LambdaForm$DMH/1138273747::invokeStatic_J_D
hs_err_pid16940.log
RAX=0x00000000ec7ca4e8 is an oop
java.lang.Long
 - klass: 'java/lang/Long'

(gdb) x/4xg 0x00000000ec7ca4e8
0xec7ca4e8:     0x0000000000000005      0x000000008f4acfa8
0xec7ca4f8:     0x000000000e851000      0x0000000000000000

I added exclusion also for invokeStatic_J_D and started again

Awesome, seems like we are on the right track!
Thanks for your so valuable input! I hope this will bring it to an end. Looking forward to hear more.

There are now also three core dumps if you want to have a look. I'd rather not post them publically but I can email a link to you.

You mean invokeStatic_J_D did not solve the problem?

Apparently not... Crashed after 3334 seconds and now latest two are invoke_D_D and invokeStatic_D_D
hs_err_pid18872.log

In the last log I can still see
Compilation events (10 events):
...
Event: 3333.866 Thread 0x00007fc15c434800 3401             java.lang.invoke.LambdaForm$DMH/1138273747::invokeStatic_J_D (14 bytes)

What is the configuration you are using?

Command line is there also in log file. Basically:
pid 16940 exclude invoke_J_D
pid 18872 exclude invoke_J_D, invokeStatic_J_D
pid 20599 exclude invoke_J_D, invokeStatic_J_D, invoke_D_D, invokeStatic_D_D

hs_err_pid20599.log
And it seems to be working. 20599 stdout shows:
Checked JNI functions are being used to validate JNI usage
Checked JNI functions are being used to validate JNI usage
### Excluding compile: static java.lang.invoke.LambdaForm$DMH/1182538353::invokeStatic_J_D
### Excluding compile: static java.lang.invoke.LambdaForm$NFI/1234030171::invoke_D_D
### Excluding compile: static java.lang.invoke.LambdaForm$DMH/20383660::invokeStatic_D_D
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=20599, tid=0x00007fd01c0be700

Feels like all LambdaForm methods crash...

Thanks!!
If you just want to test the agent without metrics, you can disable metrics collection by setting -Delastic.apm.metrics_interval=0s.
However, if you still have the patience to bring this to full resolution, a few more steps will be very helpful:

look for the additional logs (like the test.log attached to https://github.com/elastic/apm-agent-java/issues/458#issuecomment-461722960) from the last crash and attach to the issue (I see that the -Xcheck:jni -verbose:jni -XX:OnError=gdb settings were used)
try it only with -XX:CompileCommand=exclude,*.invoke_J_D -XX:CompileCommand=exclude,*.invoke_L_J and remove the others.
if crashes- look for the additional logs and attach

Again, many thanks!

Attached pid20599 test.log
It seems strange,
Compiled method (c2) 3334885 3432             java.lang.invoke.LambdaForm$DMH/1207168383::invokeInterface_L_J (14 bytes)
Compiled method (c2) 3334887  470             java.lang.Long::<init> (10 bytes)
Compiled method (c2) 3334888 3431             java.lang.invoke.LambdaForm$NFI/1305645237::invoke_L_J (11 bytes)

OK, let's see what happens when only JIT compilation of invoke_L_J and invoke_J_D are disabled as suggested above.

New crash now with invoke_L_J and invoke_J_D excluded
# Problematic frame:
# J 2783 C2 java.lang.invoke.LambdaForm.basicTypeSignature()Ljava/lang/String; (59 bytes) @ 0x00007f2a910db864 [0x00007f2a910db300+0x564]

Compiled method (c2) 3333944 3370             java.lang.invoke.LambdaForm$NFI/486510138::invoke_L_J (11 bytes)

test-20190210_164814.log
hs_err_pid24029.log

And I apparently typoed L_J as L_D... Anyhow now with actually L_J it gets invoke_D_D crash.
test-20190210_174606.log
hs_err_pid25670.log

Ohh, I am so sorry about that 😫
But we will get there eventually.
Did you try -XX:CompileCommand=exclude,*.invoke_J_D -XX:CompileCommand=exclude,*.invoke_L_J -XX:CompileCommand=exclude,*.invoke_D_D already?

Now it has been running 14 hours without crashes (with metrics_interval=1s) so looks pretty good.
stdout shows
### Excluding compile: static java.lang.invoke.LambdaForm$NFI/991593213::invoke_J_D
### Excluding compile: static java.lang.invoke.LambdaForm$NFI/1305645237::invoke_L_J
### Excluding compile: static java.lang.invoke.LambdaForm$NFI/1234030171::invoke_D_D
### Excluding compile: static java.lang.invoke.LambdaForm$NFI/2013163400::invoke_L_D

Really glad to hear! If it's not a problem, please let it run another day to make sure it is resolved and then you would probably want to restore the metrics collection interval. Looking forward to hear back.

Note to self- notify users that reported the same problem at https://discuss.elastic.co/t/apm-agent-for-java-is-causing-system-crashes/165211

I think we should use reflection instead of method handles if the agent is running on Java 7.

I have created a PR which uses reflection as opposed to MethodHanldes to get metrics from the OperatingSystemMXBean. Could you try the attached snapshot and see if it helps? If so, we'll release a fix shortly.
Thanks so much for your help!
Btw: I was unable to reproduce the JVM crash on JDK 1.7.0u80 and Mac OS.

About 18h uptime now with 1.3.1-SNAPSHOT without any compile exclusions so seems to work.
1.3.0 with exclusions still ended up crashing after 17h uptime.
Last compiled method was java.lang.invoke.BoundMethodHandle$Species_LL::<init> and nothing else obvious to my eye. Really strange how well it breaks JVM :)
hs_err_pid27244.log
test-20190210_184348.log

Looks good! Thanks so much for you help!
We will probably make a release soon so you can switch to using that instead.

@Aketzu @TeroPihlaja 1.4.0 is released, feel free to switch to it at your convenience.

Wow, this is a strange issue.  Any idea what the root-cause is?
We encountered a similar crash/hung JVM with a custom agent, and it was hard to diagnose (with jdk 8u25).  We didn't use MethodHandles anywhere, but they seem to be referenced in the generated bytecode because of lambda functions.  Removing all lambda functions from our agent resolved the issue.

@jvimal which agent version are u using?

The root cause is a JVM bug which gets triggered when the JIT optimizes the MethodHandles. Those are used under the hood for Lambdas.

@lreuven - I am not using elastic agent.  I wrote an agent, and encountered the exact same issue mentioned here.
@felixbarny Yeah I figured lambdas were causing the issue.  However, I was curious if you had more details (e.g., a link to the JVM bug for more details).
The discussion on this issue thread was super helpful!  This was the only detailed thread I could find -- all the other threads I checked just mentioned that upgrading the jvm should resolve such issues.


Questions about training details of CodeBERT/GraphCodeBERT on clone detection task

A few questions about clone detection:

Q1: How is CodeBERT finetuned? There is no code, and I cannot reproduce the reported results by adapting the code of GraphCodeBERT.
Q2: The paper says that "The probability of true clone is calculated by dot product from the representation of [CLS]." But in the code here, the probability is actually calculated by concatenating two [CLS] representations then feeding them into MLP. Which one is correct?  Or my version of the paper is outdated?

Thanks and look forward to your reply.

same question,follwing code shows the probability is actually calculated by concatenating two [CLS] representations then feeding them into MLP
` def forward(self, inputs_ids_1,position_idx_1,attn_mask_1,inputs_ids_2,position_idx_2,attn_mask_2,labels=None):
bs,l=inputs_ids_1.size()
inputs_ids=torch.cat((inputs_ids_1.unsqueeze(1),inputs_ids_2.unsqueeze(1)),1).view(bs2,l)
position_idx=torch.cat((position_idx_1.unsqueeze(1),position_idx_2.unsqueeze(1)),1).view(bs2,l)
attn_mask=torch.cat((attn_mask_1.unsqueeze(1),attn_mask_2.unsqueeze(1)),1).view(bs*2,l,l)
    #embedding
    nodes_mask=position_idx.eq(0)
    token_mask=position_idx.ge(2)
    inputs_embeddings=self.encoder.roberta.embeddings.word_embeddings(inputs_ids)
    nodes_to_token_mask=nodes_mask[:,:,None]&token_mask[:,None,:]&attn_mask
    nodes_to_token_mask=nodes_to_token_mask/(nodes_to_token_mask.sum(-1)+1e-10)[:,:,None]
    avg_embeddings=torch.einsum("abc,acd->abd",nodes_to_token_mask,inputs_embeddings)
    inputs_embeddings=inputs_embeddings*(~nodes_mask)[:,:,None]+avg_embeddings*nodes_mask[:,:,None]

    outputs = self.encoder.roberta(inputs_embeds=inputs_embeddings,attention_mask=attn_mask,position_ids=position_idx,token_type_ids=position_idx.eq(-1).long())[0]`

I am also confused that in the CodeXGLUE repo, CodeBERT is finetuned by concatenating the source tokens instead of [CLS] rep, different from GraphCodeBERT of this repo. Any explanation? 🤔

sorry for late reply. Both CodeBERT and GraphCodeBERT concatenates [CLS] vector of two source code, and then feed the concatenated vector into a linear layer for binary classification. Please refer here and here.

这是来自QQ邮箱的假期自动回复邮件。您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。

sorry for late reply. Both CodeBERT and GraphCodeBERT concatenates [CLS] vector of two source code, and then feed the concatenated vector into a linear layer for binary classification. Please refer here and here.

OK, thanks!


Linux Support

I just recently learned about this program, but I see on the releases page there are just some .exe files. Are there any plans to support other operating systems?

The provided build command produces a Linux executable if you have devkitARM (or probably even just ARM binutils) installed. There isn't a binary release.

Reporting in that it builds fine on Linux. I'm on Void Linux and installing cross-arm-none-eabi is enough to have the toolchain to assemble the payload, base-devel for the host compiler.

Thanks for confirming. I'll close this then.

Thanks for confirming. I'll close this then.

Remember that depending on the distribution the packages will have different names, i.e. Ubuntu and Debian's packages are binutils-arm-none-eabi and gcc-arm-none-eabi + build-essentials for the host machine toolchain.


Enum naming convention

So I've noticed that there are two conventions as for the enums:

repeating the prefix: e.g. MOUSE_CURSOR_DEFAULT -> Raylib.MouseCursor.MOUSE_CURSOR_DEFAULT
not repeating the prefix: e.g.MOUSE_BUTTON_LEFT -> Raylib.MouseButton.LEFT

The shorter seam nicer but either is better than both imo.
Not sure if worth the hustle though - let me know; I can prepare a pr for that.

Originally I used the first one but they must be the second one. Thank you for the prs 😄


Write v3 changelog

Another todo issue so I don't forget to do it. These points need to be clearly documented in the Changelog: (incomplete list)
Visible changes

Generators
New application structure

CSS Modules
Tests next to components
Container/Component split

ImmutableJS
reselect
react-router-redux
express.js
Code splitting/chunking routes
Component testing
Remote testing
CSS linting
$ npm run pagespeed
Lint staged files precommit
Much more documentation

Under the hood changes

Switch to offline-plugin
Initialisation script
Windows compatibility
Finally added a CoC

First draft below

Changelog
react-boilerplate v3.0.0 is out, and it's a complete rewrite! :tada: We've focussed on becoming the place to start your next app with, no matter at what scale. This is the most solid starting point you could have, every single detail is taken care of. You focus on writing the app, we focus on making that as easy as pie.
Changes

Revamped Architecture: Following the incredible discussion in #27 (thanks everybody for sharing your thoughts), we now have the best redux application architecture there is. Following a domain-based approach, instead of separating files by concern we now group them by feature. This makes development and absolute joy, try it for yourself and you'll see!

Generators: Thanks to @somus, you can now run $ npm run generate in your terminal and immediately create new components, containers, sagas, routes and selectors! No more context switching, no more "Create new file, copy and paste that boilerplate structure, bla bla". npm run generate and done.

Testing setup: Thanks to @jbinto fighting through hell and back, testing is now a first-class citizen of this boilerplate. (the example app has 99% test coverage) Using Karma and enzyme unit tests are taken care of, with ngrok your local server is tunneled through and can be accessed for anywhere in the world – perfect for testing on different devices in different locations.

Documentation: Thanks to @oliverturner's monumental effort, this boilerplate has the best documentation one could wish for. Clearly explained usage guides, but also clearly explained removal guides for every single feature. This is a starting point, don't want to use a part of this app? Get rid of it quickly and easily without digging through tons of files.

New server setup: Thanks to @grabbou, we now use express.js to have production ready servers ready to go. Hot reloading is still as available as always, but adding a custom API or a non-react page to your application is now easier than ever!

Tons of small improvements: I cannot count the amount of small improvements this version includes. Everything, from linting pre-commit (@okonet) over code splitting to cross-operating-system compatibility is now solid and ready to go. You can't go wrong with this.

The incredibly @oliverturner strikes again and finished this in #267!


Fix s3_hook list_keys error

Fix AttributeError: 'dict' object has no attribute 'Key error
Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #1 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
- Coverage   73.41%   73.37%   -0.04%
==========================================
  Files         158      158
  Lines       11957    11957
==========================================
- Hits         8778     8774       -4
- Misses       3179     3183       +4

Impacted Files
Coverage Δ

airflow/hooks/S3_hook.py
53.57% <0%> (ø)
:arrow_up:

airflow/www/app.py
94.25% <0%> (-2.3%)
:arrow_down:

airflow/configuration.py
83.09% <0%> (-0.94%)
:arrow_down:

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 54c03f3...5249e6c. Read the comment docs.


Update-RiskyUserWatchlist

New Logic watchlist add/update - timer based this logic app weekly connects to Defender for Cloud App and pulls risky users, some user context information, threat score, and direct user url.
Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

@anki-narravula Please review and provide your approve.

@anki-narravula: Could you please review the watchlist. Thanks!

@devikamehra / rushriva : Could you please review the Playbooks.

@NikTripathi : Please review the watchlists.


Add ASAN job in CI

build with a list of leaks: https://github.com/eregon/yarp/actions/runs/11333924655/job/31519044817
cc @KJTsanaktsidis

So in https://github.com/eregon/yarp/actions/runs/11333924655/job/31519044817 there are reported leaks from:
regparse.c (just 1)
prism/prism.c (multiple)
prism/templates/src/node.c.erb (multiple)

Looks like it was all one leak that @peterzhu2118 fixed. It looks like this is detecting a leak that memcheck isn't. Peter do you know why that might be?

It looks like this leak is happening inside of Ruby. The heuristics in ruby_memcheck are being used for prism, which filters out memory leaks from Ruby.
https://github.com/ruby/prism/blob/fd899e856b9f31cc88794016581ae383efbaead4/rakelib/test.rake#L57

I think ASAN detect_leaks=1 and valgrind are complementary and might each find leaks the other doesn't find, but @peterzhu2118 or @KJTsanaktsidis probably know better.

Looks like it was all one leak that @peterzhu2118 fixed.

Nice, I guess https://github.com/ruby/ruby/commit/90aa6aefc4e351d3840cfd58872c5f42a11f4c7a was the fix.

I think ideally we'd have ASAN detect_leaks=1 and/or valgrind in CRuby to find leaks in CRuby sooner and catch them directly in CI. Given it's slow probably with a subset of test-all, sounds fine to me and certainly better than nothing.
And then in Prism the same, ASAN detect_leaks=1 and/or valgrind, to avoid Prism changes to introduce leaks without noticing.
Not sure how much overlap between the two tools though.
One upside of ASAN is it doesn't need to build valgrind from source every time, OTOH it's more effort to repro locally (need to build CRuby with ASAN).

I think ideally we'd have ASAN detect_leaks=1 and/or valgrind in CRuby to find leaks in CRuby sooner and catch them directly in CI.

This has been on my todo list but I haven't been able to find the time to push it past the finish line.

One upside of ASAN is it doesn't need to build valgrind from source every time

The issue is that the Valgrind in the apt repository was too old and had bugs. Looks like the valgrind in Ubuntu 24.04 is finally new enough (>= 3.20.0): https://packages.ubuntu.com/noble/valgrind

So what is the next step here — should we wait until this is a part of memcheck or try to add this separately? If we're going to add this separately I definitely want to add a suppression for this leak since I don't want it to be red when we merge.

I think waiting for adding valgrind and/or ASAN in CRuby CI would make most sense.
That way we don't add a(nother) job which would fail because of a leak in CRuby.
That's also what we need to make ruby-asan builds usable with detect_leaks=1: https://github.com/ruby/setup-ruby/pull/653

Another benefit in having this in CI is that it makes it easier for downstream gems (e.g. https://github.com/DataDog/dd-trace-rb/pull/3864 ) to enable ASAN testing without needing to deal with too many exceptions and whatnot ;)

I'll close this because I don't think it makes sense to merge until CRuby checks leaks in its CI.


For the first point, it is kind of confusing. I will filter FAKE_VIDEOS and return the value if res.title == searchString, but it seems like it would

For the first point, it is kind of confusing. I will filter FAKE_VIDEOS and return the value if res.title == searchString, but it seems like it would not pass.
Author: Thomas Chen
Slide: Local,Public

Can we close one of the two or do you think they have different questions?


Fix horizontal overflow bug on search bar

Make search bar behavior consistent on Firefox
Rudimentary fix for #3. The new behavior on Firefox will appear like so:

while the search bar on Chrome will continue behaving as before:

Thank you! I'll publish a new version now.


isystem doesn't find header files

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
The default FFLAGS sets -isystem $PREFIX/include. On C compilers, this seems to actually find headers, but gfortran doesn't, despite docs suggesting otherwise.
I don't know if this is a bug in gfortran, a bug in the build of this package, or just my failure to understand the difference between isystem and -I, but it seems to me that -I$PREFIX/include should be in FFLAGS, not (or not just) -isystem $PREFIX/include.
Example:
conda create -n test openmpi gfortran
conda activate -n test
gfortran -isystem $CONDA_PREFIX/include helloworld.f # fails to find mpif.h
gfortran $FFLAGS helloworld.f # same
gfortran -I $CONDA_PREFIX/include helloworld.f # succeeds

isystem change was quite a while back in #9
Installed packages
# packages in environment at /Users/minrk/conda/envs/ompi5:
#
# Name                    Version                   Build  Channel
ca-certificates           2024.6.2             hf0a4a13_0    conda-forge
cctools                   986                  h4c9edd9_0    conda-forge
cctools_osx-arm64         986                  hd11630f_0    conda-forge
clang                     18.1.6          default_h095aff0_0    conda-forge
clang-18                  18.1.6          default_h7c89ad4_0    conda-forge
clang_impl_osx-arm64      18.1.6              hc6ba8f9_15    conda-forge
clang_osx-arm64           18.1.6              h54d7cd3_15    conda-forge
clangxx                   18.1.6          default_h095aff0_0    conda-forge
compiler-rt               18.1.6               h28df8ea_0    conda-forge
compiler-rt_osx-arm64     18.1.6               h56c4e69_0    conda-forge
gfortran                  13.2.0               h1ca8e4b_1    conda-forge
gfortran_impl_osx-arm64   13.2.0               h252ada1_3    conda-forge
gfortran_osx-arm64        13.2.0               h57527a5_1    conda-forge
gmp                       6.3.0                hebf3989_1    conda-forge
icu                       73.2                 hc8870d7_0    conda-forge
isl                       0.26            imath32_h347afa1_101    conda-forge
ld64                      711                  h4c6efb1_0    conda-forge
ld64_osx-arm64            711                  h5e7191b_0    conda-forge
libclang-cpp18.1          18.1.6          default_h7c89ad4_0    conda-forge
libcxx                    17.0.6               h5f092b4_0    conda-forge
libevent                  2.1.12               h2757513_1    conda-forge
libgfortran               5.0.0           13_2_0_hd922786_3    conda-forge
libgfortran-devel_osx-arm64 13.2.0               h5d7a38c_3    conda-forge
libgfortran5              13.2.0               hf226fd6_3    conda-forge
libhwloc                  2.10.0          default_h7685b71_1001    conda-forge
libiconv                  1.17                 h0d3ecfb_2    conda-forge
libllvm18                 18.1.6               hdac5640_0    conda-forge
libxml2                   2.12.7               hab74291_0    conda-forge
libzlib                   1.3.1                hfb2fe0b_1    conda-forge
llvm-openmp               18.1.6               hde57baf_0    conda-forge
llvm-tools                18.1.6               hdac5640_0    conda-forge
mpc                       1.3.1                h91ba8db_0    conda-forge
mpfr                      4.2.1                h41d338b_1    conda-forge
mpi                       1.0                     openmpi    conda-forge
openmpi                   5.0.3              h324cb95_104    conda-forge
openssl                   3.3.0                hfb2fe0b_3    conda-forge
sigtool                   0.1.3                h44b9a77_0    conda-forge
tapi                      1100.0.11            he4954df_0    conda-forge
xz                        5.2.6                h57fd34a_0    conda-forge
zlib                      1.3.1                hfb2fe0b_1    conda-forge
zstd                      1.5.6                hb46c0d2_0    conda-forge

Environment info
mamba version : 1.5.8
     active environment : ompi5
    active env location : /Users/minrk/conda/envs/ompi5
            shell level : 3
       user config file : /Users/minrk/.condarc
 populated config files : /Users/minrk/conda/.condarc
                          /Users/minrk/.condarc
          conda version : 24.3.0
    conda-build version : 24.3.0
         python version : 3.10.13.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=m1
                          __conda=24.3.0=0
                          __osx=14.5=0
                          __unix=0=0
       base environment : /Users/minrk/conda  (writable)
      conda av data dir : /Users/minrk/conda/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/minrk/label/fenics-windows/osx-arm64
                          https://conda.anaconda.org/minrk/label/fenics-windows/noarch
                          https://conda.anaconda.org/conda-forge/osx-arm64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /Users/minrk/conda/pkgs
                          /Users/minrk/.conda/pkgs
       envs directories : /Users/minrk/conda/envs
                          /Users/minrk/.conda/envs
               platform : osx-arm64
             user-agent : conda/24.3.0 requests/2.31.0 CPython/3.10.13 Darwin/23.5.0 OSX/14.5 solver/libmamba conda-libmamba-solver/23.11.1 libmambapy/1.5.8
                UID:GID : 501:20
             netrc file : /Users/minrk/.netrc
           offline mode : False

It seems like this is an upstream bug for sure. Maybe @isuruf can help us make a patch?

also reported on compiler activation with I think more detailed informatino: https://github.com/conda-forge/ctng-compiler-activation-feedstock/issues/124


CelebA

Hi, I want to know how to use the pretrain model of CelebA in your code? I load it unsuccessfully.

Solve it. ckpt.pth is a list and ckpt.pth[4] is the checkpoint of the model.


Make it possible to exit InGame scenes, via song end and pause menu

Ha, actually still no exit on song end, imma reopen this to torture myself


[BUG] Blank query parameters are dropped in _quote_path_and_params method

Describe the bug
The _quote_path_and_params method seems to drop query parameters with blank values. When a URL with a query parameter that has an empty value is sent, the parameter gets lost during processing. This behavior changes the request URL and can lead to unintended requests.
To Reproduce
from curl_cffi import requests

url = "https://example.com/api?param1=value1&param2=&param3=value3"
response = requests.get(url)
print(response.url)

Output:
https://example.com/api?param1=value1&param3=value3

The param2 parameter is omitted from the final request, even though it was included in the original URL.
Expected behavior
The URL should be sent as it is, including parameters with empty values:
https://example.com/api?param1=value1&param2=&param3=value3

Versions

OS: Ubuntu 22.04
curl_cffi version 0.7.3

Additional context

This behavior does not occur when using requests library, which retain empty query parameters as expected.
Possible fix: Modify the _quote_path_and_params method to use keep_blank_values=True with parse_qsl to ensure empty parameters are retained.
Workaround: You can bypass this issue by using quote=False in the request, like this: requests.get(url, quote=False).

@lexiforest I see that you fixed this issue. Can you tell when this fix will be released?


release-auth.now.sh is down

When going to release-auth.now.sh, I currently see an 502 error. The logs are:
▲ npm install
01/02/17 11:09:06 AM
Installing package<EMAIL_ADDRESS>01/02/17 11:09:07 AM
Installing package<EMAIL_ADDRESS>01/02/17 11:09:07 AM
Installing package<EMAIL_ADDRESS>01/02/17 11:09:07 AM
Installing package<EMAIL_ADDRESS>01/02/17 11:09:16 AM
▲ npm start
01/02/17 11:09:17 AM
> Ready! Listening on http://<IP_ADDRESS>:5000
01/04/17 2:20:21 AM
TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.
    at fromObject (buffer.js:284:9)
    at Function.Buffer.from (buffer.js:116:10)
    at new Buffer (buffer.js:95:17)
    at /home/nowuser/src/index.js:61:29
    at Generator.next (<anonymous>)
    at c (/home/nowuser/src/index.js:94:99)
    at process._tickCallback (internal/process/next_tick.js:103:7)

Should work now!


Sign In gives generic error message

I am using VSCodium and have an entirely different (but similar in nature) issue with sign-in. When I click the "Sign-in" button in the extension, I get an error dialog :

Extension version: v0.48.1
VSCode Version: (VSCodium) 1.70.2 Release: 22230
OS: macOS Monterey Version 12.5.1

VSCodium Info
Version: 1.70.2
Release: 22230
Commit: 6c122d9b2d1af2c37bd55caad614321eb53b342f
Date: 2022-08-18T04:12:18.598Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0

Steps to Reproduce:

Open the GitHub Tab and click Signin
Get error message

Extension Logs:
7-GitHub Pull Request.log
[Info] Error signing in to GitHub: HttpError: Bad credentials
[Info] HttpError: Bad credentials
	at /Users/billybryant/.vscode-oss/extensions/github.vscode-pull-request-github-0.48.1/dist/extension.js:1131:6173
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async S1.setCurrentUser (/Users/billybryant/.vscode-oss/extensions/github.vscode-pull-request-github-0.48.1/dist/extension.js:1148:16819)
	at async S1.createHub (/Users/billybryant/.vscode-oss/extensions/github.vscode-pull-request-github-0.48.1/dist/extension.js:1148:18000)
	at async S1.login (/Users/billybryant/.vscode-oss/extensions/github.vscode-pull-request-github-0.48.1/dist/extension.js:1148:15989)
	at async Sm.authenticate (/Users/billybryant/.vscode-oss/extensions/github.vscode-pull-request-github-0.48.1/dist/extension.js:1266:18461)
	at async /Users/billybryant/.vscode-oss/extensions/github.vscode-pull-request-github-0.48.1/dist/extension.js:1266:6905
	at async a._executeContributedCommand (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:85:63914)

@TylerLeonhardt we also saw this with on @joaomoreno machine with VS Code. A log out and log back in solved it.

@billyjbryant can you provide the contents of the GitHub Authentication output pane:

And also anything that shows up in Dev Tools:

ctrl + shift + P
"Dev Tools"

I've hit this now too. The error doesn't occur when calling the auth extension API. Instead, it happens when I try to use the auth token returned from the API to use GitHub API. It seems like the token is no longer valid.
There is nothing useful in the dev tools.
Here's the output, cleared just before the auth call:
[Info  - 12:19:16.240] Getting sessions for read:user,repo,user:email,workflow...
[Info  - 12:19:16.241] Got 1 sessions for read:user,repo,user:email,workflow...

@cbrnr can you please share a gif/video of you logging in? you can use a tool like gifcap.dev to do this.

Thanks for the quick response! Today the extension is working again. It seems like yesterday there were some server issues, which would explain the rate limit message and failed login attempts. Maybe @billyjbryant and @alexr00 can check if the issue has resolved itself for them as well?

Today, the issue came back. First, I got that rate limit exceeded message, and after that I cannot log in:
https://user-images.githubusercontent.com/4377312/190321866-9f838997-d394-410f-af44-ec260aa3e34a.mov

@cbrnr where you opening lots of windows or reloading the window a lot before you saw the rate limit error? We shouldn't be hitting that rate limit, but once it's hit you can't sign in.

I don't think so - at least not on purpose. FWIW, I never shut down my computer, so maybe some connections do not get reset? I do restart VS Code quite often though, and I tried in this case, but it didn't help. I am now signed in again, this seems to have happened automatically at some point.

@cbrnr I added a lot of rate limit logging in the pre-release version of the extension. If you see the rate limit error again, could you please share the output of "GitHub Pull Request" over in https://github.com/microsoft/vscode-pull-request-github/issues/3847?

The rate limit issue has been fixed. We don't have enough info continue investigating the bad credentials issue.


Support post hook when creating a service/container

Provide the ability for a user to execute a post script on a host when launching a container or service.  This could be in the form of creating this action based on a label and when a container runs, our agents will execute the post scripts on the host.  Users would also be required to ensure the scripts exist on the host beforehand.

This will be part of the API Interceptor feature.


Can't cycle through command history using the down-arrow

Windows Terminal version
1.21.2911.0
Windows build number
10.0.22631.4391
Other Software
No response
Steps to reproduce
I used to be able to run
> echo 1
1
> echo 2
2
> echo 3
3

and then press UP ARROW three times to repeat echo 1 and then DOWN ARROW to cycle through echo 2, echo 3, echo 1, etc. Now the first DOWN ARROW does nothing.
I think both Command Prompt and PowerShell had this behavior. I do know I used that pattern of cycling through the history for Command Prompt quite frequently, but now I find that I must press UP ARROW three times each time I want to cycle through the last three commands. It would be nice to have the old behavior back.
I haven't found any documentation or bug reports that addresses this issue. Thanks in advance for your help.
Expected Behavior
After pressing UP ARROW three times and ENTER to execute the third command back in history, I expected pressing DOWN ARROW followed by ENTER to execute each of the past 3 commands in sequence ad infinitum.
Actual Behavior
After pressing UP ARROW three times and ENTER to execute the third command back in history, pressing DOWN ARROW does nothing. No previous command is recalled from history.

As a temporary measure, downgrading to release v1.21.2361.0 or lower rolls back this change.

Thank you. I rolled back to v1.21.2361.0. I look forward to the release of v1.23.

Apparently that's how cmd has always worked if "Discard old duplicates" is enabled, huh. I wonder if I should double-down by changing the "Discard old duplicates" behavior and and this "circling" that you describe, or if I should revert enabling it by default under Windows Terminal.

i think a problem here is that the "replay" behaviour working consistently is dependent on not deleting old duplicate commands, since if you delete an old duplicate, you change the command sequence
i.e. with dedup
cls
echo 1
echo 2
echo 3
...
echo 2

means that "replaying" from cls onwards would then run
cls
echo 1
echo 3

i think that, if there can't be configuration on the user end, not having dedup is the better option since the only downside (afaik) is that it's inefficient usage of the history buffer (and to my knowledge that shoudn't be an issue if the history buffer is set to any reasonable size)


Not an issue but a "Thank you"

I just needed to voice my appreciation for this app.
I have an extremely complex settings file for this app which lets me perform my most commonly needed commands on dozens of servers with everything all nested in relevant submenus perfectly.
This app makes my life better on a (literally) daily basis.
So thanks to all those involved.

Hi @JayHoltslander Thanks for the kind words! Glad it helps :)

I also want to give you a big THANK YOU for this app! I use it on a daily basis and it really makes my life easy! I even did a little shell script to get all the instances from my company's AWS account and create a shuttle config with iTerm as my terminal app, easy shuttle config update in 10 seconds!


Custom column name and decrement

Hello. I have problem with decrement counter value.
I have review for companies with statuses: moderate, active, disabled.
For default review has status 'moderate', after i change status to 'active' counter cache +1
Code:
counter_culture :company, column_name: Proc.new {|model| model.status == 'active' ? 'reviews_count' : nil }
After that i change status to 'disabled' i my counter cache didn't dectment, which is logical. How i can user counter_culture for decrement counter_cache when i change review status to 'moderated' or 'disabled' from 'active'?

Actually, that should have worked. I have specs in place that test for this, so I doubt there's a specific bug here. If so, I'd need a failing test that shows this for me to dig further on it.
Are you perhaps updating the column without callbacks? Then counter_culture can't work.

Excuse me, my fault


output parsers: add structured and list

Add structured output parser. The implementation is most similar to the python implementation: https://github.com/hwchase17/langchain/blob/master/langchain/output_parsers/structured.py
And does the same as from names and descriptions in the ts version: https://github.com/hwchase17/langchainjs/blob/main/langchain/src/output_parsers/structured.ts
Add response schema struct used in the structured output parser. This is like the python version.
Add comma separated list.
https://github.com/hwchase17/langchainjs/blob/main/langchain/src/output_parsers/list.ts
https://github.com/hwchase17/langchain/blob/master/langchain/output_parsers/list.py
Add parse with prompt to interface to match python and ts version and increase flexibility.

PR Checklist

[x] Read the Contributing documentation.
[x] Read the Code of conduct documentation.
[x] Name your Pull Request title clearly, concisely, and prefixed with the name of primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Describes source of new concepts.
[x] References existing implementations as appropriate.
[x] Contains test coverage for new functions.
[ ] Passes all golangci-lint checks.
[x] (remove and do not use this row unless you are a trusted contributor) I am an existing
contributor.

Some of the lines in the test files are a bit long so the lint does not pass.

@FluffyKebab this grew a couple of conflicts, can you rebase?


Change documentation main page

Codecov Report
Patch coverage has no change and project coverage change: -0.06% :warning:

Comparison is base (4b6e049) 83.02% compared to head (9e34a9c) 82.96%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #39      +/-   ##
==========================================
- Coverage   83.02%   82.96%   -0.06%
==========================================
  Files          38       38
  Lines        5419     5419
==========================================
- Hits         4499     4496       -3
- Misses        920      923       +3

see 3 files with indirect coverage changes

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


Add missing Send/Sync impls

Forgot these in https://github.com/amethyst/shred/pull/223!

Miri failure? Hopefully nothing important

Miri failure? Hopefully nothing important

This is to be expected for now. MetaTable does some very questionable stuff with vtable pointers. I haven't ran into tests (in specs) that fail Miri due to this yet so I'm not focusing on it (but I would like to have reminder of Miri failing). Unfortunately, github CI lacks ability to have a CI check that is allowed to fail without showing red X https://github.com/orgs/community/discussions/15452. IIRC I think MetaTable is used for potential scripting support.


Show "Content disabled in Edit Mode" in user's language

What about showing the "Content disabled in Edit Mode" using the user's language and not the page one?

Example: I'm logged in by specifying I want English. and I edit a page in Italian.
Before we had:

With this PR we have:

This looks great (although I think another pull request has conflicted with this one). One question – what do you think about creating t() functions specifically for these contexts? Like
tui
t2ui
tcui
?
This is just off the top of my head – the function would basically just add the UI context, output the string, and then remove it. But it might make it cleaner to do this throughout the core?  Obviously having tons of tiny functions name like this might make things more confusing so I'm not married to the approach, just thinking about how we might make this easier to do in the future.

One question – what do you think about creating t() functions specifically for these contexts? Like
tui
t2ui
tcui
?

If we do that, we should add the site functions too (tsite, t2site, tcsite), and that starts polluting the environment...

Just an odd idea... What about something like this?
namespace {
    function t() { /* ... */ }
    function tc() { /* ... */ }
    function t2() { /* ... */ }
}

namespace t {
    function ui() { /* ... */ }
    function site() { /* ... */ }
}

namespace tc {
    function ui() { /* ... */ }
    function site() { /* ... */ }
}

namespace t2 {
    function ui() { /* ... */ }
    function site() { /* ... */ }
}

that way, we'd have t('...'), \t\ui('...'), ---

This looks great (although I think another pull request has conflicted with this one).

Conflicts resolved


user is undefined, returned from useUser in 1.4.2

Since 1.4.2, after trying to login, useUser returns undefined for user.
running supabaseClient.auth.user() does returns a user.
downgrading to 1.4.1 solves the problem

This library will no longer be maintained and I would advice you migrate to @supabase/auth-helpers-nextjs instead.


Clarification bout rescued circular contigs

Thanks for the work in MetaMDBG!
In the README you mention that the _rc suffix flags "rescued circular " contigs and that the circularity of such sequences is not as reliable. However, I couldn't find a more in depth explanation of what these rescued circular contigs are and why their circularity needs to be further validated.
Can you provide an explanation of what exactly "rescued circular" stands for?

These are long linear contigs (~ >1Mb) with both ends very close in the assembly graph (typically separated by a single unitig). This unitig is probably a long repeat. If this repeat is a inter-genomic repeat, the rescued contig is likely to be complete. The problem is that it can be an intra-genomic repeat, in this case the rescued contig will probably be incomplete.

Thanks @GaetanBenoitDev! This makes sense to me
I got an additional question about circular contigs: I've noticed that I got some circular contigs with long terminal repeats (between 7.5 and 10kb), which I assumed collapsed when the contig was extracted from the assembly graph. I also have some contigs that contain one or more repetitions of the same unit. See below the average frequencies of 21-mers for 10 circular contigs of an assembly (FASTA file here):
ctg96262_7x_c	1.0019
ctg93556_5x_c	1.0007
ctg90807_4x_c	1.7587
ctg92161_1x_c	1.4486
ctg86413_0x_c	4.2598
ctg85961_0x_c	6.5512
ctg89183_0x_c	1.4074
ctg85018_0x_c	6.3019
ctg91152_1x_c	1.7125
ctg86752_23x_c	4.3003

ctg92161_1x_c is a contig with terminal repeats ~7.5kb (that is, has a repetition of the first 7.5kb of the "unit"). ctg90807_4x_c is a contig with a complete unit plus a repetition of the first 75% basepairs of that same unit.
Is this sort of assembly expected?

I have removed the rescued circular process in the v1.0

I have removed the rescued circular concept in the v1.0


transaction-management project #280

Title : transaction-management
Issue No. : #280
Code Stack :  React,firebase
Close #280
Video
https://github.com/apu52/METAVERSE/assets/136250383/f779df00-facd-45fc-8c03-e27895f0d2f2
changes made by me:

Added project folder in Projects

Added images in assets/img

Added project information in projectsData.json

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] I have updated the projectData.json file for my contribution
[X] I have added the img of my project in the assets/img section

Additional context
Are you contributing under any Open-source programme?

Codepeak '23
KWOC

@apu52 Could you check this PR please.

It is a great project......thank you for youe contribution.
HAPPY CODING !!!!


mysql(ticdc): Add a tableInfo cache to reduce the memory and cpu overhead of BuildTiDBTableInfo

What problem does this PR solve?

Issue Number: close #xxx
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

This problem is completely and beautifully solve by https://github.com/pingcap/tiflow/pull/10483.


refactor methods for filling authors / creators

currently, the cognitive complexity is a bit much:
https://github.com/citation-file-format/cff-converter-python/blob/469715d2ebebb72cdd46190065e2cf2d7490da06/cffconvert/behavior_shared/schemaorg.py#L67-L104

[x] apalike
[x] bibtex
[x] codemeta
[x] endnote
[x] ris
[x] schemaorg
[x] zenodo

This issue includes:

#142
#177
#179

All done, closing


is this gonna be a web port??

I was literally doing that

its only loading to 13%

Only loading at 13% because it's missing half of the files, I have to manually upload them because I don't have any other device that I can upload the files directly to the repo.

ohh i see if you like i an help

Nah its fine, im gonna finish uploading all the stuff soon

ah okay

Also this repo is meant to be only for web builds, can be built for desktop too but the main purpose of this its to port old mods to web but my work is amazingly trash

BRO THIS THING ISNT PUSHING TO THE BRANCHHHHHHHHH

Ok done, had to manually push it lol, haven't checked if it works or if it doesn't, but once the page is reloaded I will close the issue

Stuck at 87%, I think its something related to flxg mouse

Ok seems to be working now, enjoy!


[Digital-Twins] Update for GA, rename namespace, add span

Hi @bterlson , we need this package to be released ASAP for a final bug bash before GA release-- can we please get a review? Do you need any other information from us? These are minor updates from the already released preview package for digital twins.

@zolvarga Update on the naming: @bterlson  and I are good with @azure/digital-twins-core. If you can clean up the missing api-extractor type exports, and consider the maxPageSize alignment, I think this change will be ready to ship.


Import and module are implemented counterintuitive

Currently, the import system seems to work like this:
The import "path" needs to be relative to the directory you call the effekt compiler from.
For example:
- root
    - foo.effekt
    - bar.effekt

foo.effekt:
module root/foo
def foo() = ()

bar.effekt
module root/bar
import root/foo
def bar() = foo()

Running this from root will with:
PATH\root> effekt bar.effekt
will lead to:
bar.effekt:2:1: Cannot find source for root/foo
But will work when run from PATH
This is not intuitive and leads to long import and module statements.
Solution
I think the module statements should be relative to the folder the effekt file lives in. So there is a mapping between folders and modules. The module's child and parent relationship corresponds to the folder hierarchy.
Import statement should import from the declared modules. The file should not need to know where the module is to import from it, otherwise it is counterintuitive to modules. Just as it works with the standard library.

I am currently looking into this issue.
I print every import in the Namers resolve function. I changed line 59-61 to:
 val imports = decl.imports collect {
      case im @ source.Import(path) =>
        Context.at(im) {
          println(Context.module.source.name)
          processDependency(path) }
    }

For a file that imports nothing, I expected the output to be nothing. But actually the output is:
..\effekt\libraries\js\immutable\option.effekt
..\effekt\libraries\js\immutable\list.effekt
..\libraries\js\immutable\list.effekt

Somehow, this is imported, even when not used by the file.
Also, the standard library files are resolved with an absolute path, while every other import is resolved with a relative path (relative to the working directory!). That seems odd.

Tree.scala:
/**
 * The type of whole compilation units
 *
 * Only a subset of definitions (FunDef and EffDef) is allowed on the toplevel
 *
 * A module declaration, the path should be an Effekt include path, not a system dependent file path
 *
 */
case class ModuleDecl(path: String, imports: List[Import], defs: List[Def]) extends Tree
case class Import(path: String) extends Tree

How is an "Effekt include path" defined, and why should it not be a system file path?

Thanks for looking into it. 👍
First of all, what is a system file path? They are slightly different between operating systems (especially Windows...). Also, the language should work on the website with a virtualized unix file system.
I have been thinking about the design of name spacing, modules, dependencies, etc. Here are two observations:

it is almost impossible to find a good individual solution without considering the other aspects.
name spaces, modules, and file paths should not be conflated (they currently are).

I don't want to belittle your approach; I think you are right and we definitely need to do something. I would be very happy if you would be interested in driving this change, but we need a somewhat holistic solution.

I think we should separate (at least) two different use cases:

"scripting use"
"project use"

I believe (but might be wrong) that in scripting use we might require/import/include resources relatively or absolutely given source paths.
In project use, having a global project config and automatically important ALL files as specified in the project config might be a better option.
This should also interact well with generalizing paths to URIs, like gist files etc. It should also integrate well with git-based dependency management.
In script mode, I can imagine to write something like:
include git://otherproject.git#a136f451

def foo() = ...

which should result in cloning the repo somewhere, checking out the specified commit, building the project, and bringing the symbols into scope (this should also work in the REPL, btw.).
In a project mode, it might make more sense to specify this as a dependency in a config file.

@jiribenes pointed out that Go had bad experiences with using git to distribute packages.

I agree that we should separate by use cases. I have a hard time understanding the current parsing step. When are the import files parsed? Are they parsed somewhere here for jvm:
https://github.com/effekt-lang/effekt/blob/ff76871e5971fb8a9e730ddc0bf90efcaa76ff56/effekt/jvm/src/main/scala/effekt/context/IOModuleDB.scala#L27 :
I would like to go further with the project approach like this:

As you suggested, having a sort of configuration file, where all modules are specified.
Parse every file for every module specified and create a Source for every module / file
The Namer should resolve name conflicts.
Load the symbols accordingly.

I know that is oversimplified. But I hope you get the idea.

Just to avoid confusion, before proceeding with an ad-hoc design, it would be wise to consider all of the wildly differing aspects of what a module is / can be:

unit of compilation (think LLVM modules, allow for separate compilation)
unit of code organization (a namespace)
unit of code reuse / polymorphism (think ML modules)
unit of code sharing (think packages that people can share)

In turn, this raises multiple questions such as:

Which of those are conflated and why? What are the consequences of conflating them? (Languages that do unify them often make heavy trade-offs!)
Which one of those is a unit of versioning code? Or is that a completely separate notion?
What does an import statement refer to? Unit of compilation? Unit of code sharing? Both?

Note that the decisions made around modules will have far-reaching consequences rippling into the rest of the language, so caution and proper planning must be employed.
For reference, here's a related issue in this repo with a preliminary module design: https://github.com/effekt-lang/effekt/issues/30


refactor(components): align all icons integrations with affix pattern

In a second thought we decided to stop and think.
Not all places that use icon need the affix. Maybe we need an icon pattern?
More style is related to affix pattern.
Will be decided later.
Line height:1 will be added to the style of each component where is needed.

was solved differently in here:
https://github.com/Vonage/vivid-3/pull/951


[tracking] Update list code owners in insights-results-aggregator-utils repository

Update list code owners in insights-results-aggregator-utils repository

Done, there: https://github.com/RedHatInsights/insights-results-aggregator-utils/blob/master/CODEOWNERS


Sharing through Zulip Android mobile App

Hi guys,
My team usually uses Zulip Android mobile app as a way to share their work or links. We all like the mobile app and like the good work you guys are putting into this project. We are wondering if we can have Zulip disappear after the share action completes. For example, if we are on a browser and want to share a website, we would get a list of apps to choose from. We would then select Zulip, choose the stream/topic, and hit send . Right now, after we hit send we don't get our browser back but we would be left inside Zulip.
Is it possible to change the way share works through Zulip Android app? We would all be so grateful to have this feature added to the Android mobile app.
Thanks

@marboxvel Thanks for reporting this, You're talking about the other android app we have
This one https://github.com/zulip/zulip-android | https://play.google.com/store/apps/details?id=com.zulip.android, right?
And this feature is not available in this app.

We would then select Zulip, choose the stream/topic, and hit send . Right now, after we hit send we don't get our browser back but we would be left inside Zulip.

Terminating the app on a message send would not be a good idea, maybe we could have a close button on the top or somewhere.
Anyways that project doesn't have any active development going on and we are focusing to improve this one! :)

I am not sure what the zulip-android project had exactly... is it something like what @vishwesh3 had done (that I'll try to work with him to merge soon) https://github.com/zulip/zulip-mobile/pull/674

@kunall17 Thanks for the quick reply. I'm talking about the one I got when I clicked the google store link you provided, the one that says "Native Android app for the Zulip open source group chat software".
Of course I didn't mean that whenever you hit send the app should exit.  I'm talking about a scenario where you are on a different app, flipboard for example, and you want to share an article with the team. Wouldn't you prefer that after you finish sharing you get back to flipboard? why would you want to stay in Zulip and hit back or exit in order to get back to whatever the app you originally shared the article from?
Many apps have this functionality implemented, you may check Slack for example.
@borisyankov Are you saying that the one @vishwesh3 is working on has this feature implemented? #674
Thanks guys for the hard work.

@marboxvel this is an improvement made in our new Android + iOS app (that will very soon replace the one you are using).
Actually, this might be a good time to ask you to have a look at the one that says 'Unreleased'. Any comments or issues you might have, we want to address them before the release.

@borisyankov Sure. I would love to give you a hand. I already installed it. It looks more sleek than the official one, but it doesn't show up in the share list at all.

Yeah, this PR is not yet merged. We would like to actually replace the current app with this one in the app store, so before we do that we need to make sure any feature that existed is at least as good or better than before. Any feedback in that regards of our current users is welcome 👍

The app still doesn't show up in the share list, what could be the reason @borisyankov ? I would like to fix that.

@pulkonet soon it will be in master. #674

I believe this was a dupe of #117 (after sorting out the confusingness of our legacy app) -- closing in favor of that issue.