[BUG] Image urls in bundled code are incorrect

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager yarn
[x] I run Snowpack on OS *Mac
[x] I run Snowpack on Node.js v12+

Describe the bug
Links to external images in code bundled with esbuild  are incorrect.
To Reproduce
My  snowpack.config.mjs looks like this:
/** @type {import("snowpack").SnowpackUserConfig } */
export default {
  mount: {
    public: "/",
    src: '/dist'
  },
  plugins: [
    '@snowpack/plugin-react-refresh',
    '@snowpack/plugin-typescript'
  ],
  optimize: {
    bundle: true,
    target: 'es2015',
  },
};

My code structure:

Component importing an image:
/src/App/App.tsx:
import React, {useState, useEffect} from 'react';
import logo from './logo.svg';
...
<img src={logo} className="App-logo" alt="logo" />

The logo.svg ends up in build/dist/App/logo.svg, but the bundled App file (loaded from index.html via /dist/index.js) still references the logo via ./logo.svg. The component path is missing:

Build output:

Compiled App in index.js:

Link to reproduction repo: https://github.com/gustaff-weldon/snowpack-spike
Just run the yarn build and open index.html (I use python -m SimpleHTTPServer to serve it)
Expected behavior
Links to external images in bundled code are properly built. Eg, in the example above link to image should be rewritten to ./dist/App/logo.svg
Anything else?
Happy to provide more information if needed

This is indeed a bug! Thank you. Will investigate a fix.

Ran into this issue as well. A quick workaround is to inline the assets with snowpack-plugin-inliner. Not ideal if you have large images, but it was sufficient for my project.


Clear cache after site install

Resolves #392

Since this PR is basically your code I am feeling OK to merge this. Hoping this stops the failures from showing up in #bots in Islandora Slack.


feat!: support unversioned data

Useful for agct and cool-seq-tool

@jsstevenson I think we should come up lab rules to determine who is assigned to a PR. I typically follow that it is the person who will ultimately be closing or merging the PR. I think instead I should be listed as a reviewer (I usually go here to see what PRs I need to review).

@korikuzma oh, that's my bad -- I think I accidentally hit the wrong dropdown (I think I do this a lot). agreed re: protocol


Fix rpcbind not enabled at startup with Raspbian Jessie Lite

Apparently the version of rpcbind that's currently shipping with Raspbian Jessie Lite is causing some issues at startup that cause the NFS server running on the first webserver to fail.
If I run sudo systemctl status nfs-kernel-server it shows the following error:
Not starting: portmapper is not running ...

I tried working around it by manually adding in the following in the nfs.yml playbook, but that didn't work after the first provision (e.g. it would start failing after a reboot, and the NFS shares would not be shared, so mounts fail):
- name: Ensure rpcbind is running for Raspbian.
  service: name=rpcbind state=started enabled=yes
  register: rpcbind_start
  when: deploy_target == 'pi'

- name: Force restart NFS if rpcbind wasn't started.
  service: "name={{ nfs_server_daemon }} state=restarted"
  when: rpcbind_start.changed

So the next step is to see about installing the latest release of rpcbind, which might work correctly with systemd/Jessie... See: https://www.raspberrypi.org/forums/viewtopic.php?t=128816&p=862161#p862161

Looks like the rpcbind install that is loaded by default in Raspbian might be at fault, so I'm going to test purging it before starting the NFS install (as part of the earliest config for the webservers), and we'll see if that works... See: http://raspberrypi.stackexchange.com/a/24914/6506

This solution does not survive a reboot on Linux diluvo 4.4.34-v7+ #930 SMP Wed Nov 23 15:20:41 GMT 2016 armv7l GNU/Linux.

@daurigi - D'oh! Can you open a new issue for that?

The problem is with the runlevels for nfs-common and rpcbind. These are the most clear (and working solutions) I found. http://lesca.me/archives/debian-or-raspbian-nfs-kernel-server-not-starting-portmapper-is-not-running.html and, http://raspberrypi.stackexchange.com/a/54472. As David mentions in his comment, a NFS upgrade might get your problem back.

Subscribed, seeing same issue on Pi2 and Pi3 with Jesie-lite

Hi, I had similar problems with Jesse lite 2016-02-09 and 2017-02-16 (latest uses rpcbind 0.2.1-6). The server-side fix I used is based on something that hasn't yet made it downstream to production, but see the references below for info.
# credit [https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=149002&p=980161]
# Original [https://lists.debian.org/debian-devel/2014/05/msg00618.html]

cat <<EOF | sudo tee -a /etc/systemd/system/nfs-common.services
[Unit]
Description=NFS Common daemons
Wants=remote-fs-pre.target
DefaultDependencies=no

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/etc/init.d/nfs-common start
ExecStop=/etc/init.d/nfs-common stop

[Install]
WantedBy=sysinit.target
EOF

cat <<EOF | sudo tee -a /etc/systemd/system/rpcbind.service
[Unit]
Description=RPC bind portmap service
After=systemd-tmpfiles-setup.service
Wants=remote-fs-pre.target
Before=remote-fs-pre.target
DefaultDependencies=no

[Service]
ExecStart=/sbin/rpcbind -f -w
KillMode=process
Restart=on-failure

[Install]
WantedBy=sysinit.target
Alias=portmap
EOF

sudo systemctl enable nfs-common
sudo systemctl enable rpcbind
sudo reboot

Hope this helps :)


Basic support for KDBX4 with DOM

Changes

Write to and save DOM databases with KDBX4 format (Issue #13)
Read, write, and save KDBX4 databases with Argon2d or Argon2id as the KDF
Java 11 compatibility and updated dependencies (Issue #30 and Issue #26)
Introduces methods to save KDBX databases with user-defined headers (Issue #36)

Notes

Doesn't solve Issue #28; Entry fields (i.e. passwords, title, url, etc.) are still stored and returned as Strings.
Breaks the simple-xml representation pretty much entirely.
Custom icons, custom data, and other aspects of KDBX4 files beyond creating and saving new Groups/Entries have not yet been implemented.
Should still be compatible with Android even with bouncycastle (though I did not personally test this); KeePassDX seems to use it, so it is possible
Databases are saved as KDBX4 by default

If necessary, I can rollback changes so KDBX3.1 is still the default save format.

Hi
Thanks for this. It will take me a bit of time to review, but a few things:
a) DOM database support is robust but very slow, so only supporting DOM is not really an objective
b) looks like some simplification could be achieved in HmacBlockOutputStream (and looks like there is a bug, as commented)
c) Could really do with some tests
I will make the time to review, high time that version 4 read/write was supported, probably wont't accept in exactly this form, but thank you for all this. I will be back.
Jo

@jorabin Thanks for the feedback, always appreciated! I'll try to fix the issues with simple-xml and actually write some JUnit tests (sorry about that!) in the coming months. On a side note, do you know of any way to make simple-xml work with things like custom icons? It would be great if it could work in any scenario, but if custom icons are enough pose problems, I don't think it would be worth the risk to try and use it on an actual database.

I know you've closed this issue, but I wanted to give a heads up that I finally pushed 2.2-SNAPSHOT with support for V4. Will address some of the other things "soon".


Could running pylint on the tests have caught the issue where two test classes had the same name?

@carlini : thoughts?


Final Version

Overall nice work, let me know if you want to discuss how to interpret model coefficients in those multiple linear models!


ENH trusting scipy.ufuncs

Partially closes #224

Q1: Is it sufficient to only trust ufuncs under scipy.special ? As for the current scipy version, public ufuncs are only visible in scipy.special. Nevertheless, for future scipy versions (and also numpy), we can either recursively traverse scipy looking for public ufuncs or limit our search to the first submodules level. E.g.:

# pseudo-code: recursively check all submodules. Warning: this needs proper handling to avoid RecursionError
for submodule in get_submodules(scipy, max_level=-1):
    look_for_type(submodule, np.func)

# pseudo-code: first submodule level
for submodule in get_submodules(scipy, max_level=1):
    look_for_type(submodule, np.func)

Q2: Does test_can_trust_ufuncs() make sense in addition to extending test_can_persist_fitted() ?
Q3: Why wouldn't we include  current public numpy ufuncs the same way we do for scipy, even when numpy 2.0 not there yet ?

@BenjaminBossan kindly pinging you 👆🏻


proposal: os: add Number method to Signal interface

Signals have portable numbers identifying them on various operating systems (Plan9 excluded). But it looks like there is no direct way to retrieve these numbers from the wrapped os.Signal other than a String method which lazily looks up the name of that signal and returns it or using reflection package or type assertion. That's why I'm proposing to seal a Number(): int method to os.Signal interface and adapt current implementations to it. It will be supposed to return the original receiver provided it's an integer (or a numeric type that can be converted to integer) otherwise returning -1.
cf.
repo:^github.com/golang/go$ file:^src/syscall/ type Signal|Note
repo:^github.com/golang/go$ file:^src/syscall/ SIGINT count:1000

I'm not sure what the point is. In the definitions for the signals on Windows in golang.org/x/sys/windows:
const (
    // More invented values for signals
    SIGHUP  = Signal(0x1)
    SIGINT  = Signal(0x2)
    SIGQUIT = Signal(0x3)
    SIGILL  = Signal(0x4)
    SIGTRAP = Signal(0x5)
    SIGABRT = Signal(0x6)
    SIGBUS  = Signal(0x7)
    SIGFPE  = Signal(0x8)
    SIGKILL = Signal(0x9)
    SIGSEGV = Signal(0xb)
    SIGPIPE = Signal(0xd)
    SIGALRM = Signal(0xe)
    SIGTERM = Signal(0xf)
)

In other words, these values are completely arbitrary. I don't think relying on them for something is a good idea. If you're going to have to treat signals differently on different systems anyways, then you may as well just check them against different values. For example:
// signal.go
c := make(chan os.Signal)
signal.Notify(c)
handleSignal(<-c)

// signal_unix.go
func handleSignal(sig os.Signal) {
  switch sig {
  case os.Interrupt:
    println("UNIX interrupt.")
  case syscall.SIGHUP:
    println("Hup.")
  }
}

// signal_windows.go
func handleSignal(sig os.Signal) {
  switch os.Interrupt:
    println("Windows interrupt.")
  }
}

If you need to deal with signal numbers, you must be running on a Unix systems.  And in that case you can write sig.(syscall.Signal) to get a number.

Sorry, we can't expand os.Signal, as that would break the Go 1 compatibility promise. It doesn't have any unexported methods, so it's frozen: https://golang.org/pkg/os/#Signal
(contrast to, say, testing.TB: https://golang.org/pkg/testing/#TB)


how to make zuul-node HA?

when I  encapsulate several zuul-nodes  as edges-serivce, How to discover these nodes? Eureka? or ELB?

I'd say it depends on where you deploy (your platform) and what is in front of zuul.

OK! I got it


Bad EC GO:0103116 ATPase-coupled alpha-D-galactofuranose transporter activity

Hello,
GO:0103116     ATPase-coupled alpha-D-galactofuranose transporter activity
has no annotations, and a reference to a partial EC that is now deleted/replaced.
@hdrabkin Can you check what this corresponds to?
Thanks, Pascale

Ok I will first delete the partial if uses as an xref. Partials are for grouping terms only
We can leave GOC:pz for now as the def ref.
There is really no proper reference at Metacyc for it.
I will request a RHEA

Leaving this open until I hear from RHEA; partial EC removed

RHEA:61716 now public
EC:<IP_ADDRESS>
Added to GO:0103116


AMBARI-24833. HDFS client kerberos support + small fixes

What changes were proposed in this pull request?

add kerberos support for hdfs client
remove external hdfs client -> merge it with hdfs client
small fixes

How was this patch tested?
FT: manually - docker/vagrant/gce env

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/57/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/58/
Test PASSed.


Create Cloud Foundry and Invite Team Member

As a developer
I need to be able to invite team members to the cloud
So that able to upload code to the cloud
Assumptions:

FYI: 00-Invite-to-IBMCloud.pdf

Acceptance Criteria:
Given IBM Cloud
Then the status of all members changed to ACTIVE

Given that team member was invited
Then they are able to upload service to the could without errors.

Hey, I could see that all of the groupmates being assigned to the dev-ops group. However, I can't seem to find an organization? I'm referring to the image below:

It seems like, in the professor's slides, that we would have to create an organization with manager/developer settings? Let me know if this makes sense and if I'm missing something.

@jtsen  thank you for checking!

I think we can't add organization when we use this free account. So that, I thought all of us use my account (org is<EMAIL_ADDRESS>we can change the name. but I think the name of the organization is anything ok. I'm not sure about my idea though...


Implemented Default to 'Recommended For You' Experiment

What
Implemented a/b experiment to show recommended projects in Discovery.
How
In the DiscoveryViewModel I added a function called initialParam() which presents projects recommended to the user if the user is in the experimental bucket based on the configuration.
To Do

[ ]  Check snapshot tests 😕

@nino g2g?


Added Asm to Have Lightning Strike Effect

Just Visual, no Ui yet a Test with Upgrading Sword and seeing how it works would be nice. Will deal with Ui later lmao
DO NOT MERGE - no UI
Tested Working on Cubes
Tested Working on Crests

Works and looks great. Just finished a seed and worked fine with Gorko, end of dungeon crests, GoT and end game. Just needs a ui option and it should be good (probably worth waiting until Starry Skies is merged first since ui conflicts suck).


libertyRun task does not fail correctly

Running the libertyRun task prints this output:
libertyRun
This task can't be executed because some dependencies are missing

A quick look at the plugin source code reveals that the task catches the exception and does not log it to the output so I have no idea what is causing this error. See this catch block:
https://github.com/WASdev/ci.gradle/blob/master/src/main/groovy/net/wasdev/wlp/gradle/plugins/Liberty.groovy#L55
This should catch statement should fail the build and print the stack trace.

PR (here)[https://github.com/WASdev/ci.gradle/pull/47]


Integration test failing with error : Unexpected exception in CPS VM thread

Just by adding this dependency {"com.google.cloud", "google-cloud-storage", "1.105.0"} in my gradle project , one of the integration tests which looks something like this :
---------------------------------------------------------------------
void "buildInit library that uses declarative pipeline libraries"() {
final CpsFlowDefinition flow = new CpsFlowDefinition('''
def envDef = [:]
executePipeline(envDef) {
stage('Init') {
//init
}
}
'''.stripIndent(), true)
final WorkflowJob workflowJob = rule.createProject(WorkflowJob, 'project')
workflowJob.definition = flow
final WorkflowRun run = rule.buildAndAssertSuccess(workflowJob)
rule.assertLogContains('[WARN]:[executePipeline]: some msg', run)
}
---------------------------------------------------------------------
is failing with the following error :
[Pipeline] End of Pipeline
java.lang.IllegalStateException: Outcome is already set
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.setOutcome(CpsBodyExecution.java:332)
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.access$900(CpsBodyExecution.java:65)
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:358)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.throwException(ContinuationGroup.java:157)
at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:49)
at com.cloudbees.groovy.cps.Next.step(Next.java:83)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:347)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:93)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:259)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:247)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
hudson.UDPBroadcastThread#run: Cannot listen to UDP port 33,848, skipping: java.net.SocketException: Can't assign requested address
0.827 [id=58]	WARNING	o.j.p.w.cps.CpsVmExecutorService#reportProblem: Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[project/1:project #1]]
java.lang.IllegalStateException: Outcome is already set
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.setOutcome(CpsBodyExecution.java:332)
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.access$900(CpsBodyExecution.java:65)
P.S. By running the command -> ./gradlew clean build in my local machine, I am able to reproduce this issue.

This is an old issue, and hard to say without a full reproducer repository. It is possible that the transitive dependencies from the dependency you added may screw up the Jenkins runtime.


Double Confirm

Maybe semantic-ui could provide similar behaviour to buttons like this plugin: https://github.com/stefanocudini/bootstrap-confirm-button
This could be very useful UX module for use with administration panels or applications with functionality similar to "iOS App Store' installation of apps, allowing for confirmation without 'dummy modals' system.

I don't think this will be roadmapped. The solve is very particular.


Creat README.zh.md.

There are a lot of Chinese users of the software, and I would like to attract more Chinese users by adding Chinese descriptions.

Sorry, but I have no interest on maintaining 2 different READMEs.


Focus delay when using custom component as inline grid editor

We have a client app in which there are a number of editable cells that users want to quickly add values to and then tab through to the next cell.
To facilitate, we have wrapped a variety of HoistInputs in React Component classes to be registered with ag-grid as specified in their docs. However, we found the need to "createObservableRef" on the HoistInput, react to that, and then query the DOM for the underlying input in order to "manually" place the focus on the input, otherwise the input will not get the focus at all.
This seems to have created a noticeable and annoying delay between the time the user presses TAB and the input receiving the focus to start accepting new input. Effectively the first one or two keystrokes get "swallowed", forcing the user to constantly correct the content and deliberately slow down to a borderline unacceptable pace.
This problem seems to go away when using ag-grid's built in inputs, but then we lose a bunch of desirable behavior from our inputs.

@haynesjm42 and @febbraiod can you please review and close if we've addressed these concerns in the latest inline editing work?

Fortunately, I can't reproduce this using our new v41 editing.  Closing.
We can always reopen if needed.


Optionally allow trailing data in bufread::XzDecoder

Some xz streams have unrelated data afterward.  In particular, Linux kernel initrd files are the concatenation of multiple cpio archives, each of which can be compressed with a different compressor.  read::XzDecoder and bufread::XzDecoder return InvalidData in this case, which makes it difficult to detect the EOF, unwrap the underlying stream, and continue reading with a different decompressor.  (write::XzDecoder returns Ok(0) after the end of the xz stream, which is less ambiguous.)  Multi-decoder mode doesn't address this, since that only handles the case where the following data is also an xz stream.
liblzma properly returns StreamEnd here; we just need to detect it. However, the xz test suite contains some tests with trailing garbage, and the xz command-line tool is designed to fail on those unless --single-stream is specified.  For compatibility, we probably can't allow trailing garbage by default, but we can provide an option.  Add an allow_trailing_data() toggle to bufread::XzDecoder, and stop accepting bytes in read() if we reach StreamEnd with that toggle enabled.
Do not add a similar option to read::XzDecoder, since it's only useful if the underlying stream is synced to the end of the xz stream afterward, and read::XzDecoder can't ensure that.
Also add an additional test verifying that write::XzDecoder refuses to accept additional bytes after the xz stream reaches StreamEnd.

Thanks for the PR! Unfortunately I don't really have the time to maintain this crate nowadays, though. If you're interested I could transfer ownership to you, however.

Hmm.  In the coreos/ GH organization we do maintain some crates.  So one option is to transfer it there.
Bigger picture I think we should be moving away from xz to zstd though.


Custom Graphs over time throws exception

When I expand "Custom Graphs"  and select the item in there, I get this:
{"$id":"1","innerException":null,"message":"The extension 'LakshayKaushik.PublishHTMLReports' doesn't contain the requested asset type 'CustomsGraphs.html' in version '1.1.43'.","typeName":"Microsoft.VisualStudio.Services.Gallery.WebApi.ExtensionAssetNotFoundException, Microsoft.VisualStudio.Services.Gallery.WebApi","typeKey":"ExtensionAssetNotFoundException","errorCode":0,"eventId":3000}
I'm on ADO server 2019, and currently using Edge

I have fixed this now, do you have some custom graphs to test this ? Let me know if it still fails.

I don't have any custom graphs, but I think I can probably still test your fix and confirm I don't receive the exception?  Will be next week sometime - I don't have permission to update the extension.

Yes, you wont get exception now. Closing this. Re-Open if you still see the exception.


PIL.Image.LINEAR no longer exists

You are using pillow==9.5.0, but despite installing all the libraries required, when executing my code I get:
File /opt/conda/lib/python3.10/site-packages/fdlite/transform.py:66, in image_to_tensor(image, roi, output_size, keep_aspect_ratio, output_range, flip_horizontal)
     63 dst_points = [(0., 0.), (width, 0.), (width, height), (0., height)]
     64 coeffs = _perspective_transform_coeff(src_points, dst_points)
     65 roi_image = img.transform(size=(width, height), method=Image.PERSPECTIVE,
---> 66                           data=coeffs, resample=Image.LINEAR)
     67 # free some memory - we don't need the temporary image anymore
     68 if img != image:

AttributeError: module 'PIL.Image' has no attribute 'LINEAR'

My code is really simple:
from fdlite import FaceDetection, FaceDetectionModel
from fdlite.render import Colors, detections_to_render_data, render_to_image
from PIL import Image

image = Image.open('ff2fc5a0-22c8-4420-8e0b-1f24ea241fa4.png')
detect_faces = FaceDetection(model_type=FaceDetectionModel.BACK_CAMERA)
faces = detect_faces(image)
if not len(faces):
    print('no faces detected :(')
else:
    render_data = detections_to_render_data(faces, bounds_color=Colors.GREEN)
    render_to_image(render_data, image).show()

I've installed your library thanks to pip, I'm running the code on a VertexAI Jupyter Notebook.
I can't use your library, can you help me?

Seems like I would need to update the dependencies to Pillow 10.3.0.

@Cioffy The latest version is available via pip and works with pillow 10.3.0.


Change outdated and/or deprecated data binding defaults for String, Instant and Duration

Change outdated and/or deprecated data binding defaults, while supporting older defaults for backwards compatibility. 1-2 months after initial commit

String <-> UTF8 (because a YDB STRING is actually a byte array)
Instant <-> TIMESTAMP, Duration <-> INTERVAL.
Mapping Instant <-> [U]INT64 should use MILLISECONDS qualifier by default, for maximum backwards compatibility (YOJ initially supported only milliseconds precision when storing Instants)

– For String we have YqlPrimitiveType.changeStringDefaultTypeToUtf8() as a temporary measure. Will add the YqlPrimitiveType.useLegacyMappingForString(); method and ask all legacy-users to call it. After everyone migrates to explicit kverride call, we can change the default mapping to UTF8.

For Instant, we'll add a similar pair of functions to set the default, and gradually migrate, eventually setting TIMESTAMP as the default type. Should support microsecond precision, because that's what both Java 9+ and YDB support (https://ydb.tech/docs/en/yql/reference/types/primitive#datetime).
For Duration, we can set default to INTERVAL right now, because previously there was NO default, and everyone has explicitly annotated their Duration fields, or used e.g. a two-field (seconds, nanos) composite value. Must ensure we support microsecond precision, because that's what both Java 9+ and YDB use (https://ydb.tech/docs/en/yql/reference/types/primitive#datetime).

@lavrukov @akorsukov What's the position of Cloud Java on this? Will you be able to explicitly set legacy mapping defaults for your services in a YC-specific module, so that YOJ can use more sensible type mapping for Strings, Instants and Durations?

Added opt-in support for New Mapping in YOJ 2.1.0.
yoj-repository-ydb-v2 users are encouraged to call
YqlPrimitiveType.useLegacyMappingFor(STRING, ENUM, TIMESTAMP);

in legacy projects to keep the old mapping, and
YqlPrimitiveType.useRecommendedMappingFor(STRING, ENUM, TIMESTAMP);

in new projects to get the new mapping.

⚠ YOJ 2.2.x will use legacy YDB<-> Java type mapping, but **THE DEFAULT WILL CHANGE IN YOJ 3.0.
What should you do?

To continue using the legacy mapping safely, call

YqlPrimitiveType.useLegacyMappingFor(STRING, ENUM, TIMESTAMP);

before initializing YOJ, e.g., in a lifecycle method.

In new projects, we recommend to the new mapping (which will become DEFAULT in YOJ 3.x). To do so, call:

YqlPrimitiveType.useLegacyMappingFor(STRING, ENUM, TIMESTAMP);

before initializing YOJ, e.g., in a lifecycle method.

👍 Using the NEW MAPPING is HIGHLY RECOMMENDED for new projects, when you have no existing table schema and/or data to migrate.
If you decide to use the new mapping in an OLD project, remember to annotate existing entities' columns with the column type used in the database:

@Column(dbType=DbType.STRING) to retain the legacy mapping java.lang.String, java.lang.Enum<->YDB STRING (=byte array)
@Column(dbType=DbType.INT64, qualifier=DbQualifier.MILLISECONDS) to retain the legacy mapping java.time.Instant<->YDB INT64 (millisecond accuracy).

See also: #71 for more mapping improvements.


Review the new curve depeg models

initial review of curve depeg models
added examples

credmark-dev run contrib.nish-curve-get-pegging-ratio --input '{"address": "0xfd5db7463a3ab53fd211b4af195c5bccc1a03890"}' -b 14234904 --format_json
credmark-dev run contrib.nish-curve-get-pegging-ratio-historical --input '{"pool": {"address": "0xfd5db7463a3ab53fd211b4af195c5bccc1a03890"}, "date_range": ["2022-01-10","2022-01-15"]}' -b 14234904 --format_json
credmark-dev run contrib.nish-curve-get-depegging-amount --input '{"pool": {"address": "0xfd5db7463a3ab53fd211b4af195c5bccc1a03890"},"token": {"address": "0xd71ecff9342a5ced620049e616c5035f1db98620"}, "desired_ratio": 0.98485645}' -b 14234904 --format_json

Still run.sh merge conflicts. It seems to me that we should break that up, since it's having problems with all changes? how do we prevent this better. @leafyoung


Question about the sample code

In example 1, the JS part is as follows:
Meteor.publish('publication', function() {
  Counts.publish(this, 'name-of-counter', Posts.find());
  return Posts.find();
});

whereas the CoffeeScript states:
Meteor.publish 'publication', ->
  Counts.publish this, 'name-of-counter', Posts.find()
  return undefined    # otherwise coffeescript returns a Counts.publish
                      # handle when Meteor expects a Mongo.Cursor object.

I assume that both samples should return an undefined value, to illustrate publishing "just" a counter?
I deducted this from the sample located under the explanation of noReady, where I learned that I have to provide the noReady flag if I also want to return a Cursor, not just a Counter. Or did I get that wrong, and the code in example 1 is correct, i.e. the noReady isn't needed in this case? If so, I would like to understand why.

You are right.  I accepted portions of PR #72 to improve the docs, and inadvertently missed that return Posts.find(); in my reversion commit.  I'll get that removed.  Thanks!

Just to clarify, here's what the examples are supposed to be.
JavaScript
Meteor.publish('publication', function() {
  Counts.publish(this, 'name-of-counter', Posts.find());
});

Coffeescript
Meteor.publish 'publication', ->
  Counts.publish this, 'name-of-counter', Posts.find()
  return undefined    # otherwise coffeescript returns a Counts.publish
                      # handle when Meteor expects a Mongo.Cursor object.

Fine, thanks. So I infer that I have to add the noReady flag if I want to return another cursor as well, right? I'm asking because I did not do this so far.

@derwaldgeist that's right

Ok, thanks for this additional info!


Fix PG10 beta2 break on predicate_refuted_by function call

PG10 Beta2 adds clause_is_check parameter to predicate_refuted_by function.

Looks good. Merging.

Cool!
On Mon, Jul 17, 2017 at 7:14 PM, Hadi Moshayedi<EMAIL_ADDRESS>wrote:

Merged #152 https://github.com/citusdata/cstore_fdw/pull/152.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/citusdata/cstore_fdw/pull/152#event-1167540833, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABNCFs9qH1CP5BUJG742uxrkLRW78aZHks5sPBTsgaJpZM4Oaptd
.


missing leader node info in diagnostics restful api

Describe the bug A clear and concise description of what the bug is.

To Reproduce Information to reproduce the behavior, including:

Git commit id https://github.com/openthread/ot-br-posix/commit/3a98779dc9f0875af9c7b137e764c9663bfdc9c3
IEEE 802.15.4 hardware platform
Build steps
Network topology

Expected behavior A clear and concise description of what you expected to happen.
Console/log output If applicable, add console/log output to help explain your problem.
Additional context Add any other context about the problem here.

There are 16 router devices and 65 child devices in the Thread network.

Hi @jwhui
Is it related to the number of TlvTypes? More TlvTypes take more time to collect?

thanks for raising this discussion.
For further tracing down your issue, I propose comparing wireshark captures. Typically, collect timeout of two seconds is sufficient for multicast responses from routers. However I suspect you may occasionally see packet collissions, in particular related to spacially dispersed Thread routers. Currently, OT lacks randomly delayed answers for multicast management queries. This is addressed in SPEC-1061

Closing stale issue.


Added another test: Nested style objects

I added another test to check another common real-world case: pseudo classes and media queries. If that fits fine, feel free to merge.

Hey @rofrischmann, looks good, but can you merge master on this branch?

ofc, gimme a sec :P

Should be up-to-date now :P

LGTM 👍


Build landing page

This is our real project
in this project i add
HTML
CSS
Linters
and README.MD

@royajamal

Your pull request does not have a description
Your README.md is also not professional and does not have the information about your project.

Solve these issues and mention me back here using my username @ahzamir so I can re-review your project

@ahzamir  Thank form your feedbacks just some requirement was missing so now it's done please check it .

@ahzamir  Thanks from your feedback just some requirement was missing so now it's done please check it.

@royajamal

Still, your code is missing some of the requirements.
And also check the comments below and solve them.

@ahzamir  Thanks from your feedback just some requirement was missing so now it's done please check it.

@royajamal
your css and html codes got no problem, i think. but in readme.md remove the description, and in installation section, you should remove the link, and add the applications that people should install, so they can use your website.

@royajamal
In my point of view, you did a great a good job, you done all the necessary things for project.

@ahzamir  teacher  all things done  please check it

@ahzamir  teacher i clean my code please check it.

@ahzamir  Teacher i clean my code please check it.

@royajamal

Please implement the comments and feedback I gave to your portfolio project as this project has the same issues.

@ahzamir  Thanks from your  feedback  now all things done please check it .

@ahzamir Thanks form your feedback  i added chenges in README.md file please check it .

@ahzamir  Thanks form your feedback your insturction is done please check it .


Not compatible with the latest version of Rollup (v1.0.0)

The<EMAIL_ADDRESS>had been released yesterday, when I upgrade to the latest version, I got the following error:
TypeError: Cannot read property 'forEach' of undefined
at Watch.capture (~\node_modules\karma-rollup-preprocessor\lib\index.js:65:20)
at rollup.then.bundle (~\node_modules\karma-rollup-preprocessor\lib\index.js:21:23)

It seems that the bundle.modules had been moved to bundle.cache.modules.

Thanks @fengyuanchen, I'm on it.


Post a comparison of this library with boost::program_options

The standard C++ library doesn't include any option parsing functionality, but Boost does: boost::program_options.
Could you possibly post an overview of the differences in functionality (and perhaps dependencies and implementation approach) between this library and the Boost one?

I think I can write that down somewhere.

Just wondering if this exists yet? No problem if it doesn't, but I am curious as to the main differences...

I concur. Seeing the difference would be helpful. At the feature level certainly, but also the compile time and binary size differences for a few compilers.


Download files directly to allow larger file transfers using StreamSaver.js

https://github.com/jimmywarting/StreamSaver.js allows streaming file downloads from JavaScript. It also has a polyfill for browsers that don't provide WritableStream.

Ideally, this could be combined with sending separate files without zipping


UI nit: splash login button a bit small (or redundant?)

Not sure if it's just for my computer, but I think the top-right login button seems either redundant, and too small if it's not. Is there any reason why we have two login buttons?

The middle button becomes a "Go to the Student Dashboard" button while the top right button is for logging in and logging out.

This is there to support the default interaction of having a login button on the top-right. As @Some3141 mentioned - this becomes a logout button.


WIP: Add config option to disable "Update branch by rebase"

Fixes #18710

How can I make AllowRebaseUpdate=true the default for existing repositories?

Maybe DisableXxx? 😂

Yes that would work 😆.
But I would like to avoid it for consistency with the other PullRequestsConfig options that are also named AllowXxx.

How can I make AllowRebaseUpdate=true the default for existing repositories?

It's not easy.

https://stackoverflow.com/questions/30445479/how-to-specify-default-values-when-parsing-json-in-go
It seems that the default value can be set during json.Unmarshal


fix cell indices for submeshes with their own hosting pointcloud

If you consider a mesh like this
from sigmaepsilon.mesh import LineData, PointData, PolyData
from sigmaepsilon.mesh.cells import L2
from sigmaepsilon.mesh.utils.space import frames_of_lines
import numpy as np

coordsA = np.array([[0, 0, 0], [1, 0, 0], [1, 1, 0], [0, 1, 0], [0, 0, 0]], dtype=float)
topologyA = np.array([[0, 1], [1, 2], [2, 3], [3, 0]], dtype=int)
framesA = frames_of_lines(coordsA, topologyA)

coordsB = np.copy(coordsA)
coordsB[:, 2] = 1
topologyB = topologyA + len(coordsA)
framesB = frames_of_lines(coordsB, topologyB)

pdA = PointData(coordsA)
cdA = L2(topo=topologyA, frames=framesA)
pdB = PointData(coordsB)
cdB = L2(topo=topologyB, frames=framesB)

mesh = PolyData(A=LineData(pdA, cdA), B=LineData(pdB, cdB))

Both meshes 'A' and 'B' will have cell indices from 0 to 3. This should be fixed such that cell indices are unique.

This only occurs if the mesh is created this way. If the mesh is created like
mesh = PolyData()
mesh["A"] = LineData(pdA, cdA)
mesh["B"] = LineData(pdB, cdB)

behaviour is ok. The problem is that the __join_parent__ method is not triggered the other way.


add basic openflow constants

Signed-off-by: Vasiliy Tolstov<EMAIL_ADDRESS>

Firstly as openflow have different versions a think to add openflow main layers that parse only minimal header with version info, after that next layer type determine by openflow header revision and inner message type. Does this right?

Also for openflow we need to goes in tcp to next layer (that openflow) not go to LayerTypePayload

Apologies for delay, just returned from honeymoon.

Dear Vasiliy
Would you consider fixing the issues raised by Graeme ?
Laurent

@lhausermann yes, i'm try to fix it today.

@gconnell can you helps me? Does it possible in gopacket create layer, that check 1 byte in packet and set next layer based on this value, but layer that does this check does not displayed anywhere (via Layers() function )
For example i'm try to decode some packet that have Ethernet, IPv4, TCP, Openflow14.
I want to write code that after TCP, check payload byte and determine openflow version and via nextLayer says that this is Openflow14 packet.

@gconnell what do you think about this decoding?
TCP->OPENFLOW->OPENFLOWXX
Also what do you think about decoding message payload inside openflow packet ?

Take a look at how this is done with MPLS at
https://github.com/google/gopacket/blob/master/layers/mpls.go, lines
27-53.  In short, you map the OpenFlow protocol to a decoder function that
checks bytes and defers to version-specific decode code.
On Wed, Jan 13, 2016 at 9:13 AM, Vasiliy Tolstov<EMAIL_ADDRESS>wrote:

@gconnell https://github.com/gconnell what do you think about this
decoding?
TCP->OPENFLOW->OPENFLOWXX
Also what do you think about decoding message payload inside openflow
packet ?
—
Reply to this email directly or view it on GitHub
https://github.com/google/gopacket/pull/93#issuecomment-171345966.

@gconnell you mean something like in my last commit?
also does this output looks right?
       base_test.go:25: Checking packet layers, want [Openflow Openflow14]
        base_test.go:28:   Got layer Openflow, 8 bytes, payload of 16 bytes
        base_test.go:28:   Got layer Openflow14, 16 bytes, payload of 0 bytes
        base_test.go:30: PACKET: 16 bytes
                - Layer 1 (08 bytes) = Openflow {Contents=[..8..] Payload=[..16..] Version=5 Type=0 Length=16 Xid=950}
                - Layer 2 (16 bytes) = Openflow14       {Contents=[..16..] Payload=[] Version=5 Type=0 Length=16 Xid=950 Message=[]}

        openflow_test.go:40: &layers.Openflow14{BaseLayer:layers.BaseLayer{Contents:[]uint8{0x5, 0x0, 0x0, 0x10, 0x0, 0x0, 0x3, 0xb6, 0x0, 0x1, 0x0, 0x8, 0x0, 0x0, 0x0, 0x20}, Payload:[]uint8(nil)}, Version:0x5, Type:0x0, Length:0x10, Xid:0x3b6, Message:layers.OFP14MessageHello{Elements:[]uint8(nil)}}

Can we fix the merge issues ?

pong @vtolstov : can you rebase it to master?

Sorry for delay, i'm try to add some more message types and rebase.

ping @vtolstov anything do to do the rebase ?

Original repository disappeared, so I think this won't happen.


microbenchmarks_ios timing out ~40% of the time, white screen

https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/godofredoc_google.com/15e28fdf5416728310250fe80d868d178b795977279a5341418a44dcbd936cb4/+/annotations
The runner is not progressing from:
[microbenchmarks_ios] [STDOUT] [  +58 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:53924/
[microbenchmarks_ios] [STDOUT] [  +14 ms] Application running.
[microbenchmarks_ios] [STDOUT] [   +5 ms] Connected to iPhone
[microbenchmarks_ios] [STDOUT] [   +2 ms] Flutter run key commands.
[microbenchmarks_ios] [STDOUT] [   +1 ms] h Repeat this help message.
[microbenchmarks_ios] [STDOUT] [        ] c Clear the screen
[microbenchmarks_ios] [STDOUT] [        ] q Quit (terminate the application on the device).
[microbenchmarks_ios] [STDOUT] [        ] An Observatory debugger and profiler on iPhone is available at: http://<IP_ADDRESS>:53927/7vUpRFk2E18=/

Split off from https://github.com/flutter/flutter/issues/75851, which will track the task never being killed.

I tried to reproduce this locally and couldn't.

Seems to happenning very frequently ~40%. Are there any logs that we can collect to help triage?
https://ci.chromium.org/p/flutter/builders/prod/Mac_ios microbenchmarks_ios

A screenshot from the device while it is hanging would be helpful.
I wish we could automatically collect that before the task times out.

Moving this one as P1 as it is the main contributor to Flutter tree closures.

I tried this again and I can't get it to fail locally.  Will probably need to ssh into a machine again.

Replicated the issue using led. The application starts opening but it gets up to the white screen and then it hangs there.

@godofredoc Are there particular machines it always fails on?

@godofredoc Are there particular machines it always fails on?

Never mind I just looked myself, it seems to reproduce all over the place.

I'm trying to reproduce again while collecting idevicesyslog I hope it contains some some hints about the problem.

I reproduced it! The screen was white, but I touched the screen and that kicked something and it loaded the UI.  I actually have a trace of it while it's stuck
dart_devtools_2021_3_3-1614827796628000.json.txt

I'm trying to reproduce again while collecting idevicesyslog I hope it contains some some hints about the problem.

@godofredoc Unfortunately idevicesyslog doesn't work on iOS 13 and above.  We would be getting logs from the debugger if the app was logging anything, since it's attached.
[microbenchmarks_ios] [STDOUT] [  +48 ms] (lldb)     run
[microbenchmarks_ios] [STDOUT] [ +170 ms] success

I got some logs with the latest idevicesyslog version installed with brew. Could it be that we need to upgrade flutter idevicesyslog to the latest version?
Attached the log
microbenchmarks_log.txt

Oh nice! I don't even see the code change where they started supporting that lockdown service.

@jmagman From the trace attached, No frames were scheduled. Could it be one one of those benchmarks that starts paused and then starts its workload after a service protocol request? Not sure why things got kicked off when you touched the screen however. Can you attach a trace when the UI starts rendering?

@jmagman can you please share the command you are using to collect the traces?

I went to the observatory service URL ("An Observatory debugger and profiler on <> is available at: http://<IP_ADDRESS>:60931/91n_cdDMTRI=/") , then timeline

"Save" button to save the current results, or "Refresh" to get the results since the last run.
I'm not sure what "Recorded Streams" @chinmaygarde or @zanderso would find helpful.

Per @jason-simmons, this is not occurring at 40%. The trace in a previous comment shows that the engine didn't get any request to render a frame. Since there isn't any actionable information to make progress on this issue, @zanderso is going to find an owner to track this down. Given the rate of occurrence, I am lowering the priority of this issue.

I saw another recipe timeout but in Mac_android this time: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android home_scroll_perf__timeline_summary/529/overview (issue filed here). Not sure if it's the same cause or not. It passed after re-running.


Reduce Detections

Hey, I got an idea to reduce detections.
You shall make the output as obfuscated batch file.
Inside the batch file, put a script that will download a exe file and execute it.
So it will reduce detections for the exe file.

I had this idea but there is a problem with that. As soon as the exe file is saved on disk, the antivirus will raise alarms.

I would rather add an open to recompile Pyinstaller bootloader on buildtime if it reduces detections.

For now, it is unavoidable. The GUI binary of Pyinstaller is getting flagged. But I'll continue working on this issue.


Adds building documentation section to ReadMe and improves generation of docs

Changes
Fixes #76
Also bug fixes #86
Provides section in ReadMe about autodocs/Sphinx and commands for generating documentation site
Adds directive for serializers module in sphinx index
Adds more options to sphinx config to ensure documentation for special members of modules is generated
Mocks import from ASnake
Adds wraps decorator to real_decorator to generate documentation for docstrings wrapped in that decorator
Questions
Is the Building Documentation section in an okay spot in the ReadMe?

@daremiyo personally, I'd move the Documentation section up above the contributing section. I think it's more likely someone coming to the project for the first time will want to build and look at docs as opposed to figuring out how to contribute.
Two other thoughts:

Should we remove the leading dot from the docs directory? That dot makes it a hidden directory, which means, depending on your OS, you'll have to take some extra steps in order to actually see it.
Let's add a .gitignore file to the docs directory (regardless of the above) and ignore the _build directory. That way we don't mistakenly commit the built docs.


Question about [CLOSED] issue prefix

Hi! I've a question about the handling of closed issues.
The README states:

If you want to import all issues including the closed ones, use --all instead of --open. Closed issues will be automatically closed in the target repository, but titles will begin with [ISSUE][CLOSED] and [PR][CLOSE].

So if I understand this correctly, closed issue in the source repository will end up as closed issues in the target repository. So I wonder why the code still adds [CLOSED] to the issue title in this case. The source code mentions this as a "temporary fix":
https://github.com/leemgs/github-issues-import-ng/blob/fc1d0e864db5bdd26a594a7d722ad08fa9aa15b7/gh-issues-import-ng.py#L366-L371
Any idea?

Ah, ok. In my case we have to migrate a repository to a new organization and I want to preserve as much of the history as possible. But after the issue migration, we will archive the old repository. Therefore, I was just wondering if it is safe to remove the code that adds the prefix before running the migration.

Welcome to any issue and PR. :)


Frame docs

Design doc on dask.frame.
This also includes a tiny implementation that doesn't do anything surprising.  It's just there to provide something concrete.

This is in.


Observations & Enhancements

I really like this component and I think it's very well executed and I'd like to use on my project.  However I found some corner cases and issues that needs to be addressed in addition to the items listed in the TODO list.
Here are my observations thus far:

If you supply exactly two images, the images won't render and you will get the following error:
NaN is an invalid value for theheight css style property. Check the render method ImageStory
[Edit: actually I'm unable to replicate this so I'm doing more testing]

If you don't supply a callback for onImageSelect and you click on an image, you'll get the following  error: Uncaught TypeError: r is not a function

The component expects a prop of type number however this could be restrictive. You can't pass a string like width='100%' to make it responsive.
[Edit: it seems that it does take a string, the only issue is the react warning on props validation
`Warning: Failed prop type: Invalid prop `width` of type `string` supplied to `ImageStory`, expected `number``.]

If onImageSelect has been provided  and you hover on an image, then it will be nice to show a hand cursor
[Edit: I'm able to get the desired behaviour by using   rootStyle={{ cursor: 'pointer' }}]

I hope we can address those to make it fully polished :)

@aliogaili This is great, thanks!
I'll soon fix those issues.

@aliogaili All issues addressed in v0.1.0 except:

If you supply exactly two images, the images won't render and you will get the following error

Is it still bothering?

That's great @gauravchl much appreciated! I'll test and let you know soon what I observe.

Hello @gauravchl  would be you tackling this last issue? I'm using a local fork of the library because of this last one.

Hi @aliogaili, Sorry i almost missed it.
I've applied the fixes in v0.1.1 Please review the new updates.
Thanks.

Great! thank you so much @gauravchl, I'll give it a spin and let you know :)

@gauravchl the component is working perfectly now! great work buddy, thanks for responding to my issues.


Microsoft.Media 2019-05-01-preview folder contains 2018-07-01 API version

See https://github.com/Azure/azure-rest-api-specs/blob/6049cf3aaf88d57c587157f85d658a3782abe907/specification/mediaservices/resource-manager/Microsoft.Media/preview/2019-05-01-preview/Accounts.json#L9 for example
This is causing issues for schema autogeneration (see https://github.com/Azure/azure-resource-manager-schemas/pull/927#issuecomment-606484394)

This is one of the older preview releases where we have duplicate files, in the newer releases we are poitning those files from the correct location.
https://github.com/Azure/azure-rest-api-specs/tree/6049cf3aaf88d57c587157f85d658a3782abe907/specification/mediaservices/resource-manager/Microsoft.Media/preview/2019-09-01-preview
We have not touched it as its an older release? is this blocking you? need help from SDK team, what is the next steps, should we cleanup older releases, even though we will not have any new releases on that SDK?


[RFC] model collections

What do you think about model specific collections?
Those collections are pre-configured PropelObjectCollection for a given model.
They would follow the same principles as each model itself. A BaseUserCollection and a UserCollection would be created.
A respective ActiveQuery will always return an instance of this collection where applicable (not on count() etc.).
This would create a home for collection specific business logic.
An example use-case
A User may create a rated Review on a Product.
Now the ProductQuery would have a method getReviews which currently yields a PropelObjectCollection.
If you now want to calculate the average value of all attached reviews on the product, you would have to find a home for the new method. Let's say you created a Product::getAverageReviewRating which yields the average value of the rating of each review attached to the product.
This seems fine, but if you want to abstract such behavior, let's say the Product is related to a Manufacturer.
You could add a ReviewQuery::filterByManufacturer which yields another collection.
If both methods would yield a ReviewCollection and you would move the calculation of the average into ReviewCollection::getAverageRating, you can call this on any result set provided by any query done by the ReviewQuery.

Current state of model collections is some odd: you allowed to hydrate collections by checking of class existence, but generated phpdoc still old and don't contain name collections, which is very useless in IDE. Also, php7 will bring ability to use strict returned type definition, which will rise relevance of current feature (we can check config «use php7 features» flag in config and generate according code).
I suggest add boolean key «generator.named_collections» to configuration or attribute to database in schema. We can add this feature as disabled by default if you afraid to generate large amount of files, but user will have ability to decide which strategy to use. Cli key for command is some little bit worse for me, but much better than nothing :).

We will have to open a new discussion here for 2022+


Setup cookie compliance

Closes lonelyplanet/destinations-next#694.
Make alert more re-usable.
Turn on alert for cookie compliance in EU.
Change map-alert class for better specificity.

:+1:


Is there any solution to control multi-uavs with the GAAS

I want to know ,how can i control multi-uavs with the GAAS, i'm new to  python and mavros.

So what kind of multi-UAVs you mean? Or what do you want to do with multi-UAVs?

So what kind of multi-UAVs you mean? Or what do you want to do with multi-UAVs?

I mean control multi-UAVs to move toghter on the same time, like formation. I know the px4 Firmware launch has multi_uav_stil.launch，but i can't use the commander.py to control it directly. How do i change the py file.

GAAS didn't support control multi-UAVs yet, but we will support it in the future(>6 months maybe). You could leave your requirements here:)

closed as stale, reopen if needed.


Fix calculate_x

have you tested this repo ? I cannot see how it can work without this fix.

Mmh I meant hash_start, without final s, sorry for the typo


Introduce Storage trait for Coprocessor DAG

What have you changed? (mandatory)
tikv::coprocessor relies on tikv::storage. In order to extract Coprocessor (or even Coprocessor DAG) into a standalone crate / workspace, we need to interfaces we used in tikv::storage.
This PR introduces a Storage trait for the Coprocessor DAG in order to solve the problem. The Storage trait (coprocessor::dag::storage::Storage) is defined as follows:
pub trait Storage: Send {
    type Statistics;

    fn begin_scan(
        &mut self,
        is_backward_scan: bool,
        is_key_only: bool,
        range: IntervalRange,
    ) -> Result<(), Error>;

    fn scan_next(&mut self) -> Result<Option<(Vec<u8>, Vec<u8>)>, Error>;

    fn get(
        &mut self,
        is_key_only: bool,
        range: PointRange,
    ) -> Result<Option<(Vec<u8>, Vec<u8>)>, Error>;

    fn collect_statistics(&mut self, dest: &mut Self::Statistics);
}

The trait does not bound to current statistics implementation tikv::storage::Statistics by introducing Storage::Statistics associated type.
All Coprocessor DAG implementations are changed accordingly. Now they only rely on this Storage trait, instead of tikv::storage::xxx.
What are the type of the changes? (mandatory)

Engineering (engineering change which doesn't change any feature or fix any issue)

How has this PR been tested? (mandatory)
WIP

/run-integration-tests

/run-integration-tests


Nested handlers broken

I updated to 0.13 and nested route handlers seem to be broken. I have my routes defined and run:
"use strict";

var React         = require("react"),
    Router        = require("react-router"),
    Route         = Router.Route,
    App           = require("app"),

    Keywords     = require("components/keywords/list"),

    routerActions = require("flux/router").Actions;

var routes = (
    <Route name="App" path="/" handler={App}>

        <Route name="Keywords" path="keywords" handler={Keywords} />

    </Route>
);

Router.run(routes, Router.HistoryLocation, function (Handler, state) {
    routerActions.changeRoute(state);
    React.render(<Handler/>, document.body);
});

var App = React.createClass({

    contextTypes: {
        router: React.PropTypes.func.isRequired
    },

    mixins: [
        routerStore.mixin()
    ],

    getStateFromStores: function () {
        return {
            router: routerStore.state,
        };
    },

    render: function () {
        return (

                                <RouteHandler />

        );
    }
});

When I access the / the App handler is run as expected but when I access /keywords only handler for that route is being rendered without parents handlers. the same thing happens when tryiing to navigate using <Link /> component.

I figured out that this part breaks the proper rendering of nested routes handlers:
routerActions.changeRoute(state);

Looks like storing router state in flux store described here https://github.com/rackt/react-router/blob/master/docs/guides/flux.md is not compatible with React 0.13.

Can you elaborate on how it breaks?

Yes, when I enter url for subroute only the handler for that route is rendered in the document.body. None of the parent routes (App in the example) is rendered. The state stored in the flux store only represents that route and does not contain the parent routes neither.

Can you put up a reproducing repo?

The app quite big and can't share its code fully. I'll try to extract the small portion of working code tomorrow and share the repo.

I'm having the same issue with Link. <Link to="act" params={{actId: this.props.act.id}}>click me</Link> clicking this only changes the url, but never renders.

We've got examples and tests w/ these very straightforward flows that work fine. If you aren't placing a <RouteHandler/> in render, or you aren't calling the callback in a willTransitionTo you won't see your stuff. I've got no other guesses at the moment.
What does routerStore.mixin() do? and what does routerActions.changeRoute(state); do?

closing due to inactivity


Question: SignalR scaling with redis, monitoring

After some attempts i could run signalR app with redis.
But i have some questions about scaling.
SignalR use Pub/Sub redis mechanism, should i use sticky session on nginx side or redis enough?
If I understood correctly sticky-session is required for all transports except websockets.
Can i monitoring existing connections count, connections fails?

in RedisHubLifetimeManager.cs there is this comment:

if the connection is local we can skip sending the message through the bus since we require sticky connections.

is that an old comment or do we need sticky sessions if using redis even if only websockets are used?

Even with WebSockets, I'd strongly recommend using sticky sessions. However, you are correct, if you are configuring your client to explicitly allow only WebSockets (new signalR.HubConnection(url, { transport: signalR.TransportType.WebSockets })), then you aren't required to use sticky sessions because the WebSocket itself is already "sticky"

because the WebSocket itself is already "sticky"
thanks, that makes sense and it helped me to understand the whole thing.

May I ask another question regarding stickyness of Websockets?
If I strictly limit the server and the client to web sockets as you describe, can I in any case assume that even if my Azure Webrole scales up, the connections will still work without interruption?

I wouldn't assume that, but I don't know enough about the mechanics on how that stuff works to know if that's true.

thank you. As far as I understand it after reading Configure the distribution mode for Azure Load Balancer and Load balancing with sticky sessions (source IP distribution mode for load balancing) in Cloud Services I can use standard Hash-based distribution mode on the Azure load balancer and if the service scales I have to make sure on the client that it reconnects on error.

can I in any case assume that ... the connections will still work without interruption?

From my experience, you shouldn't ever assume your connections will work without interruption, no matter how they're configured :). It's definitely worth thinking seriously about how your application should behave when the client loses the connection to the server. The connection loss could be temporary, in which case a reconnect is the solution, or it could be a long-term loss of connectivity and you'll want to consider disabling UI and providing a mechanism for the user to retry later. You don't want your service going down, coming back up, and then going down immediately under a barrage of clients reconnecting ;)


POC for validator that works with GopherJS

This fixes one of the failing validation tests in GopherJS.  If we like this approach, I'll finish replacing github.com/go-ozzo/ozzo-validation with github.com/go-playground/validator/v10, and then we may be able to run this entire thing with GopherJS.

Also, the Ozzo library doesn't appear to be all that well maintained: https://github.com/go-ozzo/ozzo-validation another reason why I like something internal to gobl that covers the basics.


JoWilder: LastInteraction

A feature to show which interaction a player last had within the game session.
The sub-features are:
(base) - The last interaction a player encountered in the game (replaces max_level)
This should be configured as an aggregate feature.

 JoWilder: LastInteraction

a4dc17f87809640898c4c4c6d55d3633b81c591d

627dadf027704cfb74e37baa9d5c90be5f206d0c


prusa-slicer: 2.2.0 -> 2.3.0

Motivation for this change
Preparing for the coming 2.3.0 release, documenting/sharing what needs to change.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc @mweinelt @ArdaXi @baracoder @thorstenweber83 as you were interested in the previous PRs

Builds fine for me, but throws assertion errors from time to time and some UI parts are broken. It is still RC1 though

Builds fine for me, but throws assertion errors from time to time and some UI parts are broken. It is still RC1 though

v2.3.0 is out.

v2.3.0 is out.

I've updated the PR to 2.3.0, which uses GTK3. I hope I got all new dependencies...

I've updated the PR to 2.3.0, which uses GTK3. I hope I got all new dependencies...

I was trying to get this working myself (I really wanted to try the monotonic infill) and these are much the same changes I made. I did also end up adding hicolor-icon-theme because it was complaining about it being missing in the logs, but I'm not sure if it being missing actually affects anything.

I was trying to get this working myself (I really wanted to try the monotonic infill) and these are much the same changes I made. I did also end up adding hicolor-icon-theme because it was complaining about it being missing in the logs, but I'm not sure if it being missing actually affects anything.

I was trying to get this working myself (I really wanted to try the monotonic infill) and these are much the same changes I made. I did also end up adding hicolor-icon-theme because it was complaining about it being missing in the logs, but I'm not sure if it being missing actually affects anything.

I have hicolor-icon-theme in my home-managers packages, so I didn't see that. I've added it to our inputs though as at least some packages do add it to their inputs. Not sure if this correct though...

I was trying to get this working myself (I really wanted to try the monotonic infill) and these are much the same changes I made. I did also end up adding hicolor-icon-theme because it was complaining about it being missing in the logs, but I'm not sure if it being missing actually affects anything.

I have hicolor-icon-theme in my home-managers packages, so I didn't see that. I've added it to our inputs though as at least some packages do add it to their inputs. Not sure if this correct though...

Isn't that the same argument as for wrapGAppsHook? That should also be unnecessary if the user's environment is set up properly, and it seems like NixOS has standardized on providing it. See discussion in #16285

Isn't that the same argument as for wrapGAppsHook? That should also be unnecessary if the user's environment is set up properly, and it seems like NixOS has standardized on providing it. See discussion in #16285

Isn't that the same argument as for wrapGAppsHook? That should also be unnecessary if the user's environment is set up properly, and it seems like NixOS has standardized on providing it. See discussion in #16285

Thanks, I didn't know about that. :)

Isn't that the same argument as for wrapGAppsHook? That should also be unnecessary if the user's environment is set up properly, and it seems like NixOS has standardized on providing it. See discussion in #16285

Thanks, I didn't know about that. :)

prusa-gcodeviewer binary is not built, but prusa-slicer expects it to be

prusa-gcodeviewer binary is not built, but prusa-slicer expects it to be

prusa-gcodeviewer binary is not built, but prusa-slicer expects it to be

Thanks! :) I've also added a application menu entry.

prusa-gcodeviewer binary is not built, but prusa-slicer expects it to be

Thanks! :) I've also added a application menu entry.

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

2 packages built:

prusa-slicer
super-slicer

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

2 packages built:

prusa-slicer
super-slicer

Wow, their GUI looks nice in this update)
All functionality works, slicing and exporting doesn't crash like it does in SS 2.3 branches.

Wow, their GUI looks nice in this update)
All functionality works, slicing and exporting doesn't crash like it does in SS 2.3 branches.

prusa-slicer segfaults when opening a gcode file with File -> G-Code preview after launching prusa-gcodeviewer. Does anyone else see this?

prusa-slicer segfaults when opening a gcode file with File -> G-Code preview after launching prusa-gcodeviewer. Does anyone else see this?

prusa-slicer segfaults when opening a gcode file with File -> G-Code preview after launching prusa-gcodeviewer. Does anyone else see this?

Can't reproduce. Works for me.

prusa-slicer segfaults when opening a gcode file with File -> G-Code preview after launching prusa-gcodeviewer. Does anyone else see this?

Can't reproduce. Works for me.

@Moredread It works for me. Can you, may be, share your GCODE with us?

@Moredread It works for me. Can you, may be, share your GCODE with us?

Thanks for checking, I guess in that case it's an upstream issue. I'll post  my gcode file later if I remember, but it shouldn't block this PR.

Thanks for checking, I guess in that case it's an upstream issue. I'll post  my gcode file later if I remember, but it shouldn't block this PR.

It now works, no idea what has changed overnight. XD

It now works, no idea what has changed overnight. XD

Thanks @Moredread!

Thanks @Moredread!


Joken.Signer hides private data when inspected

Related to https://github.com/joken-elixir/joken/issues/383

Since the approach on JOSE was merged and released, I'll be updating the dependency here and will close this :)


A question about the transform on the label

Cool work! But I have a question about the transform on the label in your defination of VOCClassSegBase(data.Dataset) in the voc.py. Why did you replace the pixel value 255 to -1 on the label like this ：
lbl = PIL.Image.open(lbl_file)
lbl = np.array(lbl, dtype=np.int32)
lbl[lbl == 255] = -1?

This is specific to the data set more than this package, could be because in labels they are using 255 value to indicate an unlabeled regions.
Library requires(?) the unlabeled data to have a -1 value, in visualization which is coming from the fcn utilities module this will be filled up with random noise. @wkentaro might be able to correct me on this though.


Turning off HydroDyn Summary file causes Segmentation Fault

I came across this bug trying to run a large number of FAST simulations.  My HydroDyn summary files for the OC3/Hywind spar are about ~4MB due to its long joint, member, and radiation tables.  I would like to avoid printing this since it eats up valuable disk space on my cluster allocation.  However, setting "HDSum" to "False" results in a Segmentation fault.  The model otherwise runs fine when set to "True"
Error occurred on the following builds:
Windows, compiles with Cygwin, single precision, 64 bit, release mode, openfast-v2 and dev
Linux, gcc 8.1.0, single precision, 64 bit, release mode, openfast-v2 and dev
Using the "5MW_OC3Spar_DLL_WTurb_WavesIrr" model from r-test

OpenFAST input file heading:
FAST Certification Test #24: NREL 5.0 MW Baseline Wind Turbine with OC3 Hywind Configuration,
for use in offshore analysis
Running ElastoDyn.
Running AeroDyn.
Running AirfoilInfo.
Running BEM.
Running UnsteadyAero.
Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0.  BladeNode = 1, Blade = 1
Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0.  BladeNode = 1, Blade = 2
Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0.  BladeNode = 1, Blade = 3
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers.
Running HydroDyn.
Generating incident wave kinematics and current time history.
Reading in WAMIT output with root name
"C:\Users\egaertne\OptFAST\temp\testing0x6_5\nrel5mw_spar\HydroData/Spar".
Computing radiation impulse response functions and wave diffraction forces.
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0  0xffffffffffffffff in ???
#1  0xffffffffffffffff in ???
#2  0xffffffffffffffff in ???
#3  0xffffffffffffffff in ???
#4  0xffffffffffffffff in ???
#5  0xffffffffffffffff in ???
#6  0xffffffffffffffff in ???
#7  0xffffffffffffffff in ???
#8  0xffffffffffffffff in ???
#9  0xffffffffffffffff in ???
#10  0xffffffffffffffff in ???
#11  0xffffffffffffffff in ???
#12  0xffffffffffffffff in ???
#13  0xffffffffffffffff in ???
#14  0xffffffffffffffff in ???
#15  0xffffffffffffffff in ???
#16  0xffffffffffffffff in ???
#17  0xffffffffffffffff in ???
#18  0xffffffffffffffff in ???
#19  0xffffffffffffffff in ???
3 [main] openfast 4460 cygwin_exception::open_stackdumpfile: Dumping stack trace to openfast.exe.stackdump

@evan-gaertner are you on the latest commit on the dev branch? This bug was fixed in #207.
I'm closing this issue, but please reopen if this is indeed still a bug.

Ah you're absolutely right, I was a couple of commits behind.  Sorry to bug you with this!
Thanks as always,
Evan


Install turbo-ignore

Should help with Vercel build speeds (it will skip the relative-values deployment it it hasn't changed, etc.)
Docs: https://vercel.com/docs/concepts/monorepos/turborepo#using-turbo-ignore

Codecov Report

Merging #1599 (c444669) into develop (14e7d44) will decrease coverage by 0.03%.
The diff coverage is n/a.

:exclamation: Current head c444669 differs from pull request most recent head 2055d70. Consider uploading reports for the commit 2055d70 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##           develop    #1599      +/-   ##
===========================================
- Coverage    73.12%   73.09%   -0.03%
===========================================
  Files           93       93
  Lines         5030     5069      +39
  Branches       846      847       +1
===========================================
+ Hits          3678     3705      +27
- Misses        1327     1338      +11
- Partials        25       26       +1

see 9 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


security_monkey should ship with AWS accounts built in

There are a number of AWS owned accounts that have business accessing most environments.  A few examples are:

CloudTrail,
ELB / CloudFront logs
Support accounts.

security_monkey should ship with a list of these accounts.  Adding them would be an optional command from manage.py.  They should be marked as third-party and not active.
This requires:

Enumerating the AWS accounts to add.
Updating manage.py
Updating readme/quickstart/documentation.

The idea is from @bunjiboys

Merged in #241


[hold] refactor: Merge Active and Api code together

Fixes #324

[x] Add to readme file more in-depth information: https://github.com/posit-dev/posit-sdk-py/pull/330/files#diff-97a404af0cd76efe034f1917316121f8ff4be4a51655e5bc16b65f5800cdb2b7
[ ] Make PR in rstudio/connect to address the no "alter in place" updates

Goals:

Turn entity classes into read only dictionaries. Prevents users from updating data in place. All .update()-like methods now return a new object.
Minimize public parameters such as .params: ResourceParameters (Rename to ._ctx: Context

Inherit from Context to extend it with more information rather than expanding parameters. By doing so, the names and usage are consistent. (Hard to distinguish which GUID guid represents )
Leverage the ContextP[ContextT] class where possible to give ._ctx: ContextT a type.

Minimize the locations of API path. Resolve by placing the calling class.

Classes that need to fully fetch their information may provide the bare minimum information for the ActiveDict class to request the data for initialization. This reduces multiple duplications of logic to a single spot

Attempt to use ApiCallMixin within classes to reduce how urls are constructed and processed. Given a .ctx: Context and ._path: str, many calling methods can be handled under the hood.

Note - Classes that do not follow the read-only approach:

EnvVars
ContentItemVanityMixin

After conversations with Taylor, we are not going to merge this PR. However, there are good ideas within it.
Will keep the PR open until issues are made and/or components pulled out.


Update to base <IP_ADDRESS>

(And also through all intermediate bases)
This hopefully gets right the list of modules in base-4.16; it's surprisingly nonobvious which base.cabal must contain the list as of 4.16.

So. for context, this was opened for morley/#784.
There we use stack and I see that currently the base version <IP_ADDRESS> is the newest one used by a stackage LTS.
I suppose that we want to use that version now and eventually <IP_ADDRESS> after a stackage LTS adopts it.
I think we can split this PR in two commits where the first one uses <IP_ADDRESS>, so that we can pull either of these two from master once this is merged.

Oh, right :facepalm:
Either I was very distracted or GitHub played some trick on me, because I totally didn't notice the 4 commits.

Do you mean to squash two intermediate commits

No, what you did is perfectly sane, I just didn't see it for some reason.
Sorry about that, please disregard my previous comment.


Implement public mentor page

Purpose

The purpose of this PR is to fix #9
Goals

The goal of this PR is to implement public mentor page
Approach

Screenshots

Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Related PRs

Test environment

Learning

Do we remove unused fields from profile? like the first_name, last_name and etc.
        {
            "state": "approved",
            "category": {
                "category": "Computer Science",
                "uuid": "406397fc-3cff-4780-a361-7db345845bb6",
                "created_at": "2024-01-03T16:08:12.214Z",
                "updated_at": "2024-01-03T16:08:12.214Z"
            },
            "application": {
                "firstName": "John",
                "lastName": "Doe",
                "email"<EMAIL_ADDRESS>                "contactNo": "+94779970622",
                "country": "Sri Lanka",
                "position": "SE at Google Inc",
                "expertise": "Fullstack engineering",
                "bio": "Yadi yada",
                "isPastMentor": true,
                "reasonToMentor": "Makes me happy",
                "motivation": "Boom",
                "cv": "https://www.linkedin.com/in/madhawamonara/",
                "menteeExpectations": "Enthusiastic",
                "mentoringPhilosophy": "Yadi yada",
                "noOfMentees": 5,
                "canCommit": true,
                "mentoredYear": 2020,
                "category": "406397fc-3cff-4780-a361-7db345845bb6",
                "institution": "ITUM",
                "linkedin": "https://www.linkedin.com/in/madhawamonara/",
                "website": "https://www.linkedin.com/in/madhawamonara/"
            },
            "availability": true,
            "profile": {
                "primary_email"<EMAIL_ADDRESS>                "contact_email": "",
                "first_name": "",
                "last_name": "",
                "image_url": "",
                "linkedin_url": "",
                "type": "default",
                "uuid": "1f766bf2-045a-4a27-8087-8c6b8e2b4561",
                "created_at": "2024-03-24T11:49:50.390Z",
                "updated_at": "2024-03-24T11:49:50.390Z"
            },
            "uuid": "86b65e78-dde4-447a-9abb-c72a4b86cf6f",
            "created_at": "2024-03-24T11:54:49.599Z",
            "updated_at": "2024-03-24T11:54:49.599Z"
        },

Do we remove unused fields from profile? like the first_name, last_name and etc.
        {
            "state": "approved",
            "category": {
                "category": "Computer Science",
                "uuid": "406397fc-3cff-4780-a361-7db345845bb6",
                "created_at": "2024-01-03T16:08:12.214Z",
                "updated_at": "2024-01-03T16:08:12.214Z"
            },
            "application": {
                "firstName": "John",
                "lastName": "Doe",
                "email"<EMAIL_ADDRESS>                "contactNo": "+94779970622",
                "country": "Sri Lanka",
                "position": "SE at Google Inc",
                "expertise": "Fullstack engineering",
                "bio": "Yadi yada",
                "isPastMentor": true,
                "reasonToMentor": "Makes me happy",
                "motivation": "Boom",
                "cv": "https://www.linkedin.com/in/madhawamonara/",
                "menteeExpectations": "Enthusiastic",
                "mentoringPhilosophy": "Yadi yada",
                "noOfMentees": 5,
                "canCommit": true,
                "mentoredYear": 2020,
                "category": "406397fc-3cff-4780-a361-7db345845bb6",
                "institution": "ITUM",
                "linkedin": "https://www.linkedin.com/in/madhawamonara/",
                "website": "https://www.linkedin.com/in/madhawamonara/"
            },
            "availability": true,
            "profile": {
                "primary_email"<EMAIL_ADDRESS>                "contact_email": "",
                "first_name": "",
                "last_name": "",
                "image_url": "",
                "linkedin_url": "",
                "type": "default",
                "uuid": "1f766bf2-045a-4a27-8087-8c6b8e2b4561",
                "created_at": "2024-03-24T11:49:50.390Z",
                "updated_at": "2024-03-24T11:49:50.390Z"
            },
            "uuid": "86b65e78-dde4-447a-9abb-c72a4b86cf6f",
            "created_at": "2024-03-24T11:54:49.599Z",
            "updated_at": "2024-03-24T11:54:49.599Z"
        },

Applications shouldn't be retrieved

@anjula-sack I have updated the MentorCardType to match with the backend response and also added a new mentorCards mock to support the stories.
But if we send the fields mentorId as uuid and category as Category type, then we could use the mentors mock as well.
Also seems like we don't keep track of the mentor's company or institution. Is it intentional?


Typo in description for Cartesian Explosion

I noticed a typo in the description of the "Cartesian Explosion term, as shown in the image below

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

ID: 43baa9f3-c415-c328-6c10-53aabaaec652
Version Independent ID: 4e789a1b-aa88-d194-dc2e-0a23251250d7
Content: Single vs. Split Queries - EF Core
Content Source: entity-framework/core/querying/single-split-queries.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @roji
Microsoft Alias: avickers

I noticed something weird, the typo is shown on the website but not present in the content source

I was fixed yesterday but not published yet.

Okay cool. Thanks


cleanup duplicated code

The original check was to allow other requests to quickly skip over (before cache.Lock) and read from object storage when an error occurs (e.g., the disk hangs). This modification will not achieve that purpose.


Check the TODOs in the code and create issues to those that are not s…

Summary or solution description
TODOs removed:
# TODO: get module name

Removed it because filename exists

# TODO: concat and power not implemented yet

Removed because CONCAT and POWER were implemented

# TODO: is, is not and eq were not implemented yet

Is, IsNot, and Eq were implemented

# TODO: Implement this transfer method on issue #855

The was changed, and all the content inside the smart contract and test will be replaced.

# TODO: include example when objects are implemented

I don't think NEP-5 will be touched again, so I'll delete this

# TODO: Test if the refund is successful when update the TestEngine to make Neo/Gas transfers

I don't think ico will be touched again, so I'll delete this

Platform:

OS: Windows 10 x64
Python version: Python 3.8

Task linked: CU-2ewec9h Check the TODOs in the code and create issues to those that are not solved


Update pt_BR lang

Full Brazilian Portuguese translation of Mekanism. Adds a ton of new entries, syncs with en_US, translates a handful of left-overs and general spruce-up.
European Portuguese to come (has to be created).

Thank you!


Category encoding support beyond one-hot

Is your feature request related to a problem? Please describe.
I have a dataset with a lot of categorical data. At the moment, I'm doing all my training and predicting in Python, but I'm eager to make the step to Java. I use James-Stein encoding on many of my columns. I'm looking for a way to do this in Tribuo.
Describe the solution you'd like
Could you help me think of a good way to realise this? The logical place in my mind is to create a FieldProcessor like the DoubleProcessor but then instead of parsing the value, we apply some sort of encoding to give a good value. It would be very handy to have this in the provenance system as well, I think.
Describe alternatives you've considered
I've considered keeping my encoders in Python and writing an API to reach them, but it feels like the platform is so close to being able to do this, because I think one-hot encoding is already possible in the form of the IdentityProcessor

Unfortunately I think the current Tribuo APIs don't have a good way of doing this. RowProcessor operates on a single row at a time, it never has a view of the full dataset as it would need to compute the Output mean conditioned on a specific feature value. Additionally the feature transformation infrastructure only considers a single feature at a time, so there is no way to make its behaviour conditional on the Output.
This particular encoding would fit better into Tribuo's transformation system rather than any inbound ETL step (e.g. RowProcessor) as that way it is easier to ensure correct usage, as if it lives inside TransformTrainer then you wouldn't be able to leak information from test to train by applying it during ETL and then splitting the dataset with TrainTestSplitter or CrossValidation. But as I mention above the transformation system doesn't currently have a way to do that kind of dependent transform. We're thinking about how we can evolve the design of it to allow transformations like PCA, so I'll make sure we include this kind of encoding as another design point.
If you want to do this today, and are willing to manage the train/test data leakage issues yourself then I think the simplest way is to write a DataSource which accepts another DataSource and performs the transformation on construction.


Unit Testing + Travis CI

It’s super nice to have contributions from someone else but it’s hard to see if those changes break existing features. We all do mistakes from time to time and it’s easier to recover if you have good test coverage. Automated integration tests can help you out in these situations.
Is someone available in writing unit tests and integration with Trevis?

Guys,  i think this is important :)

I'll have to go read up... i know nothing about it.

you don't know unit testing? Try to google it
In project like this is very useful.

@amiga-500 https://phpunit.de/getting-started.html

Oh i know unit testing.  I just don't know Travis CI and the whole integration process.
Thanks for the link!  I will do reading about Travis in the coming days.

@szepeviktor please, help me...! how confing travis to work with apcu? i want make some unit test!

Just install APCu in a shell script depending on the PHP version: apt-get install -y php5-apcu and apt-get install -y php7.0-apcu
See https://docs.travis-ci.com/user/installing-dependencies/

mhhh ok i need to study travis https://github.com/szepeviktor/fix-w3tc/pull/107
if you have time, you can set travis for me?
i have also write some unit tests in test dir.


RpmPackage.version and RpmPackage.release are incorrect

In Pull Request #165 I've submitted a small change to the way rpm package information is generated.
The error was that the version string reported , for example:
% rpm -q acl
acl-2.2.49-6.el6.x86_64
% rpm -qi acl
Name        : acl                          Relocations: (not relocatable)
Version     : 2.2.49                            Vendor: Red Hat, Inc.
Release     : 6.el6                         Build Date: Tue 26 Jul 2011 07:44:27 AM CDT
Install Date: Mon 28 Sep 2015 04:28:47 PM CDT      Build Host: x86-005.build.bos.redhat.com
Group       : System Environment/Base       Source RPM: acl-2.2.49-6.el6.src.rpm
Size        : 193226                           License: GPLv2+
Signature   : RSA/8, Thu 06 Oct 2011 05:45:07 AM CDT, Key ID 199e2f91fd431d51
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://acl.bestbits.at/
Summary     : Access control list utilities
Description :
This package contains the getfacl and setfacl utilities needed for
manipulating access control lists.

>>> Package('acl').version
2.2.49                            Vendor: Red Hat, Inc.

This is on a RHEL6.7 system.
In RHEL7.2, the output of rpm -qi changed and perhaps the parsing would have worked.  However, there are --queryformat ways to get the information without parsing the "info" output.
The pull request changes the way this information is gathered to a more canonical and stable method.
To wit:
% rpm -q --queryformat="%{VERSION"} acl
2.2.49

PR merged, this is resolved


signal/poll optimization

Hi, it would be great if the sm/proxy channel can support signal/poll multiple times in one function call. The code changes in this PR supports the functionality without disrupting existing usage, i.e., signal() and poll() work as before.

signal(n) sends n signals down the channel. For sm channel, this avoids doing atomicLoad multiple times on the semaphore.
x = poll(n) polls up to n signals from the channel and returns the actual number of signals polled. It returns 0 if n<=0.
signal() and poll() are equivalent to signal(1) and poll(1), which are the default arguments.

@microsoft-github-policy-service agree

Hmm. cam you tell us the scenarios which require this feature?

In my scenario, for example, data is sent as a flow of chunks between a producer and a consumer. The producer signals once per chunk sent. It would be nice for the consumer to know how many chunks it has received by one poll call. The producer may also decide to send n chunks at once, in which case n signals can be sent with one signal call.

In my scenario, for example, data is sent as a flow of chunks between a producer and a consumer. The producer signals once per chunk sent. It would be nice for the consumer to know how many chunks it has received by one poll call. The producer may also decide to send n chunks at once, in which case n signals can be sent with one signal call.

If the producer has multiple data chunks to send, you could put multiple times and then signal once. The consumer would call wait once. Does it work for your scenario?
If the producer needs to send the number of chunks to send, you could send that information as another data chunk. Probably your implementation would be faster than this, but I expect the diff of latencies would be nearly invisible.
As a minor concern, incrementing the semaphore ID by user inputs may introduce chances of misuses or bugs. For example, current design uses a single 64-bit unsigned integer flag, assuming at most single increment per a signal. This makes sense because if we say a single signal takes 100ns, it will take more than 50k years to overflow the flag. Now if we increment this by user inputs, we are implicitly pushing the users to take care of the overflow issue.

In my scenario, for example, data is sent as a flow of chunks between a producer and a consumer. The producer signals once per chunk sent. It would be nice for the consumer to know how many chunks it has received by one poll call. The producer may also decide to send n chunks at once, in which case n signals can be sent with one signal call.

If the producer has multiple data chunks to send, you could put multiple times and then signal once. The consumer would call wait once. Does it work for your scenario?
If the producer needs to send the number of chunks to send, you could send that information as another data chunk. Probably your implementation would be faster than this, but I expect the diff of latencies would be nearly invisible.
As a minor concern, incrementing the semaphore ID by user inputs may introduce chances of misuses or bugs. For example, current design uses a single 64-bit unsigned integer flag, assuming at most single increment per a signal. This makes sense because if we say a single signal takes 100ns, it will take more than 50k years to overflow the flag. Now if we increment this by user inputs, we are implicitly pushing the users to take care of the overflow issue.

Thanks for the feedback! I think sending the number of chunks separately adds unnecessary complexity, especially since the signal/poll mechanism already handles the producer-consumer scenario elegantly.
As for overflow concern, the increment could be limited to an uint8_t. This would be more than sufficient for most practical use cases, and it would still take 228 years to overflow. Please consider this feature.

In my scenario, for example, data is sent as a flow of chunks between a producer and a consumer. The producer signals once per chunk sent. It would be nice for the consumer to know how many chunks it has received by one poll call. The producer may also decide to send n chunks at once, in which case n signals can be sent with one signal call.

If the producer has multiple data chunks to send, you could put multiple times and then signal once. The consumer would call wait once. Does it work for your scenario?
If the producer needs to send the number of chunks to send, you could send that information as another data chunk. Probably your implementation would be faster than this, but I expect the diff of latencies would be nearly invisible.
As a minor concern, incrementing the semaphore ID by user inputs may introduce chances of misuses or bugs. For example, current design uses a single 64-bit unsigned integer flag, assuming at most single increment per a signal. This makes sense because if we say a single signal takes 100ns, it will take more than 50k years to overflow the flag. Now if we increment this by user inputs, we are implicitly pushing the users to take care of the overflow issue.

Thanks for the feedback! I think sending the number of chunks separately adds unnecessary complexity, especially since the signal/poll mechanism already handles the producer-consumer scenario elegantly.
As for overflow concern, the increment could be limited to an uint8_t. This would be more than sufficient for most practical use cases, and it would still take 228 years to overflow. Please consider this feature.

Sure, but that is further narrowing the use cases. Looks like you basically want a simple interface that sends a single byte data, and I still don't get exactly why we would need this.

My understanding of the programming model for the mscclpp channel is that the signal serves to notify the receiver that a task is ready for processing, which is exactly a producer-consumer scenerio. The current interface can do this but it requires repeated operations on global memory that could be done in one round. Especially in the poll case, the consumer needs to atomicLoad n+1 times to know n chunks are ready to be processed in a batch or so. Sending extra bytes along signal to indicate the # of chunks can avoid this, but it still requires the receiver to store and sum the received values, rather than leveraging the increment of semaphore.
I am OK to close this issue if you believe it would be more appropriate to address it otherwise.

My understanding of the programming model for the mscclpp channel is that the signal serves to notify the receiver that a task is ready for processing, which is exactly a producer-consumer scenerio. The current interface can do this but it requires repeated operations on global memory that could be done in one round. Especially in the poll case, the consumer needs to atomicLoad n+1 times to know n chunks are ready to be processed in a batch or so. Sending extra bytes along signal to indicate the # of chunks can avoid this, but it still requires the receiver to store and sum the received values, rather than leveraging the increment of semaphore.
I am OK to close this issue if you believe it would be more appropriate to address it otherwise.

I assume you are talking about wait not poll, because poll is designed to be repeated multiple times indefinitely. If I'm correct, could you ellaborate on why you need to repeat wait multiple times? You could send a single signal for the entire n+1 chunks, then you could wait just once.

My understanding of the programming model for the mscclpp channel is that the signal serves to notify the receiver that a task is ready for processing, which is exactly a producer-consumer scenerio. The current interface can do this but it requires repeated operations on global memory that could be done in one round. Especially in the poll case, the consumer needs to atomicLoad n+1 times to know n chunks are ready to be processed in a batch or so. Sending extra bytes along signal to indicate the # of chunks can avoid this, but it still requires the receiver to store and sum the received values, rather than leveraging the increment of semaphore.
I am OK to close this issue if you believe it would be more appropriate to address it otherwise.

I assume you are talking about wait not poll, because poll is designed to be repeated multiple times indefinitely. If I'm correct, could you ellaborate on why you need to repeat wait multiple times? You could send a single signal for the entire n+1 chunks, then you could wait just once.

I am referring to poll. Basically, the feature I am proposing is to support (1) sending n signals in one function call, and (2) knowing how many signals have been received in one poll. This would eliminate the need for repeated atomicLoads and GMEM access. The (2) is sort of similar to the poll in C that returns the # of ready fds.
In your case, if I send 1 signal for n+1 chunks, I would need additional logic to track how many chunks were sent, as n is a runtime variable. It would be simpler to send 1 signal per chunk. For example, if I send 3, 4, 5 chunks and signal 3, 4, 5 times in three rounds, a single poll on the receiver side would return 12, indicating that 12 chunks have been sent.
To be consistent with the existing poll() that returns true/false, I implemented poll(n), where n is the maximum # of signals to poll. Thus, the existing poll() is equivalent to poll(1).